On 30.06.2004 23:05, Terry Brick 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)!
Yes, you are absolutely correct. This is why I absolutely don't like them, they are hacks. The same is true for the SourceWritingTransformer. In the meantime there is a valid replacement available with the XModuleSource: http://wiki.cocoondev.org/Wiki.jsp?page=XModuleSource.
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
