All, In our project we are running our application in two container. Tomcat Weblogic.
We are accessing the Web service given by client, by generating the client stub codes from WSDL. To create the client stub code, we used WSDL2Java utility along with Apache Axis.
For Weblogic it seems to use the above generated code we need the Apache axis related jar file inside weblogic. which we don't want to do it.
Is it possible to have a generic web service client which we can use across container instead of deploying the application along with dependent jar file.
If i was wrong please clarify it.
posted 7 years ago
Originally posted by Parameswaran Thangavel: Is it possible to have a generic web service client which we can use across container instead of deploying the application along with dependent jar file.
Not with most WSDL-to-Java code generators as they will generate code that will often reference components from their specific platform for the purpose of reuse. Portability of the generated artifacts is rarely an objective. Some teams have used Axis 1.x successfully on WebLogic 8.1 (with difficulty).
For a small and simple WSDL you could possibly write a client from scratch with SAAJ which should run on different SAAJ implementations.