On 14.11.2003 21:37, Ralph Goers wrote:

It's been said before on this list, the cocoon download is pretty cool for
people who want to play around with it and kick the tires.  It doesn't work
for those of us who want to use it as a presentation framework and integrate
it into our webapp (i.e. - we DON'T want to integrate our webapp into
Cocoon).  IMHO, the biggest problem is cocoon.xconf.  I want to extend it
with my own xconf file without modifying cocoon.xconf itself.

We integrate Cocoon into our webapps - and not the other way around. And IMO that's not difficult. We build Cocoon and copy the Cocoon libs from Cocoon's build/webapp/WEB-INF/lib to our WEB-INF/lib at build time. All the conf files like cocoon.xconf, logkit.xconf and sitemap.xmap we copy once at the beginning of the project. These files are fortunately that stable, that they must not be adapted for every minor release. The last time I updated a simple project from Cocoon 2.0.x (don't know exactly) to 2.1 I replaced the conf files complerely and copied my changes afterwards by hand. This is exactly the work you fear, but as I said for minor releases you normally do not need to update the files.


But, yes, it would be good to segregate your part of the file from Cocoon's one. An importing mechanism would also allow to segregate the current block xconf's from core xconf. What about entities or xinclude (with the need of recent Xerces) as temporary solution? And what about copying cocoon.xconf from the Cocoon build at every build of your webapp to your webapp and xpatch it? This also means that I don't see the hard problem needing much time.

Also, I'm not happy that Cocoon is STILL shipping (as of 2.1.2) snapshots of
the components it uses. I really need to be able to reliably grab the source
code for those and be sure it is what I am running with.

This issue was almost completely fixed for Cocoon 2.1.3. Remaining unreleased libs are jxpath (bugfix), resolver (I guess we can upgrade to 1.1) and our rhino (it's our branch) for the core, betwixt (scratchpad), geronimo jms (jms), slide (slide)and xreporter (woody) => all for unstable blocks.


Joerg


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to