> Look through the archives - unless I misunderstand you this > has been discussed ad nauseum. In your case, there is an > xsp tag to cause the value of your parameter to be parsed > as xml and passed down the line of SAX events.
I did a quick pass over the mailing list archives but didnt see anything. I'll search a little harder - I did figure that had to have been something people had problems with in the past. But something like an xsp attribute or tag sounds exactly like what I'm trying to find. > Keep in mind, a cocoon pipeline is not a text stream of xml, > but a sax event chain. inserting new text into a character > event at one point does not create a new startElement, etc. > unless explicitly instructed to do so. This saves us from > continually reparsinng the xml as it moves through. Makes sense. Thanks, - Brent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
