On Tuesday 11 June 2002 07:35 pm, Peter Donald wrote: > > Another key difference is that the Cocoon model has a requirement > > to re-connect the hint mappings at runtime--whereas the Merlin > > model does it all at init time. > > Can you explain that? You aquire components based on request parameters but > the request parameters supply constraints and not hints (ie "ssl" vs > "xalan").
Cocoon's pipelines are assembled dynamically at runtime. The main pipeline component types are Generators, Transformers and Serializers. Each one is implemented as a ComponentSelector with the hint specifying which component to use. For an example: <map:generate type="file"/> <map:transform type="xslt"/> <map:transform type="custom"/> <map:serialize type="xml"/> The java code is akin to ComponentSelector generatorSelector = cm.lookup( Generator.ROLE ); Generator g = generatorSelector.select( "file" ); ... etc etc. I don't see why there can't be a specific GeneratorManager that is returned to let you specify specific generators. The GeneratorManager, TransformerManager and SerializerManager would all be nearly identical though, thus the thinking of abstracting out ComponentSelector-style. -pete -- peter royal -> [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
