Ok. I have made a first cut at this, which will allow you to update
your writers to address the @todo regarding serializing the configuration/
default configuration info.
I really wish we discussed this first and came to some sort of agreement before committing this into the classes. I still don't understand properly what you want to do or why you want to do it!
See my other post--I have some questions myself.
I am keeping an eye out on future requirements while trying to satisfy our current ones.
Remember that Avalon is bigger than just Fortress, Merlin, or Phoenix. The purpose of breaking the Meta package out is to unify how things are read and interpreted.
We can avoid lock-in using the approach I laid out.
For example, in Phoenix we have the core meta info, the mx-info, and the configuration schema. All of these are stored in separate files. The Builder interface in the SPI package only allowed for all of this information in one stream.
Things like Configuration validation and merging would be done by extensions or container plugins. Just because the reference to the .xsd file (or whatever it is) is in the Type information does not mean that the actual file is easily available. This change allows us to handle these things a little more simply.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
