Bug 778234 - Workround in SOA-586 should be removed
Summary: Workround in SOA-586 should be removed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Build Process
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: FUTURE
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-03 16:58 UTC by Julian Coleman
Modified: 2012-07-13 04:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: SOA-735
Environment:
Last Closed: 2011-11-01 20:16:07 UTC
Type: Task

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-735 0 None None None Never

Description Julian Coleman 2008-09-03 16:58:13 UTC 
++ This bug is a clone of bug 778232 ++

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.
Note You need to log in before you can comment on or make changes to this bug.