|
Hi Thomas,
I just figured out where is the Webshpere specific
classpath. I added an external jar file and pointed to the Axis
1.2RC1\lib\saaj.jar and.... magicaly it worked. Thanks a
lot.
For anyone who doesn't know where is the Websphere specific
classpath, you can set it up when you go to the server configuration and then to
the environment tab. in there you'll find ws.ext.dirs which is
the Websphere Specific Class path. add the external jar in
there.
So now I have a new question for anyone with some
experience about this issue. Obviously, the webservice I'm developing will go to
production at some point and I'm guessing that the production server (running
Websphere Application Server 5.0.2) doesn't have the latest saaj.jar. Is it
possible to replace the saaj.jar on the server or is it possibly going to affect
existing web services already runing on it?
Thanks
again,
--
AV
From: Dorner, Thomas [mailto:[EMAIL PROTECTED] Sent: Friday, November 12, 2004 2:06 AM To: '[EMAIL PROTECTED]' Subject: AW: Axis 1.2RC1 and WebSphere Application Developer 5.1.2 Hi
AV, you problem is the
saaj.jar - the saaj.jar in the AXIS 1.2RC1 release is newer then that one in
Websphere. So you must told your
websphere to use the saaj.jar in your webapp! For example set the
Classpath and the "Websphere specific Classpath" in your
WSAD: C:\projects\sources\....\WebContent\WEB-INF\lib\saaj.jar This should solve your
problems Thomas Von: Levy, Avi
[mailto:[EMAIL PROTECTED] Hi, I'm
new to Axis 1.2RC1. I followed the installation instructions from the website to
setup an Axis server on my local WebSphere Application Developer 5.1.2 (WSAD)
using WebSphere 5.1 test environment. Everything goes ok and the AxisServlet is
running and I can get back the Version by using WSAD's web service
explorer. As
soon as I try to run any of the samples on the user guide I keep getting the
same exception no matter how I tweak the server and client settings and
classpaths. Here is the trace I get on the
server: [11/11/04
15:50:54:694 CST] 22299d1b WebGroup E SRVE0026E:
[Servlet Error]-[class org.apache.axis.SOAPPart does not implement interface
org.w3c.dom.Document]: java.lang.IncompatibleClassChangeError: class
org.apache.axis.SOAPPart does not implement interface
org.w3c.dom.Document
at
org.apache.axis.message.MessageElement.addTextNode(MessageElement.java:1388)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:988)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java(Compiled
Code))
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:333)
at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
I
get the same exception when I try to run the supplied clients for each example
and also when running WSAD web services explorer. I
also tried to change the order of the build path by putting the Axis jars before
any other jars. I
first created the clients on the same project as the Service classes (so they
use the same Axis jars) but when it didn't work I also created the clients on
separate projects, but that didn't work either. No matter what I do I keep
getting the same exception. I have the feeling that it's something stupid
related to overlaping jars, but I couldn't find it. Thanks for your help,
--
AV |
Title: Axis 1.2RC1 and WebSphere Application Developer 5.1.2
