Uploaded image for project: 'JBoss Enterprise SOA Platform'
  1. JBoss Enterprise SOA Platform
  2. SOA-2809

Need to document CXF installation process - as it relates to impact to OOTB configs - and user-created custom configs

    Details

    • Affects:
      Documentation (Ref Guide, User Guide, etc.), Release Notes
    • Release Notes Text:
      Hide
      The Apache CXF installer modifies the jboss-as/common/lib/ directory and the included server profiles of all, default, production, standard, and web. Any other server profiles that have been added will not be affected by the installer and will be incompatible with the common server configuration. To create a custom server profile, run the installer first, and then create the profile by creating a copy of one of the supported profiles (all, default, or production).

      This also affects the JBoss Enterprise Data Services Platform installer.
      Show
      The Apache CXF installer modifies the jboss-as/common/lib/ directory and the included server profiles of all, default, production, standard, and web. Any other server profiles that have been added will not be affected by the installer and will be incompatible with the common server configuration. To create a custom server profile, run the installer first, and then create the profile by creating a copy of one of the supported profiles (all, default, or production). This also affects the JBoss Enterprise Data Services Platform installer.
    • Release Notes Docs Status:
      Documented as Known Issue

      Description

      New bug - requires a rel note

      In SOA-P 5.1, installing CXF into any server profile (all, default, production) results in ALL server profiles being affected. This is the case as the install replaces Native JBoss WS jars that are in the common lib dir shared by all server profiles in addition to replacing jars in the specific server profile lib dir.

      Also, if a user creates a custom config by copying an OOTB profile, he must run the CXF installer BEFORE copying an OOTB to a custom config.

      Additional information - for a case where a user created a custom config, then installed CXF:

      I would guess that you have installed EDS/CXF into the ER5 server but
      did this after creating the EDS_Default profile.

      Unfortunately this can lead to profiles which are inconsistent, i.e.
      configured to use JBossWS native within the profile but globally
      configured to use CXF.

      In this case it is simple to reproduce

      • copy default to default.test
      • install CXF
      • start default.test

      The class is missing because it has been moved as part of the CXF
      installation. It had originally been located within
      common/lib/jbossws-native-jaxrpc.jar (i.e. applying to all profiles) but
      then moved to server/XXX/deployers/jbossws.deployer/jaxrpc-api.jar (i.e.
      each profile containing CXF).

      There may be other inconsistencies when installing CXF in this way, but
      I believe we are only supporting CXF installation when it applies to all
      profiles.

      In order to fix this you will need to install CXF into the ER5 server
      before creating the EDS_Default profile.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                dmison Dana Mison
                Reporter:
                ldimaggio Len DiMaggio
                Writer:
                Dana Mison
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: