• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Help needed for java web services

 
Ranch Hand
Posts: 177
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I want to start java web services with JAX-RPC/JAX-WS/JAX-RS style and have idea about xml/wsdl/soap. But still have doubts in starting the implementation :
- Which soap implementation (Axis/CXF etc.) I should start with, so that I can easily adapt to other soap implementation after getting one?
- Is there any default implementation to start with instead of switching to vendor specific implementations?
- Is there any book(s) that can provide step by step information on these?

Thanks.
 
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Don't use JAX-RPC, it's way obsolete. JAX-WS is the API to use for SOAP WS these days. JAX-RS implements RESTful WS, so you wouldn't be using that for SOAP, either.

Either Axis-2 or Metro are good choices for getting started with SOAP. There's always a certain degree of incompatibility between SOAP implementations when it comes to deployment and configuration, so switching between them isn't as easy as replacing one jar file with another one. Both should serve you well, though, so most likely there's no reason to switch later.

I'd take a good look at REST (and its reference implementation Jersey) before getting into SOAP, though. RESTful WS are easier to get started with, and more popular nowadays.

Start reading here: WebServicesFaq
 
shai ban
Ranch Hand
Posts: 177
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Ulf Dittmer wrote:Don't use JAX-RPC, it's way obsolete. JAX-WS is the API to use for SOAP WS these days. JAX-RS implements RESTful WS, so you wouldn't be using that for SOAP, either.

Either Axis-2 or Metro are good choices for getting started with SOAP. There's always a certain degree of incompatibility between SOAP implementations when it comes to deployment and configuration, so switching between them isn't as easy as replacing one jar file with another one. Both should serve you well, though, so most likely there's no reason to switch later.

I'd take a good look at REST (and its reference implementation Jersey) before getting into SOAP, though. RESTful WS are easier to get started with, and more popular nowadays.

Start reading here: WebServicesFaq



I have seen this long FAQ many times but couldn't filter it for me Could you please clarify my doubts:
- Do you really think that it (JAX-RPC) is completely obsolete? I think you need to understand its basics too for giving support to existing services. Isn't it?
- Can a JAX-WS do all the work that JAX-RPC used to do?
- Today, is Annotation only medium to implement modern web services or without it also possible?
- Are SOA and Web-Services same? If not, then what is difference?
- Please suggest some good books for Axis/Metro/Jersey implementations?


Thanks a lot.
 
Ulf Dittmer
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
JAX-RPC is not the basic of WS or JAX-WS. And yes, it is obsolete, period.

It is certainly possible not to use annotations when implementing WS. E.g., you could use the Axis2 API.

SOA is an architectural style, while WS works over just one particular transport (HTTP). See their respective Wikipedia pages and the WebServicesFaq for more information.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic