1. JDK 1.3 can't cause any problems in theory because it does not provide any XML library. If you have problems, something else must be the reason.
2. Be sure, that in TOMCAT_HOME/common/endorsed are *exactly the same* libraries as in COCOON_HOME/WEB-INF/lib. And this does only work if you use the default startup scripts delivered with TOMCAT. If you don't use them you have to add -Djava.endorsed.dirs=/your/path/to/the/endorsed/libs when starting the Java process. This is the option TOMCAT sets in its start scripts to TOMCAT_HOME/common/endorsed.
If you switch between Xalan/Xerces versions you must exchange the libraries both in TOMCAT_HOME/common/endorsed and COCOON_HOME/WEB-INF/lib.
3. Test if you really use the XML libraries you think, use Xalan's environment check for it: http://xml.apache.org/xalan-j/faq.html#faq-N1005C. Try the stylesheet, it's easier. Of course you must use Xalan for it, not XSLTC. XSLTC does not support Xalan extension function which is used for the environment check.
4. The hardest test for XSLT processors I know are the DocBook stylesheets. If a Xalan version works with those stylesheets it's /approved/. ;-) I don't see a difference between both (using Xalan, not XSLTC), both have a bug with the auto index generation. But of course if you use any specific thing that has changed between both versions, it's possible that 2.5.1 has problems that 2.4.1 does not have. But for most use cases it works, so Cocoon uses the most recent ones. If you have a specific problem, then you must switch back to the old version in your installation; we can't force all users to switch back. Furthermore this helps the Xalan team to fix recent bugs. If you think you know of one, post it at bugzilla.
5. More stuff to read:
http://wiki.cocoondev.org/Wiki.jsp?page=NoMoreDtmIdError
http://wiki.cocoondev.org/Wiki.jsp?page=EndorsedLibsProblem (including an alternative for never having any endorsed libs problem anymore :-) )
6. The stacktrace is typical for endorsed libs problem - and often seen.
Regards,
Joerg
Olivier Billard wrote:
I think it may come from the JDK that was installed (1.3.1), that may cause problems with xalan-xsltc. Classic xalan works well
With a JDK 1.4, all works well
Yury Mikhienko wrote:
May be xalan-2.5.1 is not quite up yet?
My pb seemed to come from Apache and its class-loader.
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.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
