Joel John wrote:I have another long term requirement also....sometimes down the line, I want to move that service to Websphere without any effor or with minimal effort...If I have it as War, it will be easy to move to websphere.
Neither JAX-WS or its pre-decessor JAX-RPC have a deployment concept of a "web service component" that is equivalent to that of a "web component". The specifications simply describe the API and configurations that an environment for building
Java web service providers and consumers has to support - and there are gaps that implementing platforms fill in a platform dependent manner. So its likely that you will have to at the very least recompile your code under another API implementation. To be sure that you can move your code later, you better plan ahead and
test it now under both platforms.
Furthermore Axis2 implemented JAX-WS on top of its own web service API architecture rather than designing an "optimal" architecture for supporting the JAX-WS spec.
Java SE 6 supports JAX-WS and the endpoint is published programmatically with a statement like:
not of a trace of a "web service component" - just a "plain" Java class. (See
Confusion in writing web service client + jax-ws. Keep in mind that
wsgen and
wsimport could generate source code that is dependent on the implementing web services platform.)
Do you have a particular reason for using Axis 2 rather than Sun's JAX-WS implementation?
JAX-WS 2.0 Samples on Tomcat 5.5.x
Running JAX-WS Samples with Tomcat 6.x