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

MalformedURLException for relative xsl:include

           Summary: MalformedURLException for relative xsl:include
           Product: XalanJ2
           Version: 2.3Dx
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: org.apache.xalan.xsltc
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


I use a stylesheet with the following xsl:includes
        <xsl:include href="./intranet/war/style/global.xsl" />
        <xsl:include href="./intranet/war/style/global_scr.xsl" />
It gets used from a jsp-page with my own xsl-taglibrary (based on jakarta-xsl
taglib, but uses xalan-j2-api). This creates and caches Transformer objects.
I've now added 
-Djavax.xml.transform.TransformerFactory=org.apache.xalan.xsltc.trax.TransformerFactoryImpl
to my java invokation to try the xslt-compiler. When invoking the first page I get
java.net.MalformedURLException: no protocol: 
        at java.net.URL.<init>(URL.java:579)
        at java.net.URL.<init>(URL.java:476)
        at java.net.URL.<init>(URL.java:425)
        at org.apache.xalan.xsltc.compiler.Include.parseContents(Include.java:111)
        at 
org.apache.xalan.xsltc.compiler.Stylesheet.parseOwnChildren(Stylesheet.java:388)
        at 
org.apache.xalan.xsltc.compiler.Stylesheet.parseContents(Stylesheet.java:360)

I currently have a look at the code and trying to find out what is the
difference between the URL-handling in
  src/org/apache/xalan/xsltc/compiler/Include.java
and
  src/org/apache/xalan/processor/ProcessorInclude.java

Stefan

Reply via email to