This should not happen if components are activated before the JBIContainer
is started.
And this is the case if you use a spring xml configuration file.
Anyway, i have just fixed that in the case you activate the component when
the container is already started.
Cheers,
Guillaume Nodet
On 5/22/06, William Blackburn <[EMAIL PROTECTED]> wrote:
Of course you're right, I just double checked my work and I DO get
the events, that fact was hidden from me in my listener (which is
just test code at this point) because I was doing:
ComponentMBeanImpl impl = event.getComponent();
ObjectName base = impl.getMBeanName();
and I was only logging a message if 'base' was not null - but it does
appear to be null for my 'hot-deployed' components and non-null for
the rest - can this be right? Or am I still doing something odd.
Thanks,
BJ
On May 22, 2006, at 10:59 AM, Guillaume Nodet wrote:
> You should receive start / stop events for all components, but
> install /
> uninstall will not be broadcasted for lightweight components as
> they are not
> installed / uninstall ;)
> These events will be sent when the service unit is started / stopped.
>
> Cheers,
> Guillaume Nodet
>
> On 5/20/06, William Blackburn <[EMAIL PROTECTED]> wrote:
>>
>> I have a component listener implemented that retrieves some custom
>> application configuration from components as they are started via an
>> extension mbean. Because componentevent provides access to the
>> mbeanimpl, which gives me the extension mbean name, its really great,
>> because I can easily lookup my extension mbean and invoke my methods
>> -- sadly, I just discovered that the componentlistener does not
>> appear to receive events for servicemix components deployed against
>> the lwcontainer. Is there an alternative approach to accomplish the
>> same thing? I thought about just having the components fire off a
>> messageexchange containing the extra data as they start, but I was
>> hoping to tap into the management interfaces instead.
>>
>> Thanks,
>>
>> BJ
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
--
Cheers,
Guillaume Nodet
