[
https://issues.apache.org/jira/browse/XALANJ-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Gandhi updated XALANJ-2656:
---------------------------------
Description:
I'm creating this jira issue, to track specific enhancements to XSLT
xsl:attribute element implementation by xalanj.
XSLT 1.0 didn't allow xsl:attribute element to have an "select" attribute. But
XSLT 3.0 allows this.
The XSLT 3.0 spec, says following (among other things) about xsl:attribute
element,
"The string value of the new attribute node may be defined either by using the
select attribute, or by the sequence constructor that forms the content of the
xsl:attribute element. These are mutually exclusive: if the select attribute is
present then the sequence constructor must be empty, and if the sequence
constructor is non-empty then the select attribute must be absent."
I've modified the xalanj codebase a bit (on xalan-java repos's branch
xalan-j_xslt3.0), to implement xsl:attribute element to have an "select"
attribute (in addition to, xsl:attribute element to have child contents which
was already implemented by xalanj).
Few working test cases, for this jira issue have been attached as zip archive.
was:
I'm creating this jira issue, to track specific enhancements to XSLT
xsl:attribute element implementation by xalanj.
XSLT 1.0 didn't allow xsl:attribute element to have an "select" attribute. But
XSLT 3.0 allows this.
The XSLT 3.0 spec, says following (among other things) about xsl:attribute
element,
"The string value of the new attribute node may be defined either by using the
select attribute, or by the sequence constructor that forms the content of the
xsl:attribute element. These are mutually exclusive: if the select attribute is
present then the sequence constructor must be empty, and if the sequence
constructor is non-empty then the select attribute must be absent."
I've modified the xalanj codebase a bit (on xalan-java repos's branch
xalan-j_xslt3.0), to implement xsl:attribute element to have an "select"
attribute (in addition to, xsl:attribute element to have child contents which
was already implemented by xalanj).
> implementation of xslt xsl:attribute element's "select" attribute, for xalanj
> interpretive processor
> ----------------------------------------------------------------------------------------------------
>
> Key: XALANJ-2656
> URL: https://issues.apache.org/jira/browse/XALANJ-2656
> Project: XalanJ2
> Issue Type: New Feature
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Components: Xalan-interpretive
> Reporter: Mukul Gandhi
> Assignee: Mukul Gandhi
> Priority: Major
> Attachments: xsl_attribute_test_files.zip
>
>
> I'm creating this jira issue, to track specific enhancements to XSLT
> xsl:attribute element implementation by xalanj.
> XSLT 1.0 didn't allow xsl:attribute element to have an "select" attribute.
> But XSLT 3.0 allows this.
> The XSLT 3.0 spec, says following (among other things) about xsl:attribute
> element,
> "The string value of the new attribute node may be defined either by using
> the select attribute, or by the sequence constructor that forms the content
> of the xsl:attribute element. These are mutually exclusive: if the select
> attribute is present then the sequence constructor must be empty, and if the
> sequence constructor is non-empty then the select attribute must be absent."
> I've modified the xalanj codebase a bit (on xalan-java repos's branch
> xalan-j_xslt3.0), to implement xsl:attribute element to have an "select"
> attribute (in addition to, xsl:attribute element to have child contents which
> was already implemented by xalanj).
> Few working test cases, for this jira issue have been attached as zip archive.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
