Ooops, now I am a bit confused. - The initial request, was into the direction of aggregation. Thus I thought, the actual functionality missing is an aggregating generator (probably a more general one than is available with 2.1)
- The xslt example, I considered just being a topic for general URLs that are capable of referring back to the pipeline engine (And probably this might not be available with Corona natively) Reinhard does your answer imply, such referring back should avoid serialization and just link to pipeline events passing (e.g. SAX or whatever is passed along a pipeline)? I would have considered this an internal optimisation for event streams that are compatible to the user/caller (XSLTTransformer in the current example) Did I get it wrong? Rainer Reinhard Pötz schrieb: > Vyacheslav Sedov wrote: >> well, can i wish support of dynamic XSLT generation in addition? >> >> stage1 - xml1 -> xslt1 -> xslt2 >> stage2 - xml2 -> xslt2 -> result-xml > > The simplest way would be extending the XSLTTransformer class to also > accept an InputStream for the XSLT file (currently it only supports URLs ). > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
