[jBPM Development] - Re: Extension of schema and Task-objects
by sebastian.s
Hello Ronald,
thanks for your answer.
"Ronald" wrote :
| I personally would also opt for a nice api to retrieve additional attributes on existing elements (activities)
|
I am especially interested in this, too: storing information with tasks and retrieving them later on so I would love to see something like this. IHMO opinion it's a common use case that you deal with a task list in your own application or client and you are in need of additional information what the task is about and how to represent and deal with it in your program. The possibility of having custom attributes in a convient way without the need of extending or implementing would make a thing like this a lot more easier.
For example: You could define use-case-specific task types because you know that in your processes you got 3 different kinds of users tasks, for example. So you could always determine the type of a task to display a proper form to input data or you react in a different way in your application.
I hope you get the idea of my example. I'd love to hear what you think about my thought.
Cheers!
Sebastian
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258938#4258938
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258938
15 years, 3 months
[jBPM Development] - Re: making references to usercode more consistent in jpdl
by tom.baeyens@jboss.com
Guys, a question: Does it make sense to combine an expr with injections when specifying user code ?
imo it does not. if you specify an event-listener or custom activity behaviour. if you obtain the user code object by resolving an expression, i think it would be highly unlikely for users to want to inject things in it after resolution. since it is resolved as an expression, it doesn't live in the process or the deployment scope. and hence the object lives in another scope like the process instance, process engine, some web beans context maybe. if your object is resolved from these other contexts, it would seem very strange if the process execution would inject values in it.
so my conclusion is that we'll have more robust software if we explicitely remove injections in case an expr attribute is used to refer to user code.
wdyt ?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258928#4258928
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258928
15 years, 3 months