Best practice on Process Definition design sought

[greg823]

I am new to jBPM, have been following the tutorial using the starter kit, and things start making sense, am grateful to JBoss folks for this product.

My next step is to imbed jBPM workflow engine into an existing Struts application.

My questions are:

1. What granularity of process definitions should I use? A process definition may span several Struts actions. What is the best practice you recommend?

2. Are there real processdefinition.xml files that are good examples?
Particularly, I would like to see examples of JPDL files used in a Struts app,
so I can contrast the Struts config file with JPDLs.

Thank you.

[kukeltje]

1: that is up to you. If you have multiple screens/actions that span one task, then you have n:1. Sometimes there is just one screen per task so 1:1. Realy, it is up to you to decide.

2: Some others should post this I think, we don't have these. In an application I did wich uses JSF (and it's pageflow) with jBPM, there are from 1 to 4 screens per task.

hth a little,

Ronald

[dr_j]

Would somebody please post an example of jBPM with jPDL (pageflow) where there are multiple screens per task? We've been hitting problems with this (documented in another post; I'm working on an example to post to JIRA), and if somebody has a working example, it may help explain what we're doing wrong.

Thanks!

j