cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From peter royal <pro...@apache.org>
Subject Re: Jelly as treepressor was: rollback Cocoon 2.2 and do Fortress merge later
Date Tue, 04 Nov 2003 11:53:27 GMT
On Nov 4, 2003, at 5:03 AM, Stephan Michels wrote:
> But I see following problems:
>
> 1. Every tag seems to produce some XML content:
>
> // pass the output of the script somewhere
> Writer someWriter = new FileWriter( "output.xml" );
> XMLOutput output = XMLOutput.createXMLOutput( someWriter );
>
> // now run a script using a URL
> JellyContext context = new JellyContext();
> context.runScript( "foo.jelly", output );
> -------
> public class FooTag extends TagSupport {
>
>   public void doTag(XMLOutput output) {
>             ...
>   }
> }

That's only an option. You can pass what is essentially a NoopXmlOutput 
that doesn't output anything.

> 2. We configure components in the sitemap, which
> means we have some XML code, which should be processed.
> IHMO, its not a bad move to get rid of the configurations.
> Most cases can be solve by using Parameterizable.

That can still be captured and turned into a Configuration object, as 
it is currently.

> 3. Jelly seems to need a <jelly> root element.

You can have your own root element.

-pete


Mime
View raw message