>>And what do you want to do with map:aggregate? >> > > We keep the "cocoon:" protocol for this. But I always have been > frustrated that map:part only accepts a simple "src", and would love to > be able to put sitemap statements in it. But that's another story...
Boy, would I like to see this addressed. It looks like eventually we'll stop using aggregation (source everything out of our own generators that do their own aggregation internally), but I've been frustrated by this many times! > I thought of defining some "not-used" generator and serializer, if you > really want to constrain a particular use of a pipeline. These would for > example simply throw an exception explaining that this pipeline is not > used as expected. How about a "null" generator and serializer, since using a "not-used" generator has sort of an odd syntax? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
