I disagree. Why would you want to do that? When you have a production issue and you need to look inside the server to see what is going on you cannot restart the process to enable JMX... I really think it should be on by default.
Sent from my iPhone > On 2014/03/31, at 8:39, Gary Gregory <[email protected]> wrote: > > JMX shoud be off by default IMO? Is there a recommendation or a known pattern > in this area? > > Gary > > >> On Sun, Mar 30, 2014 at 2:11 PM, Ralph Goers <[email protected]> >> wrote: >> What JaveEE APIs? JMX was moved to Java SE in 1.5 and 1.6. >> >> I’m not sure I like the mbeans registering automatically but oh well. >> >> Ralph >> >>> On Mar 30, 2014, at 10:52 AM, Matt Sicker <[email protected]> wrote: >>> >>> Since JMS depends on Java EE APIs, it would make sense to place them in >>> their own packages similar to how the db code is handled. I know they work >>> fine as is, but it makes it easier to segregate optional dependencies. This >>> would be useful for OSGi so that we can use the full set of metadata >>> available without requiring all the optional dependencies in the >>> Import-Package attribute. >>> >>> -- >>> Matt Sicker <[email protected]> > > > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > JUnit in Action, Second Edition > Spring Batch in Action > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory
