anonymous wrote : My idea was a very generic framework where you declare the
variables you have in each task and how they should be validated in an XML
file.
I agree, that is what we also do. But we use an existing framework. Our
webbased ui or message b2b definitions are complex and based on
kukeltje, thanks for the reply. So you are saying that you perform validation
before it enters jbpm and not, for example, within an action handler? My idea
was a very generic framework where you declare the variables you have in each
task and how they should be validated in an XML file.
With
anonymous wrote : How/where to do validation of variablesLimit validation in
the process. Just do it like you normally would. Store only relevant (meta?)
data in the process. We hardly use the jbpm forms for production. Only for
rapid prototyping
anonymous wrote : How and when to transform the
