Also, not to start a flame war or anything, but isn't 'avalon.dependency' just as much a 'validation' issue as context, logging, and configuration tags? I mean, it's just the container validating that such services exist and allowing the component to access them. I don't see the difference between this and say 'context'. But perhaps I'm wrong.
the thing is, how to do configuration validation is clear. You have an XML file, you can write a DTD or a relaxng schema or something like that and have the container apply it.
How to do dependency validation is also clear. We have several years of experience developing the composition part of the container-component contract. All we want to do here is to verify our composition graph is not cyclic, and to do that up front you need to specify that graph up front, which you can do intuitively by the use of attributes.
How to do context and logging validation is less clear. The only place where something like that is supported is merlin, and there it has only recently been put to the test by various people.
Also, the need for context and logging validation is less clear. That's why this needs all the fleshing out being done :D
cheers,
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
