cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Derek Hohls" <dho...@csir.co.za>
Subject Re: Using <xsl:include> in stylesheet throwing error
Date Tue, 20 Dec 2005 06:17:50 GMT
Duncan
 
This sounds like one of the "deeper mysteries" of XSL; best
to take this up with the XSL mailing list - where there are a number
of very clued-up people who could give you much more insight
into the specifics of this problem.
 
See:
http://www.mulberrytech.com/xsl/xsl-list/index.html 
 
Derek

>>> duncan_mclean@blueyonder.co.uk 2005/12/19 10:04 PM >>>
Hi

Thanks for all your help; think we found the problem - is it a case that 
later versions of xalan are more "strict" in what they allow then?

(Basically the problem seems to be an included stylesheet conditionally 
referencing a template which may or may not appear in the outer 
stylesheet if that makes sense!)

Thanks again

Duncan

Geert Josten wrote:

> Put a xalan.jar next to the xsl and call:
>
> java -Xbootclasspath/p:xalan.jar -jar xalan.jar -in in.xml -xsl 
> book.xsl -out out.xml
>
> where you can replace in.xml with book.xsl if you have no input xml at 
> hand..
>
> :-)
>
> Cheers
>
> PS: the bootclasspath parameter makes sure that you are using the 
> xalan.jar you are providing yourself, not the one that is installed 
> with JDK.
>
> Duncan McLean wrote:
>
>> Hi
>>
>> Thanks for this, can someone explain how to run the command line check
>> please as I am not sure how to manually check.
>>
>> Thanks again.
>>
>>
>>
>>> In case, is it not more likely that stylesheet itself was the
>>> source of the problem - in which case Geert's suggestion
>>> of a command line test should help you pin down the
>>> cause in more detail.
>>>
>>>
>>>>>> duncan_mclean@blueyonder.co.uk 2005/12/19 02:53 PM >>>
>>>>>
>>>
>>> Hi
>>>
>>> We commented out the "offending" xsl:include and the page rendered.
>>>
>>> Thanks
>>>
>>>
>>>> FWIW, I also migrated to 2.1.7 (but not from 2.0.4);
>>>>
>>>> I have:
>>>>
>>>> <map:transformers default="xslt"/>
>>>>
>>>> in the map:components section, and
>>>>
>>>> <map:transform src="filename.xsl">
>>>>
>>>> i.e. no "type=" as an attribute...
>>>>
>>>> what leads you to think the xsl:include s are the
>>>> source of the problem?
>>>>
>>>>
>>>>>>> Geert.Josten@daidalos.nl 2005/12/19 01:59 PM >>>
>>>>>>
>>>>
>>>> Are you sure that there is no syntax error in the XSLT that was not
>>>> spotted by an earlier version of
>>>> Xalan, but is with a later one? Try applying the stylesheet to 
>>>> itself on
>>>> a
>>>> command-line to get a
>>>> syntax check.
>>>>
>>>> Cheers,
>>>> Geert
>>>>
>>>> duncan_mclean@blueyonder.co.uk wrote:
>>>>
>>>>
>>>>> Hi
>>>>>
>>>>> We are currently attempting to move applications from v2.0.4 to 
>>>>> v2.1.7
>>>>> and
>>>>> have noticed that stylesheets containing xsl:includes are failing 
>>>>> where
>>>>> they functioned perfectly well pre-migration.
>>>>>
>>>>> The error we get is:
>>>>>
>>>>> Caused by: org.apache.cocoon.ProcessingException: Unable to get
>>>>> transformer handler for
>>>>> file:/usr/local/apache/jakarta-tomcat-5.5.9/webapps/content/content/www.brokerzone.ie/xsl/bzcontent.xsl:

>>>>>
>>>>> org.apache.excalibur.xml.xslt.XSLTProcessorException: Exception in
>>>>> creating Transform Handler
>>>>>
>>>>> Cocoon runs under Tomcat (v5.5.9) in our case.
>>>>>
>>>>> I have seen a number of threads that suggest that it could be
>>>>> xalan/xsltc
>>>>> and so have tried changing the transformer type in the sitemap 
>>>>> pipeline
>>>>> from:
>>>>>
>>>>> <map:transform type="xslt"...
>>>>> to
>>>>> <map:transform type="xsltc"...
>>>>> and have also tried
>>>>> <map:transform type="xalan"...
>>>>>
>>>>> however this does not solve the problem.
>>>>>
>>>>> We have copied the latest xalan & xerces distribution jars to the
>>>>> endorsed
>>>>> directory of Tomcat to no avail.
>>>>>
>>>>> Anyone know how we can get round this problem?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Duncan
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org 
>>>>> For additional commands, e-mail: users-help@cocoon.apache.org 
>>>>>
>>>>>
>>>>
>>>> -- 
>>>> Drs. G.P.H. Josten
>>>> Consultant
>>>>
>>>>
>>>>
>>>> Daidalos BV
>>>> Source of Innovation
>>>> Hoekeindsehof 1-4
>>>> 2665 JZ Bleiswijk
>>>> Tel: +31 (0) 10 850 1200
>>>> Fax: +31 (0) 10 850 1199
>>>> www.daidalos.nl 
>>>>
>>>>
>>>> De informatie - verzonden in of met dit emailbericht - is afkomstig 
>>>> van
>>>> Daidalos BV en is
>>>> uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
>>>> onbedoeld
>>>> hebt ontvangen, verzoeken
>>>> wij u het te verwijderen. Aan dit bericht kunnen geen rechten worden
>>>> ontleend.
>>>>
>>>> ---------------------------------------------------------------------



-- 
This message is subject to the CSIR's copyright, terms and conditions and
e-mail legal notice. Views expressed herein do not necessarily represent the
views of the CSIR.
 
CSIR E-mail Legal Notice
http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html 
 
CSIR Copyright, Terms and Conditions
http://mail.csir.co.za/CSIR_Copyright.html 
 
For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR
Legal Notice send a blank message with REQUEST LEGAL in the subject line to
HelpDesk@csir.co.za.


This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message