Leszek Gawron wrote:
Carsten Ziegeler wrote:
With the help from Leszek we now have a Cocoon version in trunk which
which was rather small and of questionable quality, thanks for the
credit tough :)
does not need any deployment plugin. This means you can just drop the
jar files into WEB-INF/lib and are done! So it doesn't matter if you're
using Maven, Ant or some other strange tool :)
All you need is the main Spring applicationContext.xml with our two
elements for setting up Cocoon and the Avalon bridge.
So, what has changed?
We now load all configuration files directly from within the jar files,
so all files in META-INF/cocoon/avalon, META-INF/cocoon/spring and
META-INF/cocoon/properties are applied at runtime without the need to
extract these files.
do we need to load configuration files from WEB-INF/cocoon/*? After all
if one wants to have configuration unpack it may be done using
WEB-INF/classes/META-INF/cocoon/*. Same result. No duplication.
CocoonPropertyOverrideConfigurer could be then simplified. We could drop
scanClassPath and just provide a 'location' attribute which is
classpath*:/META-INF/properties for core and ./config/properties for
blocks.
So we could remove:
<!--+
| Include all configuration files ending with ".xconf"
| from the xconf directory.
+-->
<include dir="context://WEB-INF/cocoon/avalon" pattern="*.xconf"/>
and this from cocoon.xconf
--
Leszek Gawron CTO at MobileBox Ltd.
