Jeff,
Thanks for your approach. I guess there a various ways to structure
this. I was trying to avoid having two template pages and two controllers
for each report. That seemed like too much. Your solution is nice because
you end up with a total of two controllers, and then two template pages for
each report.
What I ended up doing was putting both the query template page and the
report template page together in a single template page doing something
like this:
<html>....
#if ($form)
html for form goes here
#else
html for report goes here
#end
...</html>
And then in the controller is something like this:
boolean getForm() { return getRequest().getMethod().equals("GET"); }
The controller also ends up serving "double-duty", handling the query and
the report. I like it because it tends to keep like functionality together.
By the by, I _really_ am enjoying this framework. It truly is
well-designed and thought through -- it is a pleasure to use. I've worked
with and seen many frameworks and this is the first one I've seen that
really makes sense. (...even without documentation!!!)
Thanks,
Dan
At 08:26 PM 2/12/02 -0800, you wrote:
>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
_______________________________________________
Mav-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mav-user
