On Aug 27, 2005, at 11:41 AM, Aaron Mulder wrote:
How about a must have to implement GBeanName according to the
previous notes on the mailing list?
Does this include modifying all code to use GBeanName instead of
object name? If not, I think we should simply remove GBeanName
instead because it makes the kernel confusing. The Kernel interface
has methods that take object names, and if a subset of ObjectNames
are invalid for the kernel this interface is misleading. Also the
only use of GBeanName in the kernel is within the registry code.
This means that the rest of the framework assumes ObjectNames, and
this change will make that code confusing. Finally, we have not
addressed ObjectName queries, which are a required component of the
framework and are used through the code base. This should be an all
or nothing change.
-dain
