Yes you are confused and now i do not know how to start explaining.
JAXR - General Purpose Java - API specification for accessing business registry.
Ebxml RR (registry and repository) is a specification for Registry and Repository. Oasis Standard.
UDDI - Long Lived specification for a Registry.
JAXR is more of an abstract layer to access / interoperate between the existing 2 big standard for accessing a Registry. Its main feature is a pluggable architecture which allows a Ebxml provider or a UDDI provider to plugin.
simply put, JAXR is for writing a java client which doesnt have to bother if there you Organisation registry switches from UDDI to EbXML .
Raj Kumar Bindal
Joined: Apr 15, 2006
That means JAXR is for both uddi and ebxml.Actually as far as i understand,it is extensible.That is why i was confused,and when i see in API,all apis are referring UDDI only.Kindly explain this.
I think you have mixed up concepts here - JAXR is a Client API to access Registeries (it's basically just a hollow specification like JDBC with a Reference Implementation and Vendor plugged Implementations). So, this API lets you access Registeries for ebXML and UDDI .Remeber Both of them are registery specifications and not registries themselves.
So, now you have on client API to access various kinds of registeries, eh.
Now, to your last Question - why do you see UDDI everywhere when it comes to JAXR?
Its because BP 1.0 supports only UDDI as a registry even though ebXML is more flexible and richer than UDDI but J2EE Web Services which are BP 1.0 client must use only UDDI.
I am not sure of the book you are referring to - but most books which talk of the J2EE platform will most likely talk only about UDDI. However if you talk about Java Web Services you will see ebXML Examples.You might want to refer Sun's Reference Documentation on Accessing ebXML Registeries.
Hope the above info helped
OCMJEA/SCEA, SCDJWS, SCBCD 1.3, SCJP 1.4
My SCEA experience:http://javalogue.blogspot.com/