: [Mav-user] additional configuration for commands
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
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
-Original Message-
From: Taavi Tiirik [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 5:18 AM
To: [EMAIL PROTECTED]
Subject: [Mav-user] additional configuration for commands
Please enlighten me :-)
I would like to specify some additional configuration
parameters for my
PROTECTED]
-Original Message-
From: Shackelford, John-Mason
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 11:23 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [Mav-user] additional configuration for commands
Jeff,
It would be easy enough to split up the params
Message -
From: Schnitzer, Jeff [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
To: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 12, 2003 10:10 PM
Subject: RE: [Mav-user] additional configuration for commands
Ah, right now there is just one set of params and each place
