Hide
current springmodules worflow jbpm support performs process definition instantiation (using process definition factory) outside jbpmcontext, so that sub-process resolver (DbSubProcessResolver) cannot attach itself to the context and correctly resolve subprocesses.
to solve this issue, processdefinition factory bean has to be instantiated with reference to the jbpm configuration used, so that it can open/create new context and parse process defintion within this context.
i have also performed some modifications to localjbpmconfigurationfactorybean, to allow for list of process definition file locations be specified, and modified 'afterPropertiesSet()' method to perform processes definitions parsing INSIDE opened context.
probably, to solve this issue, the whole idea of localjbpmconfigurationfactorybean and processdefinitionfactorybean has to be redesigned (case one), or parsing has to be allowed only within localjbpmconfigurationfactorybean, and then process definition factory won't be used anymore.
additional idea, is to create deployer bean, fired from within of localjbpmconfigurationfactorybean after being configured, so that deployer's deploy() method will be called from within of localjbpmconfigurationfactory bean after factory has passed jbpmconfiguration to it.
Show
current springmodules worflow jbpm support performs process definition instantiation (using process definition factory) outside jbpmcontext, so that sub-process resolver (DbSubProcessResolver) cannot attach itself to the context and correctly resolve subprocesses.
to solve this issue, processdefinition factory bean has to be instantiated with reference to the jbpm configuration used, so that it can open/create new context and parse process defintion within this context.
i have also performed some modifications to localjbpmconfigurationfactorybean, to allow for list of process definition file locations be specified, and modified 'afterPropertiesSet()' method to perform processes definitions parsing INSIDE opened context.
probably, to solve this issue, the whole idea of localjbpmconfigurationfactorybean and processdefinitionfactorybean has to be redesigned (case one), or parsing has to be allowed only within localjbpmconfigurationfactorybean, and then process definition factory won't be used anymore.
additional idea, is to create deployer bean, fired from within of localjbpmconfigurationfactorybean after being configured, so that deployer's deploy() method will be called from within of localjbpmconfigurationfactory bean after factory has passed jbpmconfiguration to it.
Bug
Open
Critical
I have run into this issue as well. I was wondering if you solution used the stock code or if you had to customize. Some insight would be much appreciated.
Thanks,
Summers