Re: [RT] Component confs per sitemap
Carsten Ziegeler wrote: The current solution for adding own components to Cocoon is to (optionally) add the role to the cocoon.roles file and to add the component (configuration) to the global cocoon.xconf file. What about providing the possibility to add components/roles on a per sitemap level? For example by providing a reference from within a sitemap in the map:components sections: map:components roles-file=... config-file=... .. /map:components So all of these components are available in this sitemap and in all subsitemaps. Adding this (to 2.2) should be very easy and makes adding own stuff imho easier. (As a second step - but this is independent it would be possible to move all definitions of sitemap components into these files as well, leaving just the pipelines in a sitemap). WDYT? i like this. please start a vote so that we don't have to discuss in 6 month whether it was a community decision or not. -- Reinhard
[RT] Component confs per sitemap
The current solution for adding own components to Cocoon is to (optionally) add the role to the cocoon.roles file and to add the component (configuration) to the global cocoon.xconf file. What about providing the possibility to add components/roles on a per sitemap level? For example by providing a reference from within a sitemap in the map:components sections: map:components roles-file=... config-file=... .. /map:components So all of these components are available in this sitemap and in all subsitemaps. Adding this (to 2.2) should be very easy and makes adding own stuff imho easier. (As a second step - but this is independent it would be possible to move all definitions of sitemap components into these files as well, leaving just the pipelines in a sitemap). WDYT? Carsten Carsten Ziegeler Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.net/weblogs/rael/
Re: [RT] Component confs per sitemap
On Fri, Dec 17, 2004 at 03:06:20PM +0100, Carsten Ziegeler wrote: The current solution for adding own components to Cocoon is to (optionally) add the role to the cocoon.roles file and to add the component (configuration)to the global cocoon.xconf file. What about providing the possibility to add components/roles on a per sitemap level? For example by providing a reference from within a sitemap in the map:components sections: map:components roles-file=... config-file=... .. /map:components So all of these components are available in this sitemap and in all subsitemaps. Adding this (to 2.2) should be very easy and makes adding own stuff imho easier. (As a second step - but this is independent it would be possible to move all definitions of sitemap components into these files as well, leaving just the pipelines in a sitemap). WDYT? I like both ideas, because they allow more modular configuration. It seems this may also help with virtual hosting via subsitemaps? Could we allow live updates from changes made to the roles-file and config-file like we do for changes to sitemaps? --Tim Larson
RE: [RT] Component confs per sitemap
Tim Larson wrote: I like both ideas, because they allow more modular configuration. It seems this may also help with virtual hosting via subsitemaps? I think so, yes. Could we allow live updates from changes made to the roles-file and config-file like we do for changes to sitemaps? Sure. Carsten
Re: [RT] Component confs per sitemap
Carsten Ziegeler wrote: The current solution for adding own components to Cocoon is to (optionally) add the role to the cocoon.roles file and to add the component (configuration) to the global cocoon.xconf file. What about providing the possibility to add components/roles on a per sitemap level? For example by providing a reference from within a sitemap in the map:components sections: map:components roles-file=... config-file=... .. /map:components So all of these components are available in this sitemap and in all subsitemaps. Adding this (to 2.2) should be very easy and makes adding own stuff imho easier. (As a second step - but this is independent it would be possible to move all definitions of sitemap components into these files as well, leaving just the pipelines in a sitemap). WDYT? There was a discussion on this very topic (with pretty much the same proposal) here while you were on vacation. However, as I recall it was under one of the topics that I believe you deleted. :-) You just can't go on vacation anymore! I love the idea - especially moving the component definitions into the xconf file. Small sitemap files are good. Ralph
Re: [RT] Component confs per sitemap
Carsten Ziegeler wrote: . What about providing the possibility to add components/roles on a per sitemap level? Where do I sign? 8-) -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
Re: [RT] Component confs per sitemap
Le 17 déc. 04, à 15:06, Carsten Ziegeler a écrit : ...map:components roles-file=... config-file=... .. /map:components So all of these components are available in this sitemap and in all subsitemaps. Adding this (to 2.2) should be very easy and makes adding own stuff imho easier... Sounds great, +1! -Bertrand smime.p7s Description: S/MIME cryptographic signature
RE: [RT] Component confs per sitemap
Ralph Goers wrote: There was a discussion on this very topic (with pretty much the same proposal) here while you were on vacation. Ups. However, as I recall it was under one of the topics that I believe you deleted. :-) Yepp...[sound of Carsten whistling]... You just can't go on vacation anymore! :) Ok, I just reread the thread you're refering to and it seems to me that noone was against it, right? So does anyone mind if I just implement it? Carsten I love the idea - especially moving the component definitions into the xconf file. Small sitemap files are good. Ralph
RE: [RT] Component confs per sitemap
Carsten Ziegeler said: Ok, I just reread the thread you're refering to and it seems to me that noone was against it, right? So does anyone mind if I just implement it? Carsten Are you done yet? (That's a big +1). Also, once you have this working it would be nice to see if it could be back-ported to 2.1 in a compatible manner. Ralph
Re: [RT] Component confs per sitemap
Carsten Ziegeler wrote:
The current solution for adding own components to Cocoon is to (optionally)
add the role to the cocoon.roles file and to add the component
(configuration)
to the global cocoon.xconf file.
What about providing the possibility to add components/roles on a per
sitemap
level? For example by providing a reference from within a sitemap in the
map:components sections:
map:components roles-file=... config-file=...
..
/map:components
So all of these components are available in this sitemap and in all
subsitemaps.
Adding this (to 2.2) should be very easy and makes adding own stuff imho
easier.
(As a second step - but this is independent it would be possible to move all
definitions of sitemap components into these files as well, leaving just the
pipelines in a sitemap).
WDYT?
+1. You already can put any component declaration in map:components,
so it's actually just a matter of reading this declaration in an
external file.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
RE: [RT] Component confs per sitemap
Ralph Goers wrote: Carsten Ziegeler said: Ok, I just reread the thread you're refering to and it seems to me that noone was against it, right? So does anyone mind if I just implement it? Carsten Are you done yet? (That's a big +1). No, I'm currently rewriting/cleaning up parts of ECM++ and when that is done, I will start with the configuration stuff. I hope to get everything finished before xmas. Also, once you have this working it would be nice to see if it could be back-ported to 2.1 in a compatible manner. Yeah, this should be possible, but my opinion is that it should just go into 2.2 as it is kind of a major addition. That's just my opinion, so if the majority is for 2.1 I'm fine with it. But let'S just get it running in 2.2 and then see what we do about it. Carsten
RE: [RT] Component confs per sitemap
Sylvain Wallez wrote: +1. You already can put any component declaration in map:components, :( You know my opinion about ;) so it's actually just a matter of reading this declaration in an external file. Yes, with the additional that this is then *official* and *supported* :) Carsten
