[
https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-1448:
-----------------------------------
added a test and a small fix:
Replaced line 136 in class Delegation :
ClassLoader classLoader = JbpmConfiguration.getProcessClassLoader(processDefinition);
with
ClassLoader classLoader = Thread.currentThread().getContextClassLoader();
Bernd, can you verify if this update makes sense in your overall ideas for these
classloader updates ?
I also added test org.jbpm.jpdl.par.ProcessClassLoaderTest. There are 2 TODO's in
there. Bernd, could you look at those 2 extra tests that should be created.
Give me an update thursday evening. I can take over if you don't have the time.
jBPM does not initialise thread context classloader
---------------------------------------------------
Key: JBPM-1448
URL:
https://jira.jboss.org/jira/browse/JBPM-1448
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Engine
Reporter: Kevin Conner
Assignee: Tom Baeyens
Priority: Critical
Fix For: SOA 4.2 CP03, SOA 4.3, jBPM 3.3.0 GA
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 message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira