[esb-dev] [Fwd: JAXR update to support UDDI v3?]

Burr Sutter burr.sutter at redhat.com
Mon Sep 3 09:49:19 EDT 2007


What is the alternative to JAXR?  Or is Java EE and UDDI essentially 
parting ways at this juncture and it is up to the OSS world to build 
something that becomes the "defacto standard" for providing a common 
Java-based API to the various UDDI registry products on the market?

Bill Burke wrote:
> Thoughts?
>
> -------- Original Message --------
> Subject: JAXR update to support UDDI v3?
> Date: Fri, 31 Aug 2007 12:51:03 -0700
> From: bill.shannon at SUN.COM
> Reply-To: Java Community Process JSR #316 Expert List 
> <JSR-316-EG at JCP.ORG>
> To: JSR-316-EG at JCP.ORG
>
> My impression is that few customers are using the JAXR API and
> there's little interest from vendors to improve JAXR.  Because
> of that, JAXR has fallen behind the UDDI spec and doesn't support
> all the latest UDDI features.
>
> How important do you think it is for us to update JAXR?
>
> If this were free, we would just do it, but given that there's
> real cost - to update the spec, to update the RI, and to update
> the TCK - we need to determine whether to spend resources on this
> work instead of any of the many other items we could be working
> on.
>
> Our current plan is to *not* update JAXR for Java EE 6.  If you
> think that's the wrong decision, let me know, and suggest other
> work that we could defer in order to do the JAXR work.
>
> Alternatively, should we consider adding JAXR to the list of
> technologies to prune from Java EE, possibly removing it in Java EE 7?
>
> Let me know what you think.
>
> Thanks.
>
>         Bill
>




More information about the esb-dev mailing list