Re: New XT release (19991105)

["Steve Muench" <smuench@xxxxxxxxxxxxx>]

It *looks* like the line number, but given a file like:

<list>
  <thing id="1"/>
  <thing id="2"/>
  <thing id="3"/>
  <thing id="4"/>
  <thing id="5"/>
</list>

And a stylesheet of:

<list xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>
   <xsl:for-each select="//*">
     <xsl:message><xsl:value-of select="@id"/></xsl:message>
   </xsl:for-each>
</list>

I see the message output of:

file:/C:/TEMP/list.xml:1:
file:/C:/TEMP/list.xml:2: 1
file:/C:/TEMP/list.xml:3: 2
file:/C:/TEMP/list.xml:4: 3
file:/C:/TEMP/list.xml:5: 4
file:/C:/TEMP/list.xml:6: 5

So it seems like something else, like some
other kind of node-id other than generate-id()
would give you.
_________________________________________________________
Steve Muench, Consulting Product Manager & XML Evangelist
Business Components for Java Development Team
http://technet.oracle.com/tech/java
http://technet.oracle.com/tech/xml
----- Original Message -----
From: Rick Jelliffe <ricko@xxxxxxxxxxxxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxx>
Sent: Monday, November 08, 1999 10:38 PM
Subject: RE: New XT release (19991105)


| On Mon, 8 Nov 1999 DPawson@xxxxxxxxxxx wrote:
|
| > >A new release of XT is available. For more information, see
| > >
| > >  http://www.jclark.com/xml/xt.html
| > >
| > >The most interesting new feature is an xt:node-set extension function
| > >that converts a result tree fragment to a node-set.  It is now possible
| > >to use DOM for the result tree as well as the source tree; there's a
| > >very simple purely DOM-based API to XT that uses this.
| >
| >
| > And rumour has it that xsl:message can access the source line number.
| >
| > Has anyone tried this aspect?
|
| The message is sent to standard error (it looks like) and it includes the
| filename and line number
|
| Rick Jelliffe
|
|
|  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
|


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