But even under JSE it's trivial to publish an MBean in a few lines of Java code as well:
Well, that's my whole point in this exercise. We shouldn't require people to introduce this code (albeit trivial) in their app just so it can be monitored (after all, how many app developers actually take it upon themselves to write code whose sole purpose is monitoring?). And once you put it in, you probably will want additional code to introduce a way to disable it if you need to - see Emmanuel's point about security. It should be configurable directly from the framework itself.
Let's instead burn some calories in Hibernate 3.3 getting natural ID key caching working properly, okay? :-)
I've already burned the calories myself (it is working with the patch I attached to the JIRA). And since I don't work on other parts of Hibernate, I'm not diverting resources from it. But, if this work isn't deemed contributable or highly useful, let me know and I'll stop working on it.
_______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
