Re: JavaXML.framework Question
Re: JavaXML.framework Question
- Subject: Re: JavaXML.framework Question
- From: Dov Rosenberg <email@hidden>
- Date: Fri, 17 Apr 2009 07:38:40 -0400
- Thread-topic: JavaXML.framework Question
Title: Re: JavaXML.framework Question
The problem has been around since we started deploying apps as servlets going back several years now. I think it might have something to do with this snippet I found in the Tomcat docs ( http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html)
...
For some classes (such as the XML parser components in J2SE 1.4+), the J2SE 1.4 endorsed feature can be used (see the common classloader definition above). Last, any JAR containing servlet API classes will be ignored by the classloader.
...
The javaxml framework contains javax.servlet.http.* classes. I suspect that in a servlet deployment this is causing the javaxml framework to be ignored. These classes are probably needed when running as a regular WOA application in JavaMonitor if you are using the built in web services functionality. I am going to try removing them today and see if that helps – hopefully the house of cards wont fall down.
Dov Rosenberg
On 4/17/09 12:40 AM, "Jake MacMullin" <email@hidden> wrote:
I've encountered this same problem (sans-wonder) when deploying WebObjects applications built as WARs to Tomcat, JBoss (with a Tomcat servlet container) and Glassfish application servers - though not with Jetty.
I'd really like to know more about what might be causing this problem and what the solution is. I suspect that it might be due to incompatibilities between versions of java libraries included within the javaxml.jar and different versions of the same libraries provided by the various application servers. I'm currently seeing if I can figure out exactly what is causing this problem as it is a serious issue if we're unable to deploy to JBoss/Tomcat as that's our current server set-up.
I first noticed this problem with WO 5.4.x (sans-wonder).
Regards,
Jake
On Wed, Apr 15, 2009 at 2:18 AM, Dov Rosenberg <email@hidden> wrote:
Yes, we have swapped over to Wonder a few months ago. I have run into this prior to Wonder though.
Dov
On 4/14/09 12:01 PM, "David Avendasora" <email@hidden <http://email@hidden> > wrote:
Hi Dov,
Are you using Wonder with your Tomcat servlet apps? I've run into some classpath weirdness with running the two together. The weirdness I see is different from what you are running into, but maybe they are related...
Dave
On Apr 14, 2009, at 11:39 AM, Dov Rosenberg wrote:
We deploy our apps as servlets in Tomcat. We have been deploying them that way for the past few years. Recently I have been updating our build scripts to steamline them. For some reason even though we include the javaxml.jar (from the JavaXML.framework) in our WEB-INF/lib folder the Tomcat class loader can’t seem to find classes that I can see in the jar. For example at startup if I don’t include xercesImpl.jar in my WEB-INF/lib along side javaxml.jar I will see the following error
java.lang.NoClassDefFoundError: org/apache/xml/serialize/OutputFormat: org/apache/xml/serialize/OutputFormat
That class is in both the xercesImpl and javaxml.jar’s
The same seems to apply for the xalan, axis, wsdl, etc classes. Should we be deploying the JavaXML.framework at all? It seems that if we do not the webservices functionality built into WebObjects gets broken. Seems like a waste to deploy all of these duplicate wars.
Thanks in advance for any feedback
Dov Rosenberg
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden <http://email@hidden> )
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden <http://email@hidden>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden