Hello James,
James Cummings wrote:
Hiya,
I'm really new to cocoon so am probably doing something completely
wrong. But using cocoon 2.1m3-dev, I want to grab a particular
elment by id() from an xml file in the first step of a pipeline,
and convert the result to html in the second step. In each
I'm posting the test-case now. I've discovered (in only the simple case that you'll
see), that the simple case of the stylesheet from the sitemap including one other that
doesn't have its own includes is fine. When the included stylesheet includes yet one
or more stylesheets of its own, that's
Hello Steven,
it's XSLTC who does give so exhaustive messages. Try to use Xalan for
this particular transformation, maybe you get a real error message.
Are you refering external resources from the stylesheet (xsl:import,
xsl:include, document())?
Joerg
Steven Cummings wrote:
Hello,
Is
Joerg,
Yes, in the original message I had attached the stylesheet, which xsl:include'd
another, which xsl:include'd a third stylesheet (I attached all three of them). They
are viewable here:
http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=105467465417098w=2
if your mail client didn't show
Joerg
Well, the tip really worked well. I don't quite get it, but the transform works all of
the sudden. So that leads to the question, is there (and I haven't checked Bugzilla
for Xalan or XSLTC) a bug in XSLTC related to this (maybe includes)? I'll definitely
look into it but if someone
Sorry, I didn't scroll below the start of the exception trace :)
If you don't have a real error in your stylesheets, it will work with
Xalan. xsl:include is probably the reason, it had problems with
resolving relative paths. But we thought the problem is already solved
with the dev version of
sure thing, I'll do that first thing in the morning when I get in.
/S
Joerg Heinicke [EMAIL PROTECTED] wrote:
Sorry, I didn't scroll below the start of the exception trace :)
If you don't have a real error in your stylesheets, it will work with
Xalan. xsl:include is probably the reason, it
