Hi we had some similar sort of issue, we have AS400 RPGLE programs doing business logic and validation (not screen but business related) to get the messages from RPGLE to JSP using struts we defined one ErrorMessage class, then we trap the message from AS400 in this ErrorMessage class and then build a mapping to transfer these messages from ErrorMessage class to Strusts ActionErrors class, for swing we used these ErrorMessage directly to display messages, so we did not had to duplicate any code
Ashish --- "Rooney.Dave" <[EMAIL PROTECTED]> wrote: > > -----Original Message----- > > From: Erik Weber [mailto:[EMAIL PROTECTED] > > > Sent: February 14, 2005 8:19 AM > > To: Struts Users Mailing List > > Subject: Re: Validation Strategies? > > > > > > I use Struts' declarative exception handling > abilities to handle > > manager-layer validation errors. Exceptions that > are not > > caught by your Actions can be configured to be > handled by Struts' > default > > exception handler, or even better, your own > exception handler (Struts > > is easy to extend in this fashion). The Exception > handler looks up an > > appropriate message (for the user) in a resource > bundle, just as the > Validator > > plugin does when it encounters exceptions. > > > > Erik > > Erik, > > Part of the problem is that our system has both a > Swing GUI front-end > and Struts/JSP. We don't want to duplicate the > validation logic. > > Thanks! > > Dave Rooney > Secure Systems Development > [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > __________________________________ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
