Bug 778232 (SOA-735)

Summary: Workround in SOA-586 should be removed
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Julian Coleman <jcoleman>
Component: Build ProcessAssignee: Julian Coleman <jcoleman>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecified   
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-735
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 778233 778234 (view as bug list) Environment:
Last Closed: 2011-11-01 20:16:07 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 Julian Coleman 2008-09-03 16:58:13 UTC 
Date of First Response: 2009-12-03 15:10:41
project_key: SOA

The workround in SOA-586 should be removed for 4.4 GA, now that JBAPP-900 has been resolved.
Comment 1 Julian Coleman 2008-09-17 11:37:03 UTC 
As we need to add ESB-specific entries to the *-persistence-service.xml files (see SOA-757), we will need to continue to provide our own copies of these files.  However, like other EAP/AS files that we override, we need to ensure we track their changes.
Comment 2 Mark Little 2009-12-03 20:10:41 UTC 
Status?
Comment 3 Julian Coleman 2010-01-25 16:40:43 UTC 
The process for patching the JMS DB configurations is done differently for SOA-P 5.
However, a better check for applicability is required for 5.0.1 and forward.