What you guys didn't yet show me is the problem i (or our users) would run into if
they didn't separate ui from process logic.
I don't yet see an intrinsic downside of mixing UI with process logic.
I agree that UI and process logic should not be FORCEFULLY TIED together. But i
don't see a problem in offering an optional form field in the task that can optionally
be used by UI technologies.
This can already cover most situations where there will be 1 UI technology involved for
each task form.
On the other hand, i DO see an intrinsic problem with the current approach. Namely that
users have to maintain the indirection manually in the forms.xml. (The GPD could improve
support for this, but there is always the chance of a user modifying the task name with a
text editor). Removing that indirection also removes the possiblity of errors in that
indirection
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979635#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...