Jeremy Quinn wrote:
> 
> At 00:25 +0200 02/09/00, Stefano Mazzocchi wrote:
> >
> >Torsten Curdt wrote:
> >>
> >> > Only XSP that used DOM directly (AND WE TOLD YOU NOT TO DO IT!) will be
> >> > hard to port, anything else will be piece of cake.
> >>
> >> Oh, oh! Nobody told _me_! Our JavaBeans produce DOM elements
> >> and we insert them via XSP! So this is no longer possible in
> >> Cocoon2??
> >
> >No, that's different.
> >
> >What I mean is to play around with the internal DOM objects from inside
> >the xsp:logic sections. This is -not- goint to be portable because there
> >will be no more DOM object to play with since C2 uses SAX internally.
> >
> >Hope this is clear enough.
> 
> OK, as an example, at the moment FP TagLib adds Attributes to the parent
> Element of the FP Tag (to report action/failure). This behaviour will not
> be possible under Cocoon 2, correct?

if you use the "correct" <xsp:attribute> this is already possible and
portable.

> The Element that the TagLib hands back to XSP however, will be handled.
> Is this right?

If you use <xsp:element> and <xsp:attribute> both are supported.

If you use DOM calls in your <xsp:logic> section this will NOT be
portable.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------
 Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------