At 9/20/2004 06:51 AM, you wrote:
My first idea was to use the XIncludeTransformer. The problem here is that the returned information has to be processed dynamically. So I can't simply include a returned sub-tree unmodified. (OK, admittedly I could split the stylesheet into two parts, but I still believe there must be a *nicer* way.)
My second idea was to use aggregation, so i would merge the source XML and all the XML files needed for looking-up some information while transforming. So the process would be quite the same, but I could stay within the same XML file. Despite this I find this approach a bit clumsy, because eventually I must carry along quite large XML trees just for asking for some values.
Is there sombody out there, with more elegant ideas?
How about CInclude?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
