[
https://issues.apache.org/jira/browse/XALANJ-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463071
]
Kevin Cormier commented on XALANJ-2353:
---------------------------------------
I agree that XSLTC should give access to custom output properties specified in
the stylesheet. This seems to be the intention in the JAXP specification,
though I didn't find reference to it in the XSLT spec.
I have attached a patch that provides this functionality. It does not address
the getParameter() issue though. While it is clear that getParameter() is only
supposed to return parameter values that were set with setParameter(), some
users may have come to rely on using getParameter() to access values given in
the stylesheet, so I think it is better to leave it as is.
> XSLTC Templates.getOutputProperties() does not return custom properties
> -----------------------------------------------------------------------
>
> Key: XALANJ-2353
> URL: https://issues.apache.org/jira/browse/XALANJ-2353
> Project: XalanJ2
> Issue Type: Bug
> Components: XSLTC
> Affects Versions: 2.7
> Reporter: Peter Hendriks
> Attachments: j2353.patch
>
>
> The XSLT specification describes the use of "custom" output properties using
> a namespace other than the default or XSLT namespace. For example <xsl:output
> foo:bar="true" xmlns:foo="http://foo"; />
> In interpreted mode these properties can be retrieved using
> getOutputProperties(). In XSLTC however, properties unknown to XSLTC are not
> returned. The JAXP javadoc explicitly describes that custom properties should
> be returned. In my humble opinion this is a bug.
> We want to use data defined inside the XSLT to configure some
> after-processing. As a work-around we currently use global: <xsl:parameter
> name="foo:bar" select="'true'"/>, and retrieve the value with getParameter().
> This works in XSLTC, but it does not in interpreted mode. When looking at the
> javadoc, it seems once again that interpreted mode is right, and the XSLTC
> behavior for getParameter() is a bug too. Because of the differences in
> behavior we would need two places for the settings inside the XSLT. Please
> fix the XSLTC behavior so it is conform JAXP.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
