Leo, I dont think having scripting configuration should override current XML config model.
<disclaimer>I'm not sure to understand exactly your point</disclaimer> Having script means knowing another language (even javascript is far from java). Also XML is now well known for most of the sysop, and proposing them "exotic" config file could fear them. XML config files are human readable, and application friendly (I mean you could have for exemple a main application that could generate XML config for all your running apps). What could be done is having "Scriptable" components (such as Initializable, or Configurable) that could be scripted during component lifecycle. Cheers --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
