> I would think this is the kind of application where you would want "deeper" > pipelines... In other words you could have 2 levels of XSP processing, the > first level can deal with taglib x, and the 2nd can deal with taglib y. In > many cases you can simply use 2 namespaces and combined functionality of > several taglibs, but there are cases like PerForm where that may not be a > good solution, so hence deeper pipelines, maybe even something like XSP -> > XSLT -> more XSP -> more XSLT... >
I thought about doing this, XSP -> XSP ->..., but then the output of my first XSP stage should still be a valid XSP document. Boris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
