I think this was already brought up a few weeks ago related to which
core modules would be always included by default when DSO ran. I
briefly mentioned that it might be a good idea to create a standard
properties format to pass along to modules similar to:
(maybe there's a preference for not using attributes though)
<modules>
<module name="terracotta-cache" version="1.0.0">
<properties>
<property name="ehcache.evictor.pool.size" value="1"/>
</properties>
</module>
</modules>
Maybe this is indeed better than shoving stuff into tc.properties.
However, tc.properties could still be used to setup the default
values of properties in case the user doesn't configure them. I think
that it's a nicer way to centralize the default behavior than to
scatter it around the code base in Java.
On 04 Sep 2007, at 22:25, Tim Eck wrote:
> I noticed this morning that tc.properties contains some entries
> specific to the ehcache dso config-module/bundle/plugin thingy.
> Got me thinking that maybe tc.properties isn’t the right place to
> put something like that.
>
> I don’t want this thread to turn into a conversation of
> tc.properties vs. tc-config.xml. That said, it seems like each
> module should maybe have some standard means for including and
> using properties. Any ideas on what form that would take? Any ideas
> on how an end user would tweak on those properties?o/tc-dev
>
--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
