I've reconsidered this:
+1 on canonical name as internal string representation
+1 on attempting to preserve whatever string is used to construct the
gbean name
+1 on restricting characters in gbean name and assuring that gbean name
>> object name conversion always works in a non-surprising manner.
How hard would it be to get the GBeanName to do this?
Regards,
Alan
Dain Sundstrom wrote, On 7/11/2005 10:49 AM:
Before we release M4 we need to resolve the standing veto against
geronimo/trunk/modules/kernel/src/java/org/apache/geronimo/gbean/
GBeanName.java
Note the +1s below are actually -1s the removal of said feature from
javax.management.ObjectName, which this class replaced.
-dain
Begin forwarded message:
From: "Alan D. Cabrera" <[EMAIL PROTECTED]>
Date: February 23, 2005 11:56:20 AM PST
To: [email protected]
Subject: Re: GBeanName [was: svn commit: r154723...]
Reply-To: [email protected]
+1
Dain Sundstrom wrote:
For the record;
+1 on canonical name as internal string representation
-1 on attempting to preserve whatever string is used to construct
the gbean name
+1 on restricting characters in gbean name and assuring that gbean
name >> object name conversion always works in a non-surprising
manner.
