Hide Forgot
Date of First Response: 2008-09-07 06:05:58 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.
This issue originally existed as SOA-635 but was moved into the jBPM JIRA. This exists for tracking through the SOA platform.
Link: Added: This issue is a dependency of JBPM-1448
Link: Removed: This issue is a dependency of JBPM-1448
Link: Added: This issue depends JBPM-1448
Waiting on JBPM-1448
Emailed Thomas on behalf of J, but I see there's a comment on JBPM-1448 for Trev so I've emailed him too.
Link: Added: This issue related SOA-837
Fixed in jbpm-3.3.0.GA
Verified in the sources
Release Note: JBPM-1448 The thread context classloader is now initialized by jBPM when executing actions within the process. This allows access to classes and resources in the PAR.