Correction... this should only apply to ReadDOMSessionTransformer, not WriteDOMSessionTransformer.
--- Terry Brick <[EMAIL PROTECTED]> wrote: > I guess I'm just not grasping some concepts. Could somebody explain to me why we > have > ReadDOMSessionTransformer and WriteDOMSessionTransformer instead of > ReadDOMSessionGenerator and > WriteDOMSessionGenerator? > I mean, shouldn't a tranformer take existing XML in the pipeline and transform it > using XSL? > Well > my DOM object is in the session, not the pipleline.... > I ask this because I have a situation where I need to put a DOM that's in the > session into the > pipeline and THEN transform it... but Cocoon is complaining that I'm trying to > transform > something > without a generator first! But the XML i need to 'generate' is only accessible by > the > 'transformer' (ReadDOMSessionTransformer)! > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
