xsl-list
[Top] [All Lists]

Problem with new version of Xalan

2003-01-09 09:26:36
Hi,

a few weeks ago we have installed the new version of the xalan parser.
Since then we have some mysterious phenomena.

The first is, that the parser don't allow to overwrite named templates. 
Is this behavior from the parser correct?
We have several named templates which we overwrite if we need 
other outputs. So this new 'feature' present us much more work.

The second phenomena ist, the parser seems not to know what 
the "|" means.
We have the following code:

<xsl:for-each select="self::* | following-sibling::*">
...
</xsl:for-each>

The HTML output just shows the first element like we have used
this code:

<xsl:for-each select="self::*">
...
</xsl:for-each>

If we use the second part of the node decision like this:

<xsl:for-each select="following-sibling::*">
...
</xsl:for-each>

We just get all elements except the first.

It seems that the "|" is the problem. 
Do I need another code?
Does the parser has some bugs?
Is there another expression for "|"?

Thanks to anyone for quick help.

Regards

Dirk Holstein
-------------------------------------------
www.doubleSlash.de
dirk(_dot_)holstein(_at_)doubleSlash(_dot_)de



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list



<Prev in Thread] Current Thread [Next in Thread>
  • Problem with new version of Xalan, Dirk Holstein <=