[
http://jira.jboss.com/jira/browse/JBPM-653?page=comments#action_12353613 ]
Matej Knopp commented on JBPM-653:
----------------------------------
I'm building a custom workflow solution with jBPM. The solution consists of a custom
web client built with Wicket web framework and a possibility to deploy wicket components
alongside the workflow. The components are then part of user tasklist.
I had to modify the ProcessClassLoader and ClassLoaderUtil, because by default jbpm
creates new instance of class loader for every delegate object requested. So I cache the
classloaders for specific process defition + version. I also modified the classloader. I
understand this is not how jbpm classloading is supposed to work, however, it would be
great if in future it would be possible to achieve such effect without having to modify
jbpm code.
So i'd really appreciate if it was possible to set custom classloader. But that would
also need means to affect how ClassLoaderUtil works, so that it is possible to cache class
loaders and not to create one every time a delegate class is requested.
make the process parent classloader configurable
------------------------------------------------
Key: JBPM-653
URL:
http://jira.jboss.com/jira/browse/JBPM-653
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Reporter: Tom Baeyens
Assigned To: Tom Baeyens
Fix For: jBPM jPDL 3.2
now, always the jBPM classloader is taken as a parent for the process classloaders. this
should be made configurable. at least one other possibility should be to configure the
context classloader.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira