Please enlighten me :-)
I would like to specify some additional configuration
parameters for my maverick commands in maverick.xml.
Something like this is what I came up with:
command name=orgunit
controller class=ee.tvi.eris.ctl.orgunit.Orgunit
param name=required-roles value=role1/
Jeff,
It would be easy enough to split up the params collection
into three separate collections.
I'd be interested in hearing more about why we'd want these separate since
seperating them adds complexity to the API. If we need the sperate names
spaces, great. If not, why bother?
John-Mason
Jeff,
I have no problem with that.
-- Mike
On Wednesday, February 12, 2003, at 12:10 PM, Schnitzer, Jeff wrote:
Ah, right now there is just one set of params and each place that
defines params (controller, view, transform) just adds to the pile.
Perhaps different behavior is desirable.
It
The problem just brought up was that the redirect view interprets params
as actual request parameters to append to the URL. Setting parameters
to the controller inadvertently causes them to show up in a redirect.
That seems like a compelling reason for separate namespaces.
Jeff Schnitzer
[EMAIL
Thanks for the update, but I couldn't get the new code to work, maybe
that's what you meant by not supporting the file stuff yet ! grin
I was trying to set enter something like:
getServletContext().setAttribute(Dispatcher.KEY_CONFIG_FILE,
file:///whatever/maverick.xml);
I think that
I have no problem with this.
As for me, though behaviour isn't what is expected, the case is too uncommon to
introduce new methods. Maybe there is a way to change behaiviour to what it should be
without changing API? I don't see it, but maybe it's possible...
Cheers,
Yura.
- Original
