geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <da...@coredevelopers.net>
Subject Re: How to gbean-ify a geronimo mbean that unregisters itself?
Date Mon, 19 Jan 2004 21:19:33 GMT

On Monday, January 19, 2004, at 11:11 AM, Alan D. Cabrera wrote:

> Dain, Jeremy and I talked about this.  The configuration information
> that the bean needs should be passed in during construction.  The
> doStart method should read this configuration and make the appropriate
> calls to the underlying policy context.  The doStop method should 
> delete
> the context.
>
> The delete method for the bean should be removed.  Would you like to do
> this or shall I?

I will, then could you review?  I started gbean-izing this morning.

david
>
>
> Regards,
> Alan
>
>> -----Original Message-----
>> From: Dain Sundstrom [mailto:dain@coredevelopers.net]
>> Sent: Monday, January 19, 2004 10:19 AM
>> To: geronimo-dev@incubator.apache.org
>> Subject: Re: How to gbean-ify a geronimo mbean that unregisters
> itself?
>>
>> On Jan 19, 2004, at 2:03 AM, David Jencks wrote:
>>
>>> I see that the security systems AbstractModuleConfiguration has a
>>> method "delete" that unregisters itself from the mbean server.
>>>
>>> It's not clear to me yet how to implement this in the gbean
> framework,
>>> or if we should simply find a different way to get the same effect.
>>
>> This level of control is generally not a good idea for a component.
> If
>> you simply unregister a component without following the life cycle
>> model, you will cause any dependent component to fail.
>>
>> I think we should start with these questions:
>>
>> What is this used for? Why do we need this?  Will stop work instead?
>>
>> -dain
>


Mime
View raw message