Ok - I've taken a look and to be honest - I don't understand what this is for - don't get the value it provides - I don't like the fact that its non-serializable which in turn means that the creators break because the serialized and non-serialized result will be different. As a result I think MetaInfoLocator should not be included in the Type defintion.
It is marked transient so it is never serialized.
If you really need something loike this then start thinking about defining a meta-info service under the SPI package - that takes a Type and an extension key as an argument. There simply isn't any reason to include this into the core Type defintion.
A plugin will require access to the info it provides. If it goes in the SPI package then we admit that there is no reason for the SPI package. Container and plugin requirements are identical.
--
"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]
