This week's book giveaway is in the Mac OS forum.
We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line!
See this thread for details.
The moose likes Web Services and the fly likes web services portability Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Java » Web Services
Bookmark "web services portability" Watch "web services portability" New topic
Author

web services portability

Greg T Robertson
Ranch Hand

Joined: Nov 18, 2003
Posts: 91
Exactly how portable are web services (both server & client side). After spending many months on developing a true document based web service on the Axis stack, the team I was on was looking at porting it to the Websphere stack (WAS 5.1). However it does not appear that it supports a true document based service (where our method expects a Document as the parameter). What are the "best practices" for migration of web services - or is web services going to lead to vendor lock in?
Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8919

I dont think porting WS is easy unless you use J2EE complaint containers , assuming you are implementing in java.


Groovy
Kostya Razumovsky
Greenhorn

Joined: May 02, 2004
Posts: 23
Doesn't WAS 5.1 supports Apache Axis as one of the SOAP implementations? New WAS 5.1 engine really doesn't support pure document-oriented services in the Axis manner. It is still possible to send arbitrarily XML in acordance with JAX-RPC rules.

As far as I understand it is one of the goals of the JAX-RPC specification to provide web services portability across vendors. Now if yo� create JAX-RPC compatible web services (and clients) you may be sure your services are portable (across JAX-RPC compatible runtimes).


Lots of things become clear, when you stop thinking /Viktor Pelevin/
Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8919

As far as I understand it is one of the goals of the JAX-RPC specification to provide web services portability across vendors. Now if yo� create JAX-RPC compatible web services (and clients) you may be sure your services are portable (across JAX-RPC compatible runtimes).


Yes you are right but how do I port to .NET Web Service container.
Greg T Robertson
Ranch Hand

Joined: Nov 18, 2003
Posts: 91
Kostya you are correct about WAS 5.1 supporting Axis and it will. But then you don't get the additional benefits being provided like easily implemented security etc that exist on the WebSphere stack. I think regardless of the containter (and yes we are using J2EE Compliant containters) I was surprised at the amount of work that would need to go into migrating from the Axis stack to the WebSphere stack (especially the document issue)
Kostya Razumovsky
Greenhorn

Joined: May 02, 2004
Posts: 23
Originally posted by Pradeep Bhat:


Yes you are right but how do I port to .NET Web Service container.


I wonder how you are going to port Java web service to .NET...

Anyway the porting process may be automated... E.g. WSAD 5.1 allows you to generate all the depoloyment artifacts and web service skeleton from WSDL. Though I am not sure you will be happy with this staff if you used document-style Axis web service...

But nothing to do - Axis was a particular SOAP imlementation, which appeared when there were no standard approach to J2EE web services. The only way for creating portable code is sticking to standards (JAX-RPC and JSR 109). Once you implement these standards you won't have any portability problems in future. In theory.
[ June 16, 2004: Message edited by: Kostya Razumovsky ]
 
GeeCON Prague 2014
 
subject: web services portability