Version 17

    JBossWS 1.0.1 Installation instructions


    In order to upgrade JBossWS to 1.0.1 on JBossAS 4.0.4GA there are a few steps involved that have to be done manually:


    1. Replacing JBossXB (mandatory)

    2. Moving the naming service declaration (optional)


    1. Replacing JBossXB


    This is a mandatory step since the latest JBossXB version (CR5) doesn't work with 4.0.4GA due to some binary compatibility issues.

    In order to upgrade to 1.0.1 you need to manually replace the jboss-xml-binding.jar in the JBOSS/client and JBOSS/lib directories. The 4.0.4GA compatible release can be found here: 1.0.0.CR5_JBoss-4.0.4.GA



    2. Upgrading on 4.0.4GA that was installed using the installer


    Several issues have been reported that relate to deployment ordering of JBossWS and it's depending services. These problems only occur on 4.0.4GA that has been installed using the installer and will be addressed in subsequent releases. Until these issues are resolved, we suggest to manually move the naming service declaration back to  the static jboss-service.xml:


    Cut and paste all of the mbean configurations from the deploy/naming-service.xml and put them in conf/jboss-service.xml at the bottom. Also, make sure that after you have pasted these entries in jboss-service.xml, that you delete the naming-service.xml file.


    For example:

       <mbean code="org.jboss.naming.NamingService"
          <!-- The call by value mode. true if all lookups are unmarshalled using
          the caller's TCL, false if in VM lookups return the value by reference.
          <attribute name="CallByValue">false</attribute>
          <!-- The listening port for the bootstrap JNP service. Set this to -1
            to run the NamingService without the JNP invoker listening port.
          <attribute name="Port">1099</attribute>
          <!-- The bootstrap JNP server bind address. This also sets the default
          RMI service bind address. Empty == all addresses
          <attribute name="BindAddress">${jboss.bind.address}</attribute>
          <!-- The port of the RMI naming service, 0 == anonymous -->
          <attribute name="RmiPort">1098</attribute>
          <!-- The RMI service bind address. Empty == all addresses
          <attribute name="RmiBindAddress">${jboss.bind.address}</attribute>
          <!-- The thread pool service used to control the bootstrap lookups -->
          <depends optional-attribute-name="LookupPool"
       <mbean code="org.jboss.naming.JNDIView"