> 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
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, 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.
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.
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.
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.
regards,
LSD
<java:sig>
About LSD = new PersonalInfo();
LSD.name("Leo Simons");
LSD.email("[EMAIL PROTECTED]");
LSD.URL( [
http://www.leosimons.com, // personal website
http://www.atfantasy.com, // fantasy RPG portal
http://www.the-sign.nl // web-design company
] );
LSD.quote("Buh!");
email.setSig((String)LSD);
</java:sig>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
