13.3.8. XsltAction
This performs transformation on entire documents.
Property | Description | Required |
---|---|---|
get-payload-location
|
Message Body location containing the message payload.
If unspecified the Default Payload Location is used.
|
NO
|
set-payload-location
|
Message Body location where result payload is to be placed.
If unspecified the Default Payload Location is used.
|
No
|
templateFile
|
Path to the XSL Template file. It can be defined with a file path within the deployed archive, or as a URL.
|
Yes
|
resultType
|
The type of Result to be set as the result Message payload.
This property controls the output result of the transformation. The following values are currently available:
When the message payload is a
SourceResult object and resultType is not set to SOURCERESULT , the result is returned as the type specified in resultType. The developer is responsible for ensuring the types are compatible.
|
No
|
failOnWarning
|
If
true will cause a transformation warning to cause an exception to be thrown. If false the failure will be logged.
Defaults to True.
|
No
|
uriResolver
|
Fully qualified class name of a class that implements
URIResolver . This will be set on the tranformation factory.
|
No
|
factory.feature.*
|
Factory features that will be set for the tranformation factory. The feature name, which are fully qualified URIs, should be specified after the factory.feature. prefix. E.g. factory.feature.http://javax.xml.XMLConstants/feature/secure-processing
|
No
|
Factory.attribute.*
|
Factory attributes that will be set for the tranformation factory. The attribute name should be specified after the factory.attribute. prefix. E.g. factory.attribute.someVendorAttributename
|
NO
|
validation |
If true will cause an invalid source document to cause an exception to be thrown. If false validation will not occur, although well-formed documents are enforced. .
Default value is
. false
| No |
schemaFile |
The input schema file (XSD) to use, located on the classpath. .
| No |
schemaLanguage |
The input schema language to use.
| No |