Jörn Nettingsmeier schrieb:
[EMAIL PROTECTED] wrote:
Author: andreas
Date: Tue Nov 27 01:09:29 2007
New Revision: 598565
URL: http://svn.apache.org/viewvc?rev=598565&view=rev
Log:
Don't include xindice block but add xindice and xmldb libraries to
editors module, this avoids unnecessary entries in cocoon.xconf.
but if something is included in cocoon, isn't it cleaner to use it?
Yes, but in this case it was a bit risky since the xmldb block inserts
some snippets into cocoon.xconf (among them a servlet declaration).
First I started to add xpatch files which remove these snippets, but
that's not something I'd like to maintain ...
i
wonder what happens if a user wants to use the xindice block in a
deployment, and all of a sudden there are possibly conflicting jars
around... what do we gain by this?
Less Cocoon-block-specific xpatch files. But of course shipping a copy
of the libs is not an optional solution either. Maybe we could provide a
way to use the Cocoon libs without including the blocks?
If you don't object I'd like to leave it as it is now and, after 2.0,
either replace the forms editor by something else or implement a more
sophisticated way to utilize the Cocoon libraries.
WDYT?
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
