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 2003/08/06 12:42:38 UTC

DO NOT REPLY [Bug 22167] New: - transform does not accept zero argument Source

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=22167>.
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=22167

transform does not accept zero argument Source

           Summary: transform does not accept zero argument Source
           Product: XalanJ2
           Version: 2.5
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: org.apache.xalan.transformer
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: jonathan.gray@netdecisions.com


I have an XSL which gets multiple XML inputs using the document() function 
specified in the XSL file.  The XML files are specified as parameters to the 
XSL. This means that there is no one XML source that needs to be passed to the 
Transformer.transform(...) method.

According to the Source documentation (Stream/SAX/DOM) any zero argument 
constructed instance should represent the empty XML tree.  However, when I 
pass, for example, a 'new SAXSource()' into Transformer.transform(...) the 
following exception is thrown.

java.lang.NullPointerException
	at org.apache.xml.dtm.ref.DTMManagerDefault.getDTM
(DTMManagerDefault.java:325)
	at org.apache.xalan.transformer.TransformerImpl.transform
(TransformerImpl.java:658)
	at org.apache.xalan.transformer.TransformerImpl.transform
(TransformerImpl.java:1129)
	at org.apache.xalan.transformer.TransformerImpl.transform
(TransformerImpl.java:1107)
	at com.netdecisions.mbs.struts.TemplateAction.execute(Unknown Source)

I get a similar exception using the resin XSLT library, I haven't tried using 
Saxon.

My expectation is that this should work, if there's a reason why this 
expectation is wrong it should be documented in the Xalan API.