Details
-
Type:
Improvement Request
-
Status:
New
-
Priority:
Blocker
-
Resolution: Unresolved
-
Affects Version/s: 2.7.3
-
Fix Version/s: None
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
Activity
| Field | Original Value | New Value |
|---|---|---|
| Priority | Blocker [ 1 ] | |
| Description |
An XSLT engine can accept attributes to drive its underlying implementation, for example:
* to enable or disable features, * to enable or disable traces, * to enable or disable the loading of external resources, * ... Such an attribute is set using the API {{TransformerFactory.setAttribute(...)}}. Such attributes are set at SU level, in the SU JBI descriptor as following. It is an optional parameter: {code} <jbi:jbi version="1.0" ...> <jbi:services ...> <jbi:provides ...> ... <xslt:stylesheet>transform.xsl</xslt:stylesheet> <xslt:xslt-engine-factory-class-name>org.apache.xalan.processor.TransformerFactoryImpl</xslt:xslt-engine-factory-class-name> <xslt:xslt-engine-attribute0 name="attribute0-name">attribute0-value</xslt:xslt-engine-attribute0> <xslt:xslt-engine-attribute1 name="attribute0-name">attribute0-value</xslt:xslt-engine-attribute1> ... </jbi:provides> </jbi:services> </jbi> {code} |
An XSLT engine can accept attributes to drive its underlying implementation, for example:
* to enable or disable features, * to enable or disable traces, * to enable or disable the loading of external resources, * ... Such an attribute is set using the API {{TransformerFactory.setAttribute(...)}}. Such attributes are set at SU level, in the SU JBI descriptor as following. It is an optional parameter: {code} <jbi:jbi version="1.0" ...> <jbi:services ...> <jbi:provides ...> ... <xslt:stylesheet>transform.xsl</xslt:stylesheet> <xslt:xslt-engine-factory-class-name>org.apache.xalan.processor.TransformerFactoryImpl</xslt:xslt-engine-factory-class-name> <xslt:xslt-engine-attribute-name0>attribute0-name</xslt:xslt-engine-attribute-name0> <xslt:xslt-engine-attribute-value0>attribute0-value</xslt:xslt-engine-attribute-value0> <xslt:xslt-engine-attribute-name1>attribute0-name</xslt:xslt-engine-attribute-name1> <xslt:xslt-engine-attribute-value1>attribute0-value</xslt:xslt-engine-attribute-value1> ... </jbi:provides> </jbi:services> </jbi> {code} If only one attribute, it can be written as: {code} <jbi:jbi version="1.0" ...> <jbi:services ...> <jbi:provides ...> ... <xslt:stylesheet>transform.xsl</xslt:stylesheet> <xslt:xslt-engine-factory-class-name>org.apache.xalan.processor.TransformerFactoryImpl</xslt:xslt-engine-factory-class-name> <xslt:xslt-engine-attribute-name>attribute-name</xslt:xslt-engine-attribute-name> <xslt:xslt-engine-attribute-value>attribute-value</xslt:xslt-engine-attribute-value> ... </jbi:provides> </jbi:services> </jbi> {code} |