Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-5576

JBossWS - port-component-uri in jboss.xml ignored for JAX-WS / EJB3 deployments

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.3.0.GA_CP10
    • 4.3.0.GA_CP09
    • EJB, Web Services
    • None
    • Workaround Exists
    • Hide

      Use the @WebContext annotation to set the value, this workaround however is not valid for users with a requirement to manage the URL using a descriptor.

      Show
      Use the @WebContext annotation to set the value, this workaround however is not valid for users with a requirement to manage the URL using a descriptor.
    • Hide
      If a port-compnent-uri was specified in the jboss.xml descriptor along side the EJB3 deployment, the URI was ignored and the default URI used instead. Customers wanting to alter JAX-WS or EJB3 webservice URLs using a descriptor, and not use annotations limited to JBoss (@WebContext) could not implement this functionality.
        The fix adds support for the port-component-uri in jboss.xml descriptor files. Customers can now modify the URL using the jboss.xml descriptor instead of JBoss-specific annotations.
      Show
      If a port-compnent-uri was specified in the jboss.xml descriptor along side the EJB3 deployment, the URI was ignored and the default URI used instead. Customers wanting to alter JAX-WS or EJB3 webservice URLs using a descriptor, and not use annotations limited to JBoss (@WebContext) could not implement this functionality.   The fix adds support for the port-component-uri in jboss.xml descriptor files. Customers can now modify the URL using the jboss.xml descriptor instead of JBoss-specific annotations.
    • Documented as Resolved Issue

      If a port-compnent-uri is specified in the jboss.xml descriptor along side the EJB3 deployment this is ignored and the default URI used instead.

      (The upstream versions have undergone various re-factorings for the meta data handling so this is not an upstream issue, the upstream re-factoring is also incompatible for a backport so this will be a new implementation.)

              darran.lofthouse@redhat.com Darran Lofthouse
              darran.lofthouse@redhat.com Darran Lofthouse
              Jared Morgan Jared Morgan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: