cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <blorit...@apache.org>
Subject Re: [C2] XSP based Action
Date Thu, 19 Apr 2001 18:00:01 GMT
Jeremy Quinn wrote:
> 
> At 5:11 PM +0100 19/4/01, Allan Erskine wrote:
> >
> >Any thoughts?  The first way seems easiest...
> >
> >Allan
> 
> Thanks Allan, this is going to be very cool!
> Just when the discussion gets interesting, I am off for a weeks holiday ;>
> 
> When I get back, I start work writing our new Crudlet 2.0 TagLib, the first
> thing I'll be asking advice about, will be ....
> 
>         What is the best way to write the XMLFragment implementing support
> objects for a TagLib so that you do not have to write output code for both
> DOM and SAX?
> 
>         As Cocoon 2 is the future, it makes sense to me to "natively" output SAX
> Events, and have some sort of "adapter" to capture the events and convert
> them to DOM for output to Cocoon 1. (the opposite of DOMStreamer?)
> 
>         Does this make sense?
> 
>         Is it possible?

Is this something you can accomplish using <xsp:element> and <xsp:attribute>?
If that is the case, then let Cocoon do the hard work for you.

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message