Nicola Ken Barozzi wrote: > Why use Cocoon at all? Pipelined XML processing is great. Also, Cocoon is really great for mapping URLs to content. Including dynamic content (with some work flow support it would be even better).
As for Cocoon aggregation vs. document(): aggregation is good if the structure of the aggregated stuff is relatively static. It's somewhat clumsy if parts of the URLs come from the XML source, and in particular if the number of aggregated parts varies. In these cases you need a three stage pipeline: transformation to xincludes, doing the actual include, then the final transformation. This split of the whole process into two transformations can be an advantage, but in most cases I found it more of a problem during maintenance. > You need the right tool for the right job. Indeed. J.Pietschmann --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
