10:43 p.m.
Thoughts?
-------- Original Message --------
Subject: JAXR update to support UDDI v3?
Date: Fri, 31 Aug 2007 12:51:03 -0700
From: bill.shannon(a)SUN.COM
Reply-To: Java Community Process JSR #316 Expert List <JSR-316-EG(a)JCP.ORG>
To: JSR-316-EG(a)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
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
11:36 p.m.
Prune it.
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(a)SUN.COM
Reply-To: Java Community Process JSR #316 Expert List <JSR-316-EG(a)JCP.ORG>
To: JSR-316-EG(a)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
9:52 a.m.
+1
We use JAX-R in the ESB for registries, but it's fallen way behind
where UDDI and ebXML now are that any update will be too late for us
anyway.
Mark.
On 31 Aug 2007, at 22:36, Scott M Stark wrote:
Prune it.
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(a)SUN.COM
> Reply-To: Java Community Process JSR #316 Expert List <JSR-316-
> EG(a)JCP.ORG>
> To: JSR-316-EG(a)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
>
----
Mark Little
mlittle(a)redhat.com
JBoss, a Division of Red Hat
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire,
SI4 1TE, United Kingdom.
Registered in UK and Wales under Company Registration No. 3798903
Directors: Michael Cunningham (USA), Charlie Peters (USA) and David
Owens (Ireland)
3:49 p.m.
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(a)SUN.COM
Reply-To: Java Community Process JSR #316 Expert List
<JSR-316-EG(a)JCP.ORG>
To: JSR-316-EG(a)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
6084
days inactive
6087
days old
3 comments
4 participants
participants (4)
-
Bill Burke -
Burr Sutter -
Mark Little -
Scott M Stark