-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 17 May 2006, Daniel Fagerstrom wrote:
Date: Wed, 17 May 2006 13:12:11 +0200
From: Daniel Fagerstrom <[EMAIL PROTECTED]>
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: RAD with Cocoon 2.2
Reinhard Poetz skrev:
Maven brings a lot of advantages to standardize the development process
but also makes development of applications more difficult as you spread
your applications over different artifacts.
In the light of this I think we should revert our removal of the
per-sitemap classloading
(http://marc.theaimsgroup.com/?l=xml-cocoon-cvs&m=114150323011155&w=2). As
the removal was part of a refactoring of the sitemap engine, could sombody
give me a description of what needs to be done?
I agree that RAD is important, but I would prefer to put the dynamic
classloading in the block level container rather than within the sitemap.
Component handling within the sitemap is mix of concern IMO. I know that it
has been a must for this far, as sub sitemap has been the only mechanism for
modularization. But with blocks we have a much better mechanism for
modularization so I think we should focus on that and maybe even deprecate
the sitemap component declarations.
Nah, how about a block that itself has sub-sitemaps (to modularize block
concerns)? I don't like it to be deprecated exactly because of that.
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEbBzYLNdJvZjjVZARAsJcAKDH43jWAkLwYDIqJuTgHW3I7nayiQCgilgw
RZWVcTbZreufnctc1w0zSe8=
=iTTw
-----END PGP SIGNATURE-----
