Okay, I've been here several times before. Essentially Websphere Server provides its own SOAP implementation based on SAAJ 1.1 Axis 1.2RC2 uses SAAJ 1.2. One of the jars that the Websphere container loads is SAAJ1.1.jar
When your axis.war gets loaded by default SAAJ1.1.jar is the first place WS looks for the org.w3c.dom.Document interface. org.apache.axis.SOAPPart implements the org.w3c.dom.Document interface found in saaj1.2.jar (located in your axis.war). So the trick is to make it look at the place you want it to. First you want to open the server perspective (click the open a perspective button in the upper left of the workspace, select other and find server). Now, in the server configuration panel (lower left), find the server that you are deploying the Axis.war (a.ear) to. Double click on that server and a deployment editor should come up. Click on the applications tab and highlight your EAR. Make sure that under the WAR classloader policy dropdown, you select module. Now drill down to your war on the left side and highlight it. On the right make sure that classloader mode is PARENT_LAST. Save your changes, restart the server and try running your tests again. It should work this time. -----Original Message----- From: babloosony [mailto:[EMAIL PROTECTED] Sent: Monday, January 31, 2005 6:29 AM To: [EMAIL PROTECTED] Subject: Axis Gurus - Please help .. Urgent .... Issue with Document class ??? Hi, I have successfully developed and deployed an EJB using WSAD 5.1.2's WebSphere 5.0 Test Environment. I have even able to access the EJB using UTC(Universal Test Client) in WSAD and by launching the j2ee client module using WebSphere lauchClient program. Basically I have below directory structure: a.ear --|-----axis.war -----------|------ lib --------------------|--- all axis related jars are here --|-----demoEjb.jar (has java jar dependencies set to axis.war\lib jars I have now exposed this ejb as web service using AXIS 1.2 RC2 deployed as web module inside WSAD. This web service is properly exposed as web service as I can see it and access its wsdl when I access axis web services. Now I have written a standalone-outside-wsad web service client that uses AXIS stubs and when I try to consume to this ejb web service I am getting below error. AxisFault faultCode: {http://xml.apache.org/axis/}HTTP faultSubcode: faultString: (500)Internal Server Error faultActor: faultNode: faultDetail: {}:return code: 500 Error 500: class org.apache.axis.SOAPPart does not implement interface org.w3c.dom.Document {http://xml.apache.org/axis/}HttpErrorCode:500 (500)Internal Server Error at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:663 ) at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:94) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java: 32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:147) at org.apache.axis.client.Call.invokeEngine(Call.java:2719) at org.apache.axis.client.Call.invoke(Call.java:2702) at org.apache.axis.client.Call.invoke(Call.java:2378) at org.apache.axis.client.Call.invoke(Call.java:2301) at org.apache.axis.client.Call.invoke(Call.java:1758) I read somewhere with axis mailing lists that it is problem related to axis's saaj.jar and wsad's websphere 5.0 test environment's webservices.jar so I even replaced my wsad installation's D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v5\lib\webservices.jar with saaj.jar but this did not help and even I have added an references to saaj.jar usign wsad's websphere 5.0 test environment environment tab->ws.ext.dirs property and even this did not help. Can anyone please tell me why is error occurring and how to solve it ? Thanks & Regards, Kumar.
