[JBoss-dev] jboss-head status

[Jason T. Greene]

The only reason I can see not to, is to offer behavioral backwards
compatibility. Although this is a major release, and adapting to this
kind of change would be simple. Alternatively, ServiceController could
accept beans that are already registered, and just trigger a loud
warning message.

-Jason

> -----Original Message-----
> From: jboss-development-bounces at lists.jboss.org
[mailto:jboss-development-
> bounces at lists.jboss.org] On Behalf Of Scott M Stark
> Sent: Thursday, August 24, 2006 4:52 PM
> To: JBoss.org development list
> Subject: Re: [JBoss-dev] jboss-head status
> 
> Yes, this is the current issue I see. My main question at this point
is
> why should we have the separate
> MBeanServer.registerMBean/unregisterMBean +
> ServiceControler.lifecycle/remove. It clearly leads to duplicate state
> management. Why not say the only way to manage an mbean service is
> through the ServiceController drop all of the
> MBeanServer.registerMBean/unregisterMBean usage?
> 
> Jason T. Greene wrote:
> > Not sure if this is related, but take a look at [1]. The original
> > ServiceController unregisters on remove.
> >
> > [1]
> >
http://lists.jboss.org/pipermail/jboss-development/2006-August/000776.ht
> > ml
> >
> > -Jason
> >
> >
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development