[#PETALSSEXSLT-30] Add support of XSLT engine attributes - Petals Link JIRA

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

Description:

Hide

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:

<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>

If only one attribute, it can be written as:

<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>

Show

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:

<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>

If only one attribute, it can be written as:

<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>

Environment:

-

Activity

Ascending order - Click to sort in descending order

There are no comments yet on this issue.

Petals SE XSLT

Add support of XSLT engine attributes

Details

Activity

People

Dates