Re: Tomcat Xalan classpath problem

2009-11-06 Thread Rainer Jung
On 06.11.2009 03:22, Benson Margulies wrote: i don't suppose you've had time to look at the test case? Done, unfortunately worksforme :( - or should I write :) ? See https://issues.apache.org/bugzilla/show_bug.cgi?id=48116 What's next? Regards, Rainer P.S.: Are you at ApacheCon? On Tue,

Re: Tomcat Xalan classpath problem

2009-11-05 Thread Benson Margulies
i don't suppose you've had time to look at the test case? On Tue, Nov 3, 2009 at 9:22 AM, Rainer Jung rainer.j...@kippdata.de wrote: Just to make sure w.r.t. it being working in Jetty: You use the same Java version? Sun changed an important bit between Java 5 and Java 6, where they are now

Tomcat Xalan classpath problem

2009-11-03 Thread Benson Margulies
I have a webapp that makes calls to the JAXP 1.4/Java 1.6 APIs that allow the caller to pass in the class name of implementation classes. It all works find standalone. It works fine in Jetty. It fails in Tomcat 6.0.20. The error is a missing method in a Xalan class; as if Tomcat has somehow

Re: Tomcat Xalan classpath problem

2009-11-03 Thread André Warnier
Benson Margulies wrote: I have a webapp that makes calls to the JAXP 1.4/Java 1.6 APIs that allow the caller to pass in the class name of implementation classes. It all works find standalone. It works fine in Jetty. It fails in Tomcat 6.0.20. The error is a missing method in a Xalan class; as

Re: Tomcat Xalan classpath problem

2009-11-03 Thread Benson Margulies
Here's the relevant log traffic of the missing method. I can get past this problem by putting xalan into the endorsed directory, but I should not have to do that when using the JAXP 1.4 API to create XPathFactory. Caused by: java.lang.NoSuchMethodError: org.apache.xpath.XPathContext.init(Z)V

Re: Tomcat Xalan classpath problem

2009-11-03 Thread Rainer Jung
Just to make sure w.r.t. it being working in Jetty: You use the same Java version? Sun changed an important bit between Java 5 and Java 6, where they are now caching something detected during runtime in a global static thus partially breaking the dynamics of XML parser detection when using mutiple

Re: Tomcat Xalan classpath problem

2009-11-03 Thread Benson Margulies
I am sure that I'm using the MacOS JDK 1.6 at all points. Also, if you look closely at the below, you will see that the problem is that one part of Xalan is failing to call another part ... of Xalan. If I had JDK 1.5 I'd be missing the newInstance APIs that take the class name, and if I had other

Re: Tomcat Xalan classpath problem

2009-11-03 Thread Benson Margulies
I've attached a self-contained test case to bz 48116, so you can see this for yourself. On Tue, Nov 3, 2009 at 9:22 AM, Rainer Jung rainer.j...@kippdata.de wrote: Just to make sure w.r.t. it being working in Jetty: You use the same Java version? Sun changed an important bit between Java 5