I got this requirement to migrate my application from Axis to JAX-WS(IBM). I am not sure what does it mean. My application is basically a client application which invokes services deployed somewhere else. I have verified the stub classes and they don't have any axis dependency. So does it mean i dont have to make any chage in my application. Please suggest.
Thanks,
Ajse
Tim Moores
Rancher
Joined: Sep 21, 2011
Posts: 2407
posted
0
ajse ruku wrote:I am not sure what does it mean.
Whom do you usually ask when you need to clarify requirements you got?
ajse ruku
Ranch Hand
Joined: May 06, 2005
Posts: 192
posted
0
So let me rephrase my question. I know Axis is a soap engine. Now JAX-WS should also be doing the same thing. But how its different from Axis and is there any benifits if using JAX-WS ?
thanks,
Ajse
Tim Moores
Rancher
Joined: Sep 21, 2011
Posts: 2407
posted
0
JAX-WS is an API, whereas Axis is an actual implementation, which -amongst other APIs- implements JAX-WS. So contrasting JAX-WS and Axis does not make sense.
If you're looking for other implementations of JAX-WS, check out Metro (which is the JAX-WS RI). All JEE 5 and JEE 6 app servers also come with a JAX-WS implementation.
ajse ruku
Ranch Hand
Joined: May 06, 2005
Posts: 192
posted
0
Thanks Tim, that was useful. So Appserver can create a webservice by their own implimentation of JAX-WS OR use Axis . Is this correct ?
0
