in this case you could make your own taskcontroller (afaik, never tried it to the fullest)
So there is no better way than this scenario?
depends on your definition of better..... I feel you want a different solution. Can you explain why?
I'm not sure that a different solution is better or not, because I'm newbie in jBPM. But this approach has some side effects. For example by implementing our own node tags, the eclipse graphical designer will not recognize these node definitions. And some extra code for implementing this new node is necessary.
Do other jBPM-webbased applications use a similar approach?
In my webapp the task name resolves the jsp name, in other words if there is a file 'taskname' + '.jsp' in my folder then the funktion (it is a jsf action) has the taskname as output (string). then there is a nav case in the faces-config that leads to the specific jsp.
But I also support a more generic task definition in the jpdl.
That will work for links. Thank you.
What about other information needed for each node? For example each node would have a menu id which specifies the place of the task in the menu in worklist of users (something defined in my web application)?
Is there similar way for supporting such informations?
Specifying a taskcontroller is not a specific node. It is an attribute of an existing node. So no problem there. You can even do it generic for the whole engine.
The solution Hannes proposes can also work. I did something similar once.
If you 'only' have/need forms for tasks and not as a part of another webapp, look at 3.2 (cvs-head) it has functionality for doing custom pages per task
I still think that I should implement my own nodes!
task-controllers and more genral, process variables do not seem a good solution, because for each process instantiation the variables are created and they should get values for each process instance, while properties like URL, menuID, .. are labels for "node definitions" not for "nodes in a process instances". So performance using process and task variables is not good.
So I think I should design a table along with JBPM_NODE storing extra properties for each node.
Please if this design has a drawback, inform me about that.
And my new problem is the graphical-designer, which does not support third-party implemented nodes. Is it easy to change the graphical designer so that it supports new implemented nodes in jPDL?