This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes Web Services and the fly likes Default implementation of Sun's web service specification? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Default implementation of Sun Watch "Default implementation of Sun New topic
Author

Default implementation of Sun's web service specification?

shai ban
Ranch Hand

Joined: Jan 05, 2010
Posts: 177
What is the default implementation of Sun's web service specification? And how I can start with it (Any book)?
Instead of various frameworks (Axis2/CXF etc), one should learn the default implementation that these frameworks are supposed to follow. Any comments?

Thanks.
shai ban
Ranch Hand

Joined: Jan 05, 2010
Posts: 177
anybody (
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 41040
    
  43
What is the default implementation of Sun's web service specification?

Are you asking about SOAP or REST? It would be Jersey for JAX-RS, and Metro for JAX-WS.

Instead of various frameworks (Axis2/CXF etc), one should learn the default implementation that these frameworks are supposed to follow. Any comments?

Yes - I totally disagree with that statement. The whole point of specifications is that it shouldn't matter which implementation you use - they're functionally equivalent. There may be good reasons to choose some other implementation than the reference one (performance, ease of use, tooling, experience you already have etc.); the reference implementation is definitely not always the best choice. Both Metro and Jersey are perfectly fine for production use, though. Personally, I'd choose Jersey for JAX-RS and Axis-2 for JAX-WS.


Ping & DNS - my free Android networking tools app
shai ban
Ranch Hand

Joined: Jan 05, 2010
Posts: 177
You are 100% correct Dittmer. Sorry for my bad sentence formation. I meant to say, one should learn the default implementation so that one may know what specification expects. Generally, frameworks provide extra functionalities that people may consider the expected behavior from specification.
2nd point is, if one is interested for web service certification then it asks from Metro/Jersey only not Axis2/CXF.

2nd point is very important to me. Could you please let me know some reference for Metro except the online documentation that is vast. Any particular book on it?

Thanks a lot.
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 41040
    
  43
shai ban wrote:I meant to say, one should learn the default implementation so that one may know what specification expects.

That still doesn't sound right. The specification is independent of any implementation.

if one is interested for web service certification then it asks from Metro/Jersey only not Axis2/CXF.

I can only hope that the certifictaion exam does not suppose knowledge of any specific implementation. That would be a badly designed exam, IMO.
shai ban
Ranch Hand

Joined: Jan 05, 2010
Posts: 177
Correct. Specification is independent of ANY implementation.

Certification expects from Metro/Glassfish only. Any book?
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: Default implementation of Sun's web service specification?
 
Similar Threads
Client AXIS Handler & XML Signature
unknown protocol - https
difference between restful webservice and jersey webservice
Hibernate vs JPA (ORM techniques) - Dubious concept
Confusion of java web services implementation terminology