What is the use of urn:jboss:domain:jaxr subsystem in JBoss EAP 6?

Solution Unverified - Updated -

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.x

Issue

  • What is the use of urn:jboss:domain:jaxr subsystem in JBoss EAP 6? Is it okay to remove this subsystem?

Resolution

<subsystem xmlns="urn:jboss:domain:jaxr:1.0">
    <connection-factory jndi-name="java:jboss/jaxr/ConnectionFactory"></connection-factory>
    <properties></properties>
</subsystem>
  • This configuration means that by default Scout connects to the UDDI registry using the UDDI v2 API specification, using the SaajTransport class. It is this configuration that was used for TCK compatibility testing as the JAXR specification has not been updated since the UDDI v3 specification was published.

  • Previous version of JBoss-AS have always shipped with a jUDDI v2 registry but, for the time being, it was decided to ship the client libraries only this time, which is the only JEE6 required component anyway.

  • The JAXR subsystem is provided in standalone-full profile. So if users don't want to use jaxr module, using default profile or deleting the module is fine.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.