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