RE: [JBoss-dev]InstanceAlreadyExistsExceptionafterundeployandrepeated deployin JBoss AS 5.0.0 Beta
Right, so why don't we complain if they don't clean up after themselves,
and then clean up for them? Just like Mom does.
-----Original Message-----
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-
bounces(a)lists.jboss.org] On Behalf Of Brian Stansberry
Sent: Wednesday, August 16, 2006 11:20 AM
To: JBoss.org development list
Subject: RE: [JBoss-
dev]InstanceAlreadyExistsExceptionafterundeployandrepeated deployin
JBoss
AS 5.0.0 Beta
jboss-development-bounces(a)lists.jboss.org wrote:
> On Wed, 2006-08-16 at 15:49 +0200, Adrian Brock wrote:
>> Also, this change causes "problems" for web deployments (looks like
>> they being unregistered from the MBeanServer rather than being
>> removed from the ServiceController?):
>>
>
> Yep. And I've fixed this as well.
So, before ServiceController.remove() was cleaning up after people,
and
now the new implementation is again. And you just fixed an issue
where
it would complain if people had already cleaned up after themselves
:)
If need be my mom used to clean up after me, but she also trained me
to
clean up after myself (well, kinda). So, seems like if
EjbModule.createService() is going to call registerMBean(),
EjbModule.destroyService() should call unregisterMBean().
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
Ph: 510-396-3864
skype: bstansberry
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development