I may be misunderstanding your question, but it sounds fairly straightforward. Sounds like you could have two controllers, the first of which takes parameters to indicate which fields to display and then populates a model (say a HashMap) with the data to be displayed on the admin screen. The view for the admin screen would have the whole possible set of form elements, but it would only display them based on which values are in the Map model. Of course the submit controller for the admin screen would be able to accept everything.
What templating technology are you using? This is quite easy in XSL and Velocity, considerably less so in JSP without the proper tag libraries. Jeff > -----Original Message----- > From: Dan Finkelstein [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 12, 2002 11:22 PM > To: [EMAIL PROTECTED] > Subject: [Mav-user] Standard Query Page => Results Page > > Hi -- > > I have a number of "admin-type" screens that I'm putting together which > first display a page with a form to specify what to display. Then the > results are displayed on the next page. > > My question is: what's the "recommended" way to do this with > Maverick? I've been scratching my head on this, and came up with some > seemingly awkward ways, but it seems like there might be simpler way. > > Any ideas? > Thanks, > Dan > > > _______________________________________________ > Mav-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/mav-user _______________________________________________ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
