Eclipse Community Forums: Eclipse Scout » Scout Axis Support to be replaced by JAX-WS Support

Help

Home

Home » Eclipse Projects » Eclipse Scout » Scout Axis Support to be replaced by JAX-WS Support

Show: Today's Messages :: Show Polls :: Message Navigator

Scout Axis Support to be replaced by JAX-WS Support [message #691355]

Fri, 01 July 2011 09:39

Matthias Zimmermann

Messages: 208
Registered: June 2015

Senior Member

For the Scout 3.8.0 Juno release we consider to deprecate the Scout Axis webservice support and replace it with JAX-WS support.

If this creates serious issues on your side, please let us know until end of August 2011.

Report message to a moderator

Re: Scout Axis Support to be replaced by JAX-WS Support [message #692939 is a reply to message #691355]

Tue, 05 July 2011 14:01

Adrian Moser

Messages: 67
Registered: March 2011

Member

What do you recommend when implementing a web service with Scout today?
- using the current Axis-based solution and migrate to JAX-WS later
- use JAX-WS without Scout Support today

Will it be difficult to migrate to JAX-WS from Axis?

Report message to a moderator

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.

Report message to a moderator

Re: Scout Axis Support to be replaced by JAX-WS Support [message #697457 is a reply to message #693540]

Sat, 16 July 2011 20:48

Adrian Moser

Messages: 67
Registered: March 2011

Member

Thanks Daniel.

One more question: Will Scout support JAX-WS "code first" service design?

Report message to a moderator

Re: Scout Axis Support to be replaced by JAX-WS Support [message #698818 is a reply to message #697457]

Wed, 20 July 2011 09:45

Daniel Wiehl

Messages: 1
Registered: May 2016

Junior Member

Hi Adrian

This will be implemented soon. If you have any input on that, please report this on bugzilla ticket 350517 which you can find at https://bugs.eclipse.org/bugs/show_bug.cgi?id=350517.

Report message to a moderator

Re: Scout Axis Support to be replaced by JAX-WS Support [message #718601 is a reply to message #698818]

Wed, 24 August 2011 20:01

Adrian Moser

Messages: 67
Registered: March 2011

Member

Thanks, I have added a comment on that ticket.

Basically I suggest just to enable the JAX-WS code first approach - since JAX-WS already handles creating the WSDL out of the POJO.

Report message to a moderator