• Post Reply Bookmark Topic Watch Topic
  • New Topic

Which Web service implementation to use ?  RSS feed

 
Vinod John
Ranch Hand
Posts: 162
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
With so many open source web service implementation available, what is the guide lines you follow to corner down to a single framework ? and how do you rate the individual implementations like Apache SOAP, Axis, JAX-RPC ...
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Here are the approximate guidelines I proceed with selecting a framework/product for running web services:
1) If there's a sufficient product already available, use that (i.e. if the selected application server supports web services)
2) If open source is not a problem for the legal department, use Apache Axis
3) If money is not a problem, use one of WebLogic8/WebSphere5/Oracle9iAS, ordered by the team's experience
4) If money is a problem, use one of SystinetWASP/WebMethodsGLUE, ordered by the team's experience
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A couple of things still:
1) Avoid using Apache SOAP if at all possible -- its successor, Apache Axis is way better and much more interoperable.
2) JAX-RPC is an API, not a product -- for example, Axis implements JAX-RPC.
3) There are no officially J2EE 1.4 compatible appservers out there, yet
 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There are no officially J2EE 1.4 compatible appservers out there, yet

What about Sun RI? Yes, it is not a commercial product but...Lasse any reason for not using it?
 
Vinod John
Ranch Hand
Posts: 162
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In case of Apache SOAP, you are correct I used is 2-3 back when it was a beta, I guess there is no development going on that after Axis came out.
My main question is there any visible performance difference between different webservice implementating be it the JAX-RPC implementation or the one implemented in other language/platform, I guess there should be "absolute ZERO" compatiblilty issue processing messages at each end. And in terms of ease of use which one of the Java based implementation you prefer and why ?.
 
Vinod John
Ranch Hand
Posts: 162
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Lasse Koskela:
2) JAX-RPC is an API, not a product -- for example, Axis implements JAX-RPC.

Did Sun not have a it own stand alone implementation ??? what do they call it ... I thought they named it the same ... I am wrong it is Java WSDP
 
Kishore Dandu
Ranch Hand
Posts: 1934
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
By the way does weblogic7.1 supports web services and comply with Jax-rpc etc.
Kishore.
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Pradeep Bhat:
What about Sun RI? Yes, it is not a commercial product but...Lasse any reason for not using it?
Sure, you could use it. I wouldn't, because I don't trust a reference implementation to be of commercial quality -- it simply isn't built for production use. I could consider the Sun ONE Application Server (or whatever its name is this week ) when the J2EE 1.4 compatible version is released.
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Vinod John:
Did Sun not have a it own stand alone implementation ??? what do they call it ... I thought they named it the same ... I am wrong it is Java WSDP
Yep, the JWSDP... I'm not quite sure how reliable it is. I guess I have always associated it with the "reference implementation" stigma as well.
If anyone is using JWSDP in production, please raise your voice!
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Chris Daniel:
By the way does weblogic7.1 supports web services and comply with Jax-rpc etc.
Yes, it does.
 
Kishore Dandu
Ranch Hand
Posts: 1934
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Lasse,
You remind me of a popular indian tv serial by name "Jasse Jaisa Koi Nahi", it means "there is no one like Jasse".
I would say "Lasse jaisa koi Nahi"
Dan.
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Heh. I'll take that as a compliment
 
Pho Tek
Ranch Hand
Posts: 782
Chrome Python Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If money is a problem, use one of SystinetWASP/WebMethodsGLUE, ordered by the team's experience

How much does WebMethodsGLUE cost anyway, for commercial use? Anyone?
Thanks
Pho
 
Ariel Valentin
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So JAX-RPC may not be implemented on some app servers?
From what I have read about Axis, those classes are implemented in a package named org.apache.client
That seems to loose it's "portability" that way doesn't it?
Because one would have to rewrite code to use javax.xml.rpc when moving it to a non-Axis based engine... right?
RPC Newbie,
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So JAX-RPC may not be implemented on some app servers?

Correct. However, if the app server is J2EE 1.4 compliant, it must implement JAX-RPC. Also, if the app server supports web services at all, it probably supports JAX-RPC before anything else.
From what I have read about Axis, those classes are implemented in a package named org.apache.client
Yes, they are implemented in org.apache.axis.client, but those classes extend/implement the javax.xml.rpc.* API so you shouldn't have problems with portability.
Oh, and would you mind editing your display name a bit -- our naming policy requires both a first name and a last name.
Thanks.
 
Ariel Valentin
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the reply.
Sorry about the naming thing, did not realize the policy requried my "Fully Qualified Name".
Guess that is why I have not won any contests... ;-)
 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Why are vendors slow in implementing WS in J2EE 1.4?
 
Guadalupe Ortiz
Ranch Hand
Posts: 74
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I�m using JWSDP. There is no problem with it, but it might be posible that axis is more intuitive, I dont know because I didnt try it.
gobellot
 
Guadalupe Ortiz
Ranch Hand
Posts: 74
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I�m using JWSDP. There is no problem with it, but it might be posible that axis is more intuitive, I dont know because I didnt try it.
gobellot
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Pradeep Bhat:
Why are vendors slow in implementing WS in J2EE 1.4?
Well, the specification was finalized only three months ago. It's not that uncommon for the vendors to take a number of months for bringing their product up to date with the latest spec. For example, IBM's WebSphere started supporting J2EE 1.3 not until v5.0...
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!