|
Hi,
Me too using Websphere 5.1 for my service and I have never faced this problem. I guess you need to check up how ur deployment process is. I’ll list down my application structure as follows, might be helpful,
WEB-INF web.xml classes ur service classes lib wsdl4j.jar axis-ant.jar commons-discovery.jar commons-logging.jar jaxrpc.jar log4j-1.2.8.jar saaj.jar axis.jar
You also have a way of making a jar file of ur service classes and including that in WEB-INF/lib folder, say service.jar. So your classes folder will not have anything.
I guess if you follow the above structure, you wont get the problem, as WEB-INF/lib folder binary will be working in a different class loaders as of the app server binaries.
Let me know if this helps. Thanks & Regards From: Arijit Mukherjee
[mailto:[EMAIL PROTECTED]
Hi Thomas
I had similar problems (with tomcat though). Tomcat needs all java.* and javax.* classes in TOMCAT_HOME/common/lib or TOMCAT_HOME/common/endorsed. There would probably be something similar in WebSphere. You need to make sure that the jar files in Axis and Websphere are equivalent...
Hope this helps.
Arijit
|
- Websphere 5.1 and Axis rc1 Dorner, Thomas
- WSDL Sequence holding String[0] being received as Se... Silvano Maffeis
- Serializer bug? (Axis 1.2 RC1) Silvano Maffeis
- RE: Websphere 5.1 and Axis rc1 Arijit Mukherjee
- RE: Websphere 5.1 and Axis rc1 Pranay Parsatwar
- RE: Websphere 5.1 and Axis rc1 Pranay Parsatwar
