Daniel Rall <[EMAIL PROTECTED]> writes:
>Couldn't that be said about all Turbine properties? TR.props
>pre-dated the addition of deployment descriptors to the spec by years.
Please remember, that I did a shy proposal in January to rename the
TurbineResources.properties to Turbine.properties because we no longer
have a "TurbineResources" Service...
There was consensus on this. I'd like to do this, once 2.3 is out of
the door and all references to the TurbineResources Service are
finally gone. I already have a patch for this...
>When ever possible, all properties should be consolidated in the same
>place.
Hm...
% cd deploy/conf ; ls *.properties
Fulcrum.properties
Turbine.properties
domainverwaltung.properties
framework.properties
mailboxverwaltung.properties
mailumleitung.properties
ticketverwaltung.properties
userinterface.properties
webfarm.properties
wizard.properties
and yes, they all are merged to constitute the actual application
configuration.
% tail -9 Turbine.properties
include= Fulcrum.properties
include= domainverwaltung.properties
include= framework.properties
include= mailboxverwaltung.properties
include= mailumleitung.properties
include= ticketverwaltung.properties
include= userinterface.properties
include= webfarm.properties
include= wizard.properties
It would be terrible if Turbine wouldn't support multiple-location
Application configuration... JNDI would be bliss but I can live with
properties files.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
