Hi all,
I'd originally sent this to the cocoon-dev list since I wasn't
sure whether it was a Cocoon2 problem or Xalan. It now seems
that, at least part of the issue, resides with xalan.
Some background:
One of the classes within Cocoon2, TraxTransformer, has implemented
the URIResolver interface which I guess basically means adding a
javax.xml.transform.Source resolve(String href, String base)
method. It appears that with nested stylesheets with 3 or more
levels of nesting, the "base" parameter is null rather than
being the systemId (?) of the second stylesheet.
So, here's the forwarded message.
------- Forwarded Message
To: [EMAIL PROTECTED]
Subject: [C2] : Bug with TraxTransformer and URIResolver addition
Date: Mon, 28 May 2001 19:50:40 -0700
From: Rick Tessner <[EMAIL PROTECTED]>
Hi all,
I believe I've found a bit of a bug with the URIResolver addition
to the TraxTransfomer class.
If I have a stylesheet nesting of 3 or more levels, the resolve()
method in TraxTransformer is being passed a null "base" value. The
"href" value is correct. This in turn causes an NPE to be thrown.
This is from cocoon.log:
java.lang.NullPointerException
at
org.apache.cocoon.transformation.TraxTransformer.resolve(TraxTransformer.java:240)
at org.apache.xalan.processor.ProcessorInclude.parse(ProcessorInclude.java:227)
.
:
I have the following stylesheets:
a.xsl "xsl:includes" b.xsl "xsl:includes" c.xsl
I then get the NPE. If I simply have two levels a.xsl and b.xsl,
everything works just fine.
I've been looking at this for a bit and I don't know yet whether this
is a xalan thing or a cocoon2 thing ... (it does happen with
xalan-2.0.1.jar as well as xalan-2.1.0.jar).
Since I don't seem to be getting anywhere with this, I thought
I'd toss it up to the list.
------- End of Forwarded Message
--
Rick Tessner [EMAIL PROTECTED]
MYRA Systems Corp. Fone: (250) 381 1335 x125 Phax: (250) 381 1304
Cell: (250) 885 9452
"Hmmm. They have the Internet on computers now!"
