><snip/> >> > At the same time, everybody considered the sitemap one of the core >> > features of Cocoon and, for sure, this isn't going to go away any time >> > soon (not even for Cocoon 3.0). this doesn't mean we can't innovate or >> > propose alternative solutions to cohexist, but for now, I'd concentrate
>> > on keeping our design focus on what we have. >> >> I certainly wouldn't expect sitemap to go away, even if the capability >> I suggest was implemented. In particular, one might want to use both >> capabilities, directing only some URIs to the router type XSLT that >> I'm looking at. Depending on how it was implemented one might also >> want to use the sitemap to specify how the context for the router XSLT >> was built up (aggregation patterns). > > Couldn't you do this very simply (well...) with a URIResolver? (yes) > > Hook up the URIResolver to to cocoon generators, transformers what-have-you Unless I'm missing something I don't think that's really the problem; I'd still need the equivalent of an XSLT:transform tag to tell the stylesheet to jump to another stylesheet once it figured out who to call... Maybe I'm looking at the problem up-side down? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
