Bug 780389 (SOA-2809)

Summary:	Need to document CXF installation process - as it relates to impact to OOTB configs - and user-created custom configs
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Len DiMaggio <ldimaggi>
Component:	Documentation, EDS	Assignee:	Dana Mison <dmison>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	5.1.0.ER7
Target Milestone:	---
Target Release:	5.1.0 GA
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2809
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-17 02:14:27 UTC	Type:	Task
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Len DiMaggio 2011-01-19 15:11:14 UTC

Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes
project_key: SOA

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.

Comment 1 Dana Mison 2011-02-16 03:58:15 UTC

Labels: Added: Getting_Started_Guide

Comment 2 Dana Mison 2011-02-16 05:02:11 UTC

Added to known issues.  Will also add a warning to the EDS install instructions

Comment 3 Dana Mison 2011-02-16 05:02:11 UTC

Release Notes Docs Status: Added: Documented as Known Issue
Writer: Added: Darrin
Release Notes Text: Added: 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.
Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes]