You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2004/02/10 12:43:06 UTC

DO NOT REPLY [Bug 26825] New: - DTM result set contains only one string with well-formed XML

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26825>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26825

DTM result set contains only one string with well-formed XML

           Summary: DTM result set contains only one string with well-formed
                    XML
           Product: XalanJ2
           Version: 2.5
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: org.apache.xalan.lib.sql
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: peter@sigent.com


DTM result set contains only one string with well-formed XML, although there 
are several <row> elements. 
For example, I get the DTM in a standard way:
<xsl:variable name="careerTable" select="sql:query($db, $query)"/>
After that the value of count($careerTable//col) is 3 (this is ok),
and value of count($careerTable//row) is always 1.
If I try to convert that DTM to a node-set with xalan:node-set function,
I get the following exception:
--------------------
java.lang.RuntimeException: Programmer assertion is incorrect! - Can not get a 
DTM Unless a DTMManager has been set!
        at org.apache.xpath.Expression.assertion(Expression.java:459)
        at org.apache.xpath.axes.NodeSequence.getDTM(NodeSequence.java:212)
        at org.apache.xml.dtm.ref.DTMNodeIterator.nextNode
(DTMNodeIterator.java:202)
        at org.apache.xpath.NodeSet.addNodes(NodeSet.java:534)
        at org.apache.xpath.NodeSet.<init>(NodeSet.java:158)
        at org.apache.xalan.lib.Extensions.nodeset(Extensions.java:128)...
etc.
--------------------

Actually I do not know if I am missing something, the source code browsing gave 
nothing to me.