Re: [orbeon-user] xforms:bind design question

[balazs . molnar]

Hello Alex,

Our plan at the moment is to create a layer like the 'session facade' in j2ee terms which would allow statefulness for transactions during client interactions within a session. One of the responsibilities of this layer would be to do the data type and content validation. The result of this would be passed back all the way to epilogue processing and there we would implement our own error display.  The issues I currently see:
- a very important one: localization of error messages
- xforms:bind is basically a client side validation therefore it is not suitable for many kinds of error validation which involve verification of rules of business entities residing on the server. Even if you could express some rules it does not seem like the place to put them - an issue that immediately occurs to me would for e.g. be reuse of validation logic
- schema validation: many of the data type validation could be here but not a total solution either

For some of the above reasons we came to the conclusion to take error message handling in a separate layer and maybe use xforms:bind rules only for page specific error validations.

regards,
Balázs

p.s.: XMLBeans seem to have meningful and correct validation messages.