Bug 778352 (SOA-837)

Summary: jBPM does not initialise thread context classloader
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: nwallace <nwallace>
Component: JBPM - within SOAAssignee: trev <tkirby>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.2 CP02   
Target Milestone: ---   
Target Release: 4.2 CP04   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-837
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-06-12 09:03:17 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:

Description nwallace 2008-09-25 14:23:53 UTC 
Date of First Response: 2008-11-29 05:51:17
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=191831
project_key: SOA

 jBPM does not initialise the thread context classloader when executing actions within the process.

The outcome of this decision is that code executed within the context of this action will not have access to classes/resources in the par unless the action classloader is an explicit parameter.

One example of this is the RMI marshalling layer, which has an implication on JNDI lookups.
Comment 1 nwallace 2008-09-25 14:23:53 UTC 
Link: Added: This issue depends JBPM-1448
Comment 2 nwallace 2008-09-25 14:32:06 UTC 
Link: Added: This issue is related to SOA-648
Comment 3 nwallace 2008-09-25 14:37:32 UTC 
Can we have confirmation that fixes are in place for 4.2CP03.
Comment 4 Thomas Diesler 2008-11-29 10:51:17 UTC 
Fixed in jbpm-3.3.0.GA
Comment 5 Julian Coleman 2009-05-05 10:34:28 UTC 
Fixed with the upgrade of jBPM to 3.2.5SP5.
Comment 6 Jiri Pechanec 2009-06-12 09:03:17 UTC 
CR4: Correct jBPM version in place