One of the nice things about our subscription offerings is that if you buy an EAP
subscription, you get support and maintenance (patching) for all releases we have. Every
release has a base 7 year life-cycle, and another 3 years can be purchased. EAP 6 is only
a year into the cycle so customers have up to 9 years left on it. Our recommended solution
for CMP, JAXR, and JAX-RPC support is to leave those applications on EAP6.x. They will not
be available in EAP 7 and future releases.
One big factor that went into the decision to pull them from not just the community
project, but also the product line is that these specifications have significant
drawbacks. CMP can limit application performance, JAX-RPC has unfixable interoperability
issues, and JAXR suffers from limited use and is out of date with the latest UDDI
standard. We believe all of our users and customers would be best served by updating their
applications to the greatly improved replacements available since Java EE5. We believe
that the long life-cycle window of EAP 6.x should give everyone ample time to make that
On Jun 6, 2013, at 7:09 AM, Rebecca Searls <rsearls(a)redhat.com> wrote:
So what is the plan for handling this gracefully for users.
It would be helpful to have some clear documentation for a guide.
And a plan for the EAP implementation to provide backward compatibility even if WildFly
Big corporate customers will want the backward compatibility, better to plan for it now
than hack it later.
----- Original Message -----
> From: "Bartosz Baranowski" <bbaranow(a)redhat.com>
> To: "Stuart Douglas" <stuart.w.douglas(a)gmail.com>
> Cc: wildfly-dev(a)lists.jboss.org
> Sent: Thursday, June 6, 2013 2:34:20 AM
> Subject: Re: [wildfly-dev] JAXR backward compat
> ----- Original Message -----
>> From: "Stuart Douglas" <stuart.w.douglas(a)gmail.com>
>> To: "Bartosz Baranowski" <bbaranow(a)redhat.com>
>> Cc: wildfly-dev(a)lists.jboss.org
>> Sent: Wednesday, June 5, 2013 2:31:20 PM
>> Subject: Re: [wildfly-dev] JAXR backward compat
>> JAXR has been dropped as a required component of EE7, and will not be
>> supported in Wildfly AFAIK.
> Thats all I need to know, thanks.
>> If you want to reproduce this you will need to run it against EAP.
>> Bartosz Baranowski wrote:
>>> Im working on https://bugzilla.redhat.com/show_bug.cgi?id=964202
>>> seems to be a problem.
>>> Ive tried to reproduce this issue in upstream and it seems:
>>> [Host Controller] 10:29:49,081 INFO
>>> (Remoting "port2:MANAGEMENT" task-10) JBAS010920: Server
>>> [Server:server-two] registered using connection [Channel ID 316dfe98
>>> (inbound) of Remoting connection 248c1402 to /127.0.0.1:42158]
>>> [Host Controller] 10:29:49,117 ERROR
>>> (server-registration-threads - 1) JBAS014613: Operation
>>> failed - address: ([
>>> [Host Controller] ("profile" => "full"),
>>> [Host Controller] ("subsystem" => "jaxr")
>>> [Host Controller] ]) - failure description: "JBAS013452: Legacy
>>> 'org.jboss.as.jaxr' is not supported on servers running this version.
>>> extension is only supported for use by hosts running a previous release
>>> a mixed-version managed domain"
>>> Support for this has been dropped.
>>> Offending are two last commits:
>>> Shouldn't EAP 6 and 7 be backward compatible? If in this case answer is
>>> 'no' - is there any way to setup AS8 to reproduce this issue?
>>> wildfly-dev mailing list
> wildfly-dev mailing list
wildfly-dev mailing list
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat