RE: Best Practices Please

I've been away for a few days (hunting kangaroos and missing) but thanx to
the help so far on this topic.

Issue3
> I have a login command that returns the "home" view when the user
successfully logs in but
> I want to return a view OR command that is based on a http or session
parameter

>> I’m not quite sure why what I was saying earlier wouldn’t work - you
could return the name of a view which is a document \
>> view which forwards to another Maverick command.  Just like forwarding to
a JSP except that the path would be “nextCommand.m”
>> or whatever.  This might be awkward if the next command could be any of
the possible commands, but if you’re adventurous you
>> can simplify the configuration aspect of this by using an XSL on the
maverick.xml.

I partially looked into having a nextCommand.m (I did get it working) but
one of the issues that I can see is that if you return a view name that is
not correct then a ServletException is thrown by CommandBase which means
that your controller has to validate the redirect name that is stored in the
url parameter but since the views are stored in CommandBase, your Controller
cannot get a reference to the available views so you need to maintain an
independant list which admitedly could be found by parsing the Maverick.xml
file.


>> You below example seems like a perfect fit for servlet filters.
>> Have a filter defined with your "runBusinessLogic" and mapped to the
commands it applies to.

I have not used servlet filters before, I was wondering if you could maybe
give a more detailed idea of how you think this would all work with a simple
example.

>> Have you tried using the requestDispatcher directly? That should work.

Can you expand on what you mean by this, do you mean replacing with a
subclass.

 Cheers Dave