On Monday, March 11, 2002, at 09:40 am, Carsten Ziegeler wrote:
> a) Sitemap components in the cocoon.xconf.
> Now, personally I don't like this - but that's my own opinion about
> this.
> If you want to edit the sitemap, you not only have to look at the
> sitemap
> but also at the cocoon.xconf. This makes handling the sitemap even more
> complicated.
> I know a lot of people complaining about the complexity of Cocoon and
> the many places of configuration. By this splitting of component
> definition
> it gets even harder for beginners.
> So I would like to have all these definitions back in the sitemap.
> What is the benefit of having them in the cocoon.xconf?
We have a growing number of sites under development that use a common
configuration. Being able to put all the general cocoon configuration
in the cocoon.xconf file (configuration that requires knowledge of Java
class names and is quite often impacted by updates to cocoon and its
components), and keep site specific stuff in one or more "sitemap.xmap"
files is definitely beneficial.
Otherwise, every time Cocoon is updated we have to compare the diffs of
the supplied sitemap with the previous supplied version and implement
these in all our sitemaps. If, on the other hand, all of this is in
cocoon.xconf, we may be able to just get away with using the supplied
file (but for database configuration).
If we want to reduce complexity I would be in favour of deprecating the
facility for declaring components within sitemap.xmap.
Stuart.
Public Key - 1024D/88DD65AF 2001-11-23 Stuart Roebuck (Adolos)
Key fingerprint = 89D9 E405 F8B1 9B22 0FA2 F2C1 9E57 5AB1 88DD 65AF
-------------------------------------------------------------------------
Stuart Roebuck [EMAIL PROTECTED]
Systems Architect Java, XML, MacOS X, XP,
etc.
ADOLOS <http://www.adolos.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
