[
http://jira.jboss.com/jira/browse/JBPM-653?page=comments#action_12363179 ]
Ernst-Jan van der Laan commented on JBPM-653:
---------------------------------------------
Hi,
I created a modified version of jBPM also that caches the process classload as long as
there are classes loaded by this classloader. It is using WeakReferences to cache the
process class loaders. This can easly be extended/changed to a version using
SoftReferences as well.
The reason I created this cache is to enable to store serializable classes used as process
instance variables deployed together with the process definition.
By default only the handler classes can be deployed together with the process definition.
To get this working I also modified the VariableInstance.getValue method to change the
current thread context class loader to the ProcessClassLoader for this variable. The
SerializableToByteArrayConverter revert function then uses this classloader to deserialize
the class from the process definition database.
If someone is interested in this solution please let me know and I will send the modified
files.
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.1
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