Bug 778373 (SOA-856) - jBPM datasource should be XA datasource
Summary: jBPM datasource should be XA datasource
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-856
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.2 CP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CP05
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-25 19:39 UTC by nwallace
Modified: 2010-07-28 20:23 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-07-28 20:23:38 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778004 0 high CLOSED jBPM datasource should be XA datasource 2025-02-10 03:14:37 UTC
Red Hat Bugzilla 778010 0 high CLOSED Extend /jboss-as/tools/schema to support Sybase (tier2 database) 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 778011 0 high CLOSED Extend /jboss-as/tools/schema tool, add multiple config files to support DB2 (tier2 database) 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 778016 0 urgent CLOSED Extend /jboss-as/tools/schema to support MS-SQL (tier2 database) - and add other server config files 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-856 0 Major Closed jBPM datasource should be XA datasource 2016-03-18 07:23:59 UTC

Internal Links: 778004 778010 778011 778016

Description nwallace 2008-09-25 19:39:54 UTC 
project_key: SOA

See JBESB-1695
Comment 1 nwallace 2008-09-25 19:39:54 UTC 
Link: Added: This issue depends JBESB-1695
Comment 2 nwallace 2008-09-25 19:39:54 UTC 
Link: Added: This issue related SOA-538
Comment 3 nwallace 2008-09-25 19:39:54 UTC 
Link: Added: This issue related SOA-541
Comment 4 nwallace 2008-09-25 19:39:54 UTC 
Link: Added: This issue related SOA-537
Comment 5 nwallace 2008-09-25 19:40:31 UTC 
Link: Added: This issue is related to SOA-531
Comment 6 nwallace 2008-09-25 19:41:13 UTC 
Can we have confirmation that fixes are in place for 4.2CP03.
Note You need to log in before you can comment on or make changes to this bug.