At 10:01 23/4/01 +0200, Leo Simons wrote:
>> How about also having one file say blocks.xml that describes all
>> the blocks
>> and from which xinfo and provide part of assembly.xml could be generated.
>
><snip>
>
>> what do you think ?
-1 defeats the purpose of composing in a component based system.
>I've not been fond of the configuration system ever since I
>saw it. I would like to have a single config file per .sar,
you mean like we do? (conf/config.xml)
or
>one per .bar if the file otherwise becomes to large. Additionally,
>you might want to be able to include a security.policy on a per-sar
>basis.
like we do ? (conf/server.xml?server/policy)
>This is not something to change lightly - changing the mechanism
>means everyone who uses it to rewrite their files. Then again, I'd
>say we cannot change this for a long time after we go beta.
But remember that it was set up this way for a very specific reason - it
separates out the roles developer/assembler/deployer/admin. (Thou deployer
and admin are practically the same in our current model). The benefits of
this design may not be seen now but in time will become obvious.
>Note: I will probably set up phoenix so you can configure most
>of it through a conf/phoenix-conf.xml file, if no-one objects.
that was vetoed ages ago but maybe if you put a good case for it ;)
(especially once we actually have some pluggable facilities).
>one more note: long term prediction - the use of xml for configuration
>files will decline once it becomes easy to pass a configuration
>object through JMX.
XML will still be required as part of deployment descriptor. Whether it
stays in that form or goes in via LDAP/XML/JMX/whatever is largely
irrelevent (I personally want LDAP).
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
