Yep, that may be the approach I take although it circumvents the front controller. Not necessarily a bad thing. It just disperses business logic, configuratin, and, in event that the assertion fails, navigation logic. It would be nice to have this all reside within the front controller and configurable via one source (the struts-config file).
robert > -----Original Message----- > From: Jennings, Christofer J. [mailto:[EMAIL PROTECTED]] > Sent: Thursday, June 06, 2002 10:26 AM > To: 'Struts Users Mailing List' > Subject: RE: Assertions > > > How about using filters? > > -----Original Message----- > From: Robert Taylor [mailto:[EMAIL PROTECTED]] > Sent: Thursday, June 06, 2002 7:12 AM > To: [EMAIL PROTECTED] > Subject: Assertions > > 1. Assertions that are common to all events. > 2. Assertions that are common to a set of related events. > 3. Assertions that are specific to an event. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
