Variable nested in param sets incorrect param value
---
Key: XALANJ-1984
URL: http://nagoya.apache.org/jira/browse/XALANJ-1984
Project: XalanJ2
Type: Bug
Components: Xalan-interpretive
Versions: 2.6
Environ
> Okay, but all of the templates were imported. The template it
eventually selected to execute
> was also an imported template. Why did it select imported template B
with a lower priority
> versus imported template C? The one it ultimately selected was the
last template imported;
> I moved t
>...Why did it select imported template B with a lower priority versus
imported template C?
If they were imported from different places, then their import precedence
differs. But it appears that you really want to switch over to
xsl:include, since you want to avoid the effects of import precede
Okay, but all of the templates were imported. The template it
eventually selected to execute was also an imported template. Why did
it select imported template B with a lower priority versus imported
template C? The one it ultimately selected was the last template
imported; I moved them aro
[ http://nagoya.apache.org/jira/browse/XALANJ-1983?page=comments#action_55083 ]
Robert Taylor commented on XALANJ-1983:
---
Please note that when I entered this bug, JIRA
munged the formatting of the table structure
in the following section:
Here i
last() inside for-each causes strange behavior
--
Key: XALANJ-1983
URL: http://nagoya.apache.org/jira/browse/XALANJ-1983
Project: XalanJ2
Type: Bug
Components: Xalan
Versions: 2.6
Environment: Win2k JDK1.4.2