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 2002/05/22 14:54:16 UTC

DO NOT REPLY [Bug 9312] New: - XSLT should return errors in an architected structure

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

XSLT should return errors in an architected structure

           Summary: XSLT should return errors in an architected structure
           Product: XalanJ2
           Version: 2.0.0
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: org.apache.xalan.xsltc
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: clau@ca.ibm.com


The compile/warning errors returned by XSLTC when compiling a vector of files 
is a vector of strings with various file names embedded inside it. This makes 
it very hard to use in a tooling environment. For example, this is what I got:

file:/F:/.../Order.xsl Unable to resolve call to functions abc...
file:/F:/.../Abc.xsl ...
Type check error in cast(variable-ref..).
...

I would like to get an architected interface where I can ask for the file info 
on each error. I don't know which string have URI, which string does not.