Reinhard Pötz wrote: > I want to provide a SAX buffer to the pipeline and the serializer just > passes the SAX events to it. Ah, ok.
>> As the output stream is a runtime object for the finisher it should be >> treated like other objects of this kind (the src url for the file >> generator for example etc.) which means it should be passed in through >> the parameters for the finisher. > > I'm not sure if I understand your idea: Do you propose to change the > interface this way? > > setup(Map<String, Object> outputParameters, > Map<String, Object> inputParameters); > > > The client of the pipeline API has to put the objects for the serializer > into the output parameters map and the serializer gets them passed so > that it can manipulate them? Yes, but I thought about just using: setup(Map<String, Object> parameters); so we don't differentiate between input and output parameters. Maybe two parameter maps make more sense. > The advantage compared to my proposed solution is that this way a > serializer could handle more than one output type. Right? Yes (and it doesn't create a new interface :) ) Carsten -- Carsten Ziegeler [email protected]
