Stefano: This actually gives me a feeling of defining components "below" the sitemap, lol. I think it's a good solution, though :). It definitly solves both my deployment of application issues and the whole "complicated looking sitemap" problem.
Sincerely, Jay Freeman (saurik) [EMAIL PROTECTED] ----- Original Message ----- From: "Stefano Mazzocchi" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, August 23, 2003 8:51 AM Subject: Re: [RT] Improving Sitemap and Flowscript ... > Ok, here is what I think it would be wise to do: > > 1) leave cocoon.xconf as is > > 2) allow the sitemap to get components configurations from an external > file or from an inside definition (as today). > > 3) write our main sitemap pointing to its components to an external > file. > > The proposed sitemap syntax is something like > > <map:sitemap> > > <map:components src="blah.xconf"/> > > <map:pipelines> > ... > </map:pipelines> > </map:sitemap> > > In case, both src="" and internal components are defined, these > overload the ones included in the file. > > How does this sound? > > > -- > Stefano.
