| Summary: | The name of the transaction must be set in hibernate.cfg.xml | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | nwallace <nwallace> |
| Component: | Documentation, JBossESB, Build Process, Configuration | Assignee: | trev <tkirby> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 4.3 IR4 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.3 CP01 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-959 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-02-20 12:48:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 778311 | ||
|
Description
nwallace
2008-10-20 11:37:38 UTC
Link: Added: This issue is related to JBPM-1179 Link: Added: This issue is a dependency of SOA-796 Jpachane raised this point. "CP01 will contain new jBPM so it has to be done at config file level to work ESB out-of-box" Link: Added: This issue related SOA-1039 Trevor, is this still necessary with the update to jbpm-3.3.0? Also could you please point me to the hudson job where I can see jbpm running on the SOA platform? This was fixed in revision 2455 of: build-tools/builders/jbpm/build.xml Commit message: Pull across revision 2454 from 4.2.0 branch. > Also add a jta.UserTransaction property to the "standalone" jbpm-jpdl build. Verified in CR2 Release Note: Compatibility changes required in transaction lookup in jBPM 3.2.3 make it now necessary to set the jta.UserTransaction property in hibernate.cfg.xml to UserTransaction. Additional information: http://jira.jboss.com/jira/browse/JBPM-1179 Scratch that. Already documented as a known issue in the release notes, and in the Getting Started Guide under upgrading applications |