Tomcat in standalone mode seem to work...
For the exception you mentioned, I met this error today and it worked when I changed back default Transformer to "xalan"...
Yury Mikhienko wrote:
In additional: if I remove the xalan-2.4.1.jar xercesImpl-2.1.0.jar xml-apis.jar from Tomcat endorsed directory (like after the pure Tomcat installation) I get the following error:
2003-07-24 16:56:07 StandardWrapperValve[Cocoon]: Servlet.service() for servlet Cocoon threw exception javax.servlet.ServletException: Servlet execution threw an exception at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) ... ----- Root Cause ----- java.lang.IllegalAccessError: class org.apache.xml.dtm.ref.sax2dtm.SAX2DTM2$AncestorIterator cannot access its superclass org.apache.xml.dtm.ref.DTMDefaultBaseIterators$InternalAxisIteratorBase at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123) at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1679) at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:968) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1409) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1289) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315) at org.apache.xalan.xsltc.dom.XSLTCDTMManager.getDTM(XSLTCDTMManager.java:291) at org.apache.xalan.xsltc.dom.XSLTCDTMManager.getDTM(XSLTCDTMManager.java:174) at org.apache.xalan.xsltc.trax.TransformerHandlerImpl.startDocument(TransformerHandlerImpl.java:232) at org.apache.cocoon.xml.AbstractXMLPipe.startDocument(AbstractXMLPipe.java:83) ... It is VERY strange behavior :(((
but all works fine if I copy into the Tomcat endorsed directory the xalan xercesImpl and xml-apis libs from cocoon/lib But xindice with some XPath expressions do not work correctly with xalan-2.5.1 & xercesImpl-2.4.0 lib's (with xalan-2.4.1.jar xercesImpl-2.1.0.jar all works fine) May be still to early to include the xalan-2.5.1 & xercesImpl-2.4.0 lib's into the cocoon project?
Can anyone say me where I'm wrong? Thanks for all.
Joerg Heinicke wrote:
Is this problem still an issue? Or are all your problems solved with the other thread?Unfortunately not...
When I copy endorsed libs to tomcat from those shipped with Cocoon M3, my page is blank... Some pipelines are working, but other aren't... Especially a pipeline taking
a session parameter. But this one is working with my local tomcat, with the same libs in the endorsed folder.
The webapps are strictly the sames in the 2 PCs. Am I going crazy ?
Olivier Billard wrote:I didn't take this into account. Thanks. But it seem to work, and only in this case...
Hi all !If you put those to Tomcat you should use the same libs in Cocoon. The endorsed libs and the libs used in Cocoon should always be the same. Otherwise there is the risk of getting ClassCastExceptions or strange messages.
I'm trying to port my project based on Cocoon M3 from Window/JDK1.4.1/Embedded Jetty to Linux/JDK 1.4.1/Apache 2.0.46/Tomcat 4.1.24
I'm having some problems I didn't have with Jetty, concerning the ChartTransformer. All seems to work fine.
I'm using the default xsltc transformer. Tomcat has the following libs in common/endorsed :
xalan-2.4.1.jar xercesImpl-2.1.0.jar xml-apis.jar xsltc-20030211.jar
Gasp...The new libs from M3 don't seem to works, neither with no libs...This problem will remain until the XML libs are removed from JDK - and I guess this will never happen. And not only with Tomcat but all environments processing XML.
Is there still some problems with the endorsed libs with this version of tomcat ?
Ok.Must I copy the endorsed libs in an endorsed folder of the JDK ?No. Setting the java.endorsed.dirs property is enough. And exactly this Tomcat is doing in its start scripts.
The app on the server is going to be tested, so I'll try to investigate on this issue after tests.
Thanks anyway, Joerg !
-- Olivier
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-- Olivier BILLARD Société Jouve Tel : 33 2 99 86 93 55 Mail : [EMAIL PROTECTED]
Le présent mail ainsi que toutes les informations qu'il contient ne peuvent en aucun cas être considérés comme un engagement juridique de quelque nature que ce soit de JOUVE. Tout accord devra être formulé par écrit papier ultérieur signé par un représentant légal de JOUVE. Par ailleurs, si vous recevez ce mail par erreur, merci de nous le signaler et de le détruire ainsi que l'intégralité du document qui pourrait y être joint.
The present email and all information included therein do not constitute a legal agreement accorded by Jouve. All legal agreements must be formulated in writing on paper by a legal representative of JOUVE. If you have received this email by mistake, please inform us of that fact and destroy the email and any documents it might contain. Thank you for your cooperation.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
