On Jul 15, 2008, at 18:33, Carsten Ziegeler wrote:
Peter Hunsberger wrote:
On Tue, Jul 15, 2008 at 5:42 AM, Reinhard Pötz
<[EMAIL PROTECTED]> wrote:
Are you talking about passing the input parameters as parameters
of the
setup() method?
void setup(Map<String, Object> inputParameters)
I'd be fine by this.
I hate seeing Maps used as dumping grounds for randomly typed
objects.
Could you use something that gives a little more strong typing?
Perhaps more like a ServletContext though I don't think I'd go that
far in this case?
I agree that strong typing would be great - but the pipeline api
does not define any concrete key/object for the map. So this is use-
case specific. Therefore I think a map is the best we can come up.
The question if those configuration are needed in a generic form in
the API. (I doubt it) As I would expect them to be implementation
specific a configuration callback that sets up the pipeline might be a
way around this?
Just my 2 cents
cheers
--
Torsten
