Hi All,
Hope all is well.
Currently in our project we're doing an internal migration from
hand made classes to avalon components (yippee!).
We've come across the occasion several times where we would like to
access a global configuration value, set outside of that
components configuration hierarchy in an xconf file.
I've brought this up before in an earlier post, and a
suggestion from Giacomo was to use ECM's Context to store these global
values.
I like this idea, but it means having to manually read the
configuration file before passing it onwards to ECM.
No problem, but how about automating this a little by enhancing
ECM/ComponentManager so that root level attributes in xconf files are
automatically added to ECM's Context ?
ie:
<application version="value" variable1="value" variable2="">
<component>
...
</component>
...
...
</application>
...
String version = this.context.get("version");
This would remove the need to do this step manually, and would
provide a nice place for globals.
Thoughts ? Comments ?
Cheers,
Marcus
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: ManageSoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&'
&&&&.
&&&&&&&:
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
