Carsten Ziegeler wrote:
Leszek Gawron wrote:
<SNIP>
The blocks consists of:
- COB-INF resources (covered with mount in sitemap)
- java classes (loaded on sitemap level with reloading classloader, now
gets me thinking it will break if block supplies some core spring beans)
- avalon contexts (covered by include in cocoon.xconf)
- spring contexts (covered by include in cocoon.xconf)
- sitemap additions (covered by include in cocoon.xconf)
- properties
- those in src/main/resources/COB-INF/config/properties/ covered by
automatic loading in block sitemap
- those in src/main/resources/META-INF/properties are NOT COVERED
Thanks for the nice overview, Leszek - I've never used it this way.
To be honest, I have no good idea how to solve this. But I think putting
these include into the xconf is not the right way :(
Your proposal to use a system property would work. But its ugly. You
would need to have this configured in every pom.xml:
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty6-plugin</artifactId>
<version>6.0.0beta10</version>
<configuration>
<connectors>
<connector
implementation="org.mortbay.jetty.nio.SelectChannelConnector">
<port>8888</port>
<maxIdleTime>30000</maxIdleTime>
</connector>
</connectors>
<webAppSourceDirectory>target/${artifactId}-${version}</webAppSourceDirectory>
<contextPath>/</contextPath>
<systemProperties>
<systemProperty>
<name>org.apache.cocoon.mode</name>
<value>dev</value>
</systemProperty>
<systemProperty>
<name>org.apache.cocoon.additional.property.directory</name>
<value>/src/main/resources/META-INF/properties</value>
</systemProperty>
</systemProperties>
</configuration>
</plugin>
It should not be something that needs configuring in pom.xml. This
configuration issue should go directly somewhere into /target/cocoon-webapp
--
Leszek Gawron, IT Manager MobileBox sp. z o.o.
+48 (61) 855 06 67 http://www.mobilebox.pl
mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
