Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown


Ranch Hand
Posts: 385
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Could any please expalin the difference between these APIs SAAJ vs JAXP vs JAX-RPC?

I know JAXP is used for XML processing.

But what is the difference between SAAJ and JAX-RPC as both can be used for webservice?

Also how JAXP is different from JAX-RPC?

Posts: 43016
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As you said, JAXP is an API for XML processing: parsing (SAX and DOM), transforming (XSLT), and dissecting (XPath).

SAAJ and JAX-RPC are web service APIs, with JAX-RPC operating on a higher level than SAAJ. SAAJ is sort of like a DOM API for SOAP messages, while JAX-RPC lets you work with a Java API to set/add/read parameters and results.

JAX-RPC is obsolete, though - you shouldn't use it for anything new. JAX-WS is the current high-level API for web services.
Ranch Hand
Posts: 121
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is there anything JAX-RPC cannot do that JAX-WS does? Infact i found it very convenient to webservice enable my application using JAX-RPC - RAD provides a good tooling for that.
Ranch Hand
Posts: 2198
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think I recall having read somewhere that the XML binding in JAX-RPC is not as complete as JAXB, which is what JAX-WS uses.
Some items from the JAX-WS specification:
- Client-side asynchronous service invocations.
- Substitution of deployment descriptors with annotations.
- Support for message based session management.
- Development of handlers has been simplified.
- Supports the WS-I Basic Profile version 1.1, as compared to version 1.0 for JAX-RPC.

There are probably more, but at least you should have some more motivation to take a look at JAX-WS.
Best wishes!
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic