In order to solve "model" issues much easier and much more flexibly,
What "model" issues are your referring to?
Keep in mind that the Avalon Meta package is about meta-info associated with component types and service definitions. There are no issues with this that I am aware of. Certainly nothing has been posted to the list on this subject.
I propose to use the work that Leo did a while back with the Attributes embedded in the class file itself. It is a much more flexible way of doing things which will not require future
modifications to the meta model to take care of enhancements.
The only enhancement I am aware of is the discussion concerning code security. That could be easily addresses under the current approach by extending the definition without breaking any existing component meta-info definitions.
Can we go back to the underlying reason for the proposal, and secondly, how the proposal will ensure that existing XML and serial representations are supported.
Cheers, Stephen.
-- |------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
