> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]] > > From: "Sylvain Wallez" <[EMAIL PROTECTED]> > > > Please find below an answer I gave to a colleague on cocoon-users. After > > more thoughts, I think to have found a good example of a Serializer that > > could take advantage of both Parameters and SourceResolver... > > <snipped-real-life-needs-I-agree-with/> > > I have another need: I have a Serializer that takes a JComponent and renders > it to JPEG directly without using SVG. > I need to specify a configuration, and have access to the class that may not > be in the Classpath. > > Are there any technical reasons that still stand in the way for making > Serializer a SitemapModelComponent?
I don't think so. Moreover, CachingStreamPipeline.java already checks whether Serializer is Cacheable or not, and processes it accordingly. This means, that no caching issues should arise. I could try: 1. Add SitemapModelComponent to the Serializer, 2. Call serializer's setup() in the AbstractStreamPipeline's setupPipeline(), 3. Did I forget something else? 4. test how it works :) Vadim > > -- > Nicola Ken Barozzi [EMAIL PROTECTED] > - verba volant, scripta manent - > (discussions get forgotten, just code remains) > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
