[EMAIL PROTECTED] writes:
>Secondly,
>I am thinking about the CompositeConfiguration stuff as working somewhat
>similar to how the various schedular jobs are listed in the TR.props.
>Basically something like this:
>services.ConfigurationService.configurations=propertiesSource,JNDISource
>services.ConfigurationService.configurations.propertiesSource.file=/web-inf/
>conf/MyProperties.props
Then we're back on "ResourcesService", which got removed for 2.3-dev.
The problem with "logging" and "configuration" is, that these are
special. You simply can't move this stuff into services without
starting to build loopholes and shortcuts, because without logging and
configuration, you can't do very much else.
>services.ConfigurationService.configurations.JNDISource.prefix=java:comp/env
Stuff like this must IMHO come from the web.xml or from a very very
small "meta" configuration file (which might simply be a sub category
of the TR.props) that gets parsed only with Properties or XML
Configuration.
Using a service for this got tested in T2.0 and T2.1 It does not work.
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]
