Our general recommendation is to provide an XSLT that transforms the maverick configuration file to add your extra views.
Use the configTransform init param to the Maverick dispatcher: http://mav.sourceforge.net/maverick-manual.html#N100CB You can define your commands like this: <command name="blah" loginRequired="true"> ... </command> (or whatever designator you choose) and then you can have an XSLT that adds the extra views to any command so designated. I can provide a sample if you would like assistance. Jeff Schnitzer [EMAIL PROTECTED] > -----Original Message----- > From: Shackelford, John-Mason [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 17, 2002 2:31 PM > To: '[EMAIL PROTECTED]' > Subject: [Mav-user] chained controller use case? > > In the friendbook example, each command defines two views for > authentication > failures in addition to one for "success". I am working on an app which > has > four different views for authentication failures and hundreds of commands. > Defining four extra views for each command obscures the logic of my > maverick.xml file and seems unnecessarily redundant. > > It seems like what I would want to do is send all security authentication > failures to a security controller that would have these four views. Has > anyone done anything like this? > > Doing authentication checks in perform() method and return a String > representing a view isn't going to work unless I clutter up the > maverick.xml > file with special views that handle the redirect--which would defeat my > purpose. Can I alter the context so that we render a view associated with > a > different command? Or, as an alternative, can we call another controller > and > have it redefine the context so that we render one of its views? > > > > John-Mason Shackelford > > Software Developer > NCS Pearson - Measurement Services > 2510 North Dodge St. > Iowa City, IA 52245 > 319-354-9200x6214 > [EMAIL PROTECTED] > > > ************************************************************************ ** > ** > This email may contain confidential material. > If you were not an intended recipient, > Please notify the sender and delete all copies. > We may monitor email to and from our network. > ************************************************************************ ** > ** > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > [INVALID FOOTER] ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ [INVALID FOOTER]
