[jboss-dev-forums] [Design of JBoss jBPM] - Re: extending form / task functionality

[tom.baeyens@jboss.com]

there would be no logic behind the taskform field in the task.  i think it could make sense that the task has a field called taskform, which is used and interpreted by external tools like our webapp.

so the task only gets one extra field which is optional and doesn't impact runtime execution.

wether mixing flow control with presentation is a good think depends on the use case, i think.  in some cases it is easier to define it all in one file, sometimes it is easier to separate things.

isn't this just style and taste versus good or bad ?

if that is the case, then i am in favour of supporting both.  as long as the runtime performance is not impacted.  in this case the impact is minimal.  by default, hibernate will load all null values in the taskform in case it is not used.  not sure if that is a problem.  if it would be a problem, the hibernate mapping for the taskform field can always be commented...

what do you think: is it a matter of taste or a matter of good or bad ?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979624#3979624

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979624