Vadim, I like this as an elegant way to "go outside" the main flow, do something and continue. The important factor is the ability to script the behavior, change of the script produces changes of the behavior. > > Vadim, > > The document you are sending contains two <Body> in the case of this > example > > it will not work. <Body> is expected to be unique. Invent some other > > modification of the document. > > How come? It works! When <body> are embedded in each other - it works. You are right, what I mean was no <Body> siblings are not allowed.
> > Looking at all this I see an opportunity to rewrite all SQL / LDAP / > XMLDB / Include / I18N / Lucene / etc transformers as a single > Dispatcher and a bunch of handlers, reacting on namespaced tags, and > working on a SAX stream. What do you think? It is very interesting possibility... > > On the other side, it reminds me somehow about reactor pattern in the > Cocoon 1 and that it was not good enough for some reason... I am free from "old reactor" fillings... and I see in this powerful and simple mechanism. Kinga > > Vadim > > > Kinga > > > > > -----Original Message----- > > > From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]] > > > Sent: Thursday, February 07, 2002 7:18 PM > > > To: [EMAIL PROTECTED] > > > Subject: RE: Dispatcher/Adapter > > > > > > > > > No, I used online sample with: > > > > > > <Envelope> > > > <Body> > > > <SomeTag>This is a part of the Body node tree</SomeTag> > > > </Body> > > > <Body> > > > <SomeTag>This is a part of the Body node tree</SomeTag> > > > </Body> > > > <OtherTag>This is not a part of the Body node tree</OtherTag> > > > </Envelope> > > > > > > :) > > > > > > Vadim > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
