|
|
Re: Scout Axis Support to be replaced by JAX-WS Support [message #693540 is a reply to message #692939] |
Wed, 06 July 2011 17:35 |
Daniel Wiehl Messages: 1 Registered: May 2016 |
Junior Member |
|
|
Basically, webservice stubs generated by Axis cannot be migrated to JAX-WS in an easy manner. Thereto, you have to generate the WS stub in JAX-WS anew, which actually is very easy in Scout SDK. The support for JAX-WS in Scout and Scout SDK is still in incubation, which is why this implementation is not public yet. After generating the JAX-WS stub, the business logic of the Axis provider can simply be copied into the JAX-WS provider implementation. Only references to stub objects such as request and response objects have to be resolved all over again. Also, if you did some session management, transaction control and authentication in your WS implementation, in JAX-WS Scout integration, this is done by the framework itself. Meaning, that you only have to annotate your webservice implemenation class of how to deal with thing like that. So when migrating Axis webservices to Scout JAX-WS, this glue code can also be removed. Furthermore, WS handlers must be rewritten. Even though the concept of handlers is the very same in both implementations, some refactoring would be necessary.
I would suggest to develop your webservices still with Axis unless you make heavily use of webservices. In such situation, it might be useful / easier to take our internal, pre-released JAX-WS integration.
If you have any further questions, please let us know.
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03248 seconds