Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <41A4F500.3030209@gluecode.com>
References: <26906998-3E48-11D9-B78A-000D93C5B79C@gluecode.com>
 <41A4D82D.1060205@gluecode.com>
 <33B7B138-3E4B-11D9-B78A-000D93C5B79C@gluecode.com>
 <41A4F500.3030209@gluecode.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F8118DCA-3E60-11D9-B78A-000D93C5B79C@gluecode.com>
Content-Transfer-Encoding: 7bit
From: Dain Sundstrom <dsundstrom@gluecode.com>
Subject: Re: GBeans, Kernel and JMX Exceptions
Date: Wed, 24 Nov 2004 13:36:58 -0800
To: dev@geronimo.apache.org

On Nov 24, 2004, at 12:54 PM, Jeremy Boynes wrote:

> Dain Sundstrom wrote:
>> When you going to make that change?  I'm working on the GBean code 
>> right now, but will be offline Thursday until Sunday Morning.
>
> I've been waiting to see if there is any more input given this is not 
> critical and it does change the API. As I said, I plan to get to it 
> this week. Are you going to finish up your changes before you 
> disappear?

I hope so :)  I'm getting close....

>> Also, I'm a bit curious about the GBeanName interface?  For example, 
>> I assume we are keeping the concept of pattern matching, but are we 
>> keeping the concept that a name contains name/value pairs.  I know 
>> there is some J2EE deployment code manipulate the name/value pairs to 
>> build new object names.
>
> Of course - there is a lot of other stuff that relies on this.

cool

-dain