Quote: I do mind that quite a bit (for more complex validation): where I work we don't just have a web tier exposing the services only, we have may have webservices exposing the business tier as well.
In this case, it is highly desirable not to need to duplicate the validation in both places, it should ideally exist in the business tier only and be propagated to the UI. This can already be done with server side exception handling in struts using the pattern matching exception handler we have in bpm4struts: Write an OCL constraints as a precondition, and then have the patern matching exception handler take care of the rest in propagating it to the UI, however you still have to duplicate your javascript error handling, which is a pain (end of quote) ah, is that what he meant ? k, in that case I misunderstood, I was thinking your description to be the opposite (reusing the middle tier in the web tier, instead of vice-versa as he mentioned) -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=483#483 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
