late-binding was intended to be able to update the subprocess and have all
instances of the parent process use the latest version of the subprocess
instead of the version that was initially deployed
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100241#410024
Thanks!
Both solutions solve the problem, although i think the late-binding is the
preferred one.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100097#4100097
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100097
___
correct, or use the 'late binding option'
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099976#4099976
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099976
___
jboss-user ma
Hi, radius,
I had a similar problem with sub-processes and my solution was to put the
sub-process in components.xml before the calling process.
Seems like the sub-process has to be made known to the calling process, before
the calling process is parsed.
Hope this helps
Christian
View the