[
https://issues.apache.org/jira/browse/XALANJ-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676701#action_12676701
]
Michel Nolard commented on XALANJ-1576:
---------------------------------------
As said previously, the solution already exist, so why not to apply the patch ?
As it just modifies a few lines, it should be quite straightforward to validate
it ?
Moreover, the severity of the issue which is a duplicate from this one is
"blocker" ... shouldn't this issue be tagged as a "blocker" also ?
I really need this issue to be solved quickly... and I can't use an unofficial
Xalan release as it is against our policies.
> xsl:attribute and element extensions
> ------------------------------------
>
> Key: XALANJ-1576
> URL: https://issues.apache.org/jira/browse/XALANJ-1576
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Components: parse-or-compile, Xalan-interpretive
> Affects Versions: 2.5Dx
> Environment: Operating System: All
> Platform: All
> Reporter: Dimitry E Voytenko
> Assignee: Xalan Developers Mailing List
> Attachments: 1
>
>
> Using extension elements inside of xsl:attribute produces error:
> "javax.xml.transform.TransformerException: ns:name is not allowed in this
> position in the stylesheet!"
> For instance, if I have describe prefix "my" as an extension element prefix,
> and there's element "url" in this namespace, call to
> <xsl:attribute name="HREF">
> <my:url>...</my:url>
> </xsl:attribute>
> will produce error described above.
> Extension usage such as this is particulary convinient for URL creation.
> Workaround in this situation will be using temp variable:
> <xsl:variable name="href">
> <my:url>...</my:url>
> </xsl:variable>
> <xsl:attribute name="HREF">
> <xsl:value-of select="$href"/>
> </xsl:attribute>
> As I understand, error is being raise during stylesheet parsing. Still, I
> couldn't find such a restriction anywhere in the XSLT 1.0 specification.
> Paragraph 7.1.3 of the spec only says that it's an error "Creating nodes
> other
> than text nodes during the instantiation of the content of the xsl:attribute
> element; implementations may either signal the error or ignore the offending
> nodes."
> But I don't think this paragraph can be applied to this situation.
> Otherwise, spec allows using "Content: template" inside of xsl:attribute and
> extension elements belong to this group.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org
For additional commands, e-mail: xalan-dev-h...@xml.apache.org
