• 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:
  • Tim Cooke
  • Campbell Ritchie
  • paul wheaton
  • Ron McLeod
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:

JAX-RPC vs Axis SOAP

 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi I have gone through the web services tool kits available from SUN and IBM. I observed in few examples that SUN & IBM are using different APIs for publishing to / search the registries.. I guess sun is using JAXR and IBM is using uddi4j API. I am prettry confused here of whether uddi4j is an extension of JAXR. To add to my woes, it is mentioned in the axis release notes (that comes with IBM wstk3.2) that axis beta release 3 is 100% complient with JAX-RPC and SAAJ specifications from SUN. My question here is that, does the IBM webservices framework (or any webservices frame work available today) is built on these SUN api's? Please clarify, I appreciate your help.
 
Author and all-around good cowpoke
Posts: 13078
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
As far as I know, IBM's work on UDDI is mostly separate from Sun's. APIs for UDDI seem to be in flux and the "standard" is not well nailed down. I think the various vendors are all going in their own directions as far as an API for UDDI is concerned.
Bill
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
To qualify Bill's statement:
(1) There is no decided API for accessing registries. JAX-R is certainly not accepted by the Java community at large.
(2) IBM's Web Services systems are generally built off of the Apache systems (not surprising, considering that IBM is far and away the largest contributor to the Apache projects). For instance, the Web Services support in WebSphere Application Server 4.0 is built on Apache SOAP. The SOAP Support in WebSphere Application Server 5.0 will include support built on Apache Axis. We have accepted JAX-RPC as the standard Web Services API for Java, particularly considering our support for JSR 109 (which depends on JAX-RPC).
Kyle
 
reply
    Bookmark Topic Watch Topic
  • New Topic