[
https://jira.jboss.org/jira/browse/JBPM-1966?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-1966:
-----------------------------------
my initial idea was that users should be able to supply their classloader if they want to.
and by default, the context classloader is used.
but for users to supply their classloader, i needed to store the classloader in various
places: configuration, parsers, ...
so now my idea was to get rid of the user-supplied classloader and just to use the context
classloader only. (then users can still set the context classloader if they want to)
clean up classloading
---------------------
Key: JBPM-1966
URL:
https://jira.jboss.org/jira/browse/JBPM-1966
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: PVM
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.0.0 Alpha2
in all of jbpm codebase, the context classloader should be taken.
all classloader members to provide a classloader programmatically should be removed.
if users want to configure the classloader, it should be done with a command service
interceptor that sets the current thread context classloader.
--
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