[
https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug...
]
Bernd Ruecker commented on JBPM-1448:
-------------------------------------
Seems nobody can reproduce this test locally. Tom and me added some more testing and fixed
a small bug there (well spotted Tom!), in my eyes everything should be fine now...
Let's see what Hudson says (Heiko wanted to try it locally with Hudson as well)
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: Bernd Ruecker
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