utiba_davidr
Joined: Sat Jun 23, 2007 08:52 AM

Oops, excuse me for my previous reply. I did not yet dive into the posts in the Seam forum, and apparently in that specific topic you and Gavin King decided that this question was better asked in the jBPM forum -- and you even linked here. Good!

So: I hope you'll find your answer here. At least my erroneous comments make your topic move up in the list of topics...

Sorry,
Arjan.

Don't know about extending and overloading but pageflow composition (http://jira.jboss.com/jira/browse/JBSEAM-157 ?) would be an option. What I personnaly would like is a dynamic processcomposition. This way you can have one big main process, but runtime decide which subprocess to load for a specific user. Would that solve your problem or would overloading/extending of subprocesses still be required?

Dynamic process composition would be very useful. Is this something that is being worked on? Is there any way to achieve the same effect with the current release?

Thanks,

Damian.

"damianharvey" wrote:
Dynamic process composition would be very useful. Is this something that is being worked on?

"damianharvey" wrote:

Is there any way to achieve the same effect with the current release?

Correction.... there is something like a customsubprocessresolver... that can be used to achieve this. Look at the testcases in the source!!!

But.... see

http://jira.jboss.com/jira/browse/JBPM-1004

I already implemented this... committing will be tonight

if you want it now, apply this patch to the source of 3.2.1

### Eclipse Workspace Patch 1.0
#P jbpm.3-clean
Index: jpdl/jar/src/main/java/org/jbpm/graph/node/ProcessState.java
===================================================================
RCS file: /cvsroot/jbpm/jbpm.3/jpdl/jar/src/main/java/org/jbpm/graph/node/ProcessState.java,v
retrieving revision 1.3
diff -u -r1.3 ProcessState.java
--- jpdl/jar/src/main/java/org/jbpm/graph/node/ProcessState.java 15 Nov 2006 12:51:07 -0000 1.3
+++ jpdl/jar/src/main/java/org/jbpm/graph/node/ProcessState.java 28 Jun 2007 13:04:57 -0000
@@ -62,6 +62,7 @@
 import org.jbpm.graph.exe.Token;
 import org.jbpm.graph.log.NodeLog;
 import org.jbpm.graph.log.ProcessStateLog;
+import org.jbpm.jpdl.el.impl.JbpmExpressionEvaluator;
 import org.jbpm.jpdl.xml.JpdlXmlReader;
 import org.jbpm.jpdl.xml.Parsable;

@@ -147,9 +148,14 @@
 ) {
 SubProcessResolver subProcessResolver = getSubProcessResolver();
 List attributes = new ArrayList();
- attributes.add(new FlyweightAttribute("name", subProcessName));
+ String subProcessNameResolved = (String) JbpmExpressionEvaluator.evaluate(subProcessName, executionContext);
+ if (log.isDebugEnabled()) {
+ log.debug("SubProcessName after eval: " + subProcessNameResolved);
+ }
+ attributes.add(new FlyweightAttribute("name", subProcessNameResolved));
 Element subProcessElement = new DefaultElement("sub-process");
 subProcessElement.setAttributes(attributes);
+
 usedSubProcessDefinition = subProcessResolver.findSubProcess(subProcessElement);
 }

ahh... what the h.... already committed, INCLUDING a testcase

Thanks. Speedy stuff.

This is all due to the very flexible design of jbpm (and it will be even better for the 4.0 release). Docs still need updating though... (but that is also true for the late binding etc..

uhmm... one thing... this is only for subprocesses in jpdl... not for pageflow yet!!!