Axis2 requires Java 1.5 and in that version, all the APIs defined by xml-apis are already included in the JRE. Therefore xml-apis is no longer necessary. Also note that the fact that the problem disappears after adding xml-apis to the WAR doesn't necessarily mean that the removal of the JAR in Axis2 1.5.x is the cause of the problem.
The difficulty with class loading issues is that there are so many variables that it is virtually impossible to debug them from a distance. The first thing you should do is to realign your setup with the guidelines for deployment on WebSphere given in [1]. Andreas [1] https://builds.apache.org/job/Axis2/site/docs/app_server.html#WebSphere On Wed, Nov 23, 2011 at 22:40, Jack Sprat <rexclaim...@yahoo.com> wrote: > We have a situation in Websphere 6.1 where there is a class loading problem > with an Axis2 1.5.2 web service. The class loading is set to PARENT_LAST on > the web app. That is the first thing I always do with Axis2 web services > running on Websphere. > We've determined that the class loading problem comes from the fact that > classes are missing that were in prior versions of Axis2. These were in the > xml-apis-1.3.04.jar file in Axis2 version 1.4.1. The specific class causing > the problem is org.w3c.dom.Notation. It is no longer present in the Axis2 > 1.5.2 WAR and causes a linkage error. > > Manually adding the xml-apis-1.3.04.jar file from the Axis2 1.4.1 > distribution to the Axis2 1.5.2 web application cures the problem. > Why was this JAR removed in newer versions? How do I get around this error, > apart from manually adding a JAR from a prior distribution? There must be a > better way. > > Any guidance is appreciated. > Thanks, > J > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org
