RE: [JBoss-dev] jboss-head status
- First Post
- Replies
- Stats
-
Go to
- ----- 2026 -----
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2007 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2006 -----
- December
- November
- October
- September
- August
- July
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(a)lists.jboss.org
[mailto:jboss-development-
bounces(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
If we want backward compatibility, then one should be able to manage a
service via only MBeanServer.registerMBean/MBeanServer.unregisterMBean
without the current exception stack trace. Yes, its only a debug
message, but I don't need the stack to yell at me further.
Otherwise, cleanup the mbean management and make the ServiceController
the only entry point for all mbean service registration/lifecycle.
Jason T. Greene wrote:
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
7169
days inactive
7168
days old
jboss-development@lists.jboss.org
1 comments
2 participants
tags (0)
participants (2)
-
Jason T. Greene -
Scott M Stark