|
Dear,
From your mail I get that u have added axis jars in server classpath. I.e. your WSAD configured server. Am I right? I don’t want you to put the axis jars in server classpath. Just include the jar files in your WEB-INF/lib directory and automatically as per the war structure, ur axis classes will be loaded.
As for the explanation, say if you have same 2 classes in same package structure, but in different jars and both classes have diff logic of itself, then the classloader doesn’t understand which class to load and you get your exception.
Now including the classes in your war structure will have a different loader for the app, so your problem will be solved.
Let me know if you need more information for the same. If you want I can send you a sample war structure of web service deployment, which doesn’t require any special server configuration. Thanks & Regards From: Dorner, Thomas
[mailto:[EMAIL PROTECTED]
Hi Pranay Parsatwar,
Thank you for your reply - but I don't understand what you mean.
I am starting websphere out of my IDE (WSAD) so I can change the order of my jars, but it doesn't change anything.
I do not want to include my classes in a jar (service.jar), because I will debug the classes in my IDE when websphere running.
Do you have an idea form y problem???
Thanks in advance Thomas
Von: Pranay
Parsatwar [mailto:[EMAIL PROTECTED]
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
|
