[EMAIL PROTECTED] wrote: > Hi folks, > > can someone tell me if its possible to create a DOM out of a > currently present SAX event in a pipeline (before the pipeline > becomes serialized)? Not to confuse you, the pipeline would for sure > use the current SAX event for further computation and not the DOM. In > other words, I'd like to have the current status of the pipeline (so > the current SAX event) as kind of input stream for the generation of > a DOM which becomes instantiated in e.g. an XSP file within this > specific pipeline.
i'm neither a sax nor a cocoon expert, but iiuc this is impossible, since at most points in time a stream of sax events does not yield a correct xml dom tree (this is only the case after the last endElement event or whatever it's called has been received). because of this, dom does not make a lot of sense in pipelines: dom implies that you have to wait for the complete set of xml data before you can do anything useful with it, and the basic idea of pipelines is sequential processing. -- "I don't need backups. I need restore!" - Trad. -- Jörn Nettingsmeier, EDV-Administrator Institut für Politikwissenschaft Universität Duisburg-Essen, Standort Duisburg Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
