7:09 a.m.
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
will not.
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.
>
> Stuart
>
> Bartosz Baranowski wrote:
> > Hi
> >
> > Im working on https://bugzilla.redhat.com/show_bug.cgi?id=964202 and
> > there
> > seems to be a problem.
> > Ive tried to reproduce this issue in upstream and it seems:
> >
> > [Host Controller] 10:29:49,081 INFO
> > [org.jboss.as.domain.controller.mgmt]
> > (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
> > [org.jboss.as.controller.management-operation]
> > (server-registration-threads - 1) JBAS014613: Operation ("describe")
> > failed - address: ([
> > [Host Controller] ("profile" => "full"),
> > [Host Controller] ("subsystem" => "jaxr")
> > [Host Controller] ]) - failure description: "JBAS013452: Legacy extension
> > 'org.jboss.as.jaxr' is not supported on servers running this version.
The
> > extension is only supported for use by hosts running a previous release
> > in
> > a mixed-version managed domain"
> >
> >
> > Support for this has been dropped.
> > Offending are two last commits:
> >
https://github.com/wildfly/wildfly/commits/master/jaxr/src/main/java/org/...
> >
> > 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(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev