JAXR has been dropped as a required component of EE7, and will not be supported in Wildfly
AFAIK.
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