yep from a dependency point of view it can be in core i think (and annotations in api)
can be a separated module too but think it is not justified the issue i currently have is how to get the cdi bean from the MBean. I used BeanProvider (ignoring Qualifiers for a first version) but it is not the best way if some "destroy/release" should be done. Not sure we have this issue elsewhere What i wanted to avoid is to add a MBean specific qualifier and add another bean completely managed (to use later @Inject @DSMBean MyMBean mbean;) Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2012/11/28 Mark Struberg <[email protected]>: > yea, looks good. Not sure in which module it fits though. But certainly a > good start for a discussion. > > LieGrue, > strub > > > > > ----- Original Message ----- >> From: Romain Manni-Bucau <[email protected]> >> To: [email protected] >> Cc: >> Sent: Wednesday, November 28, 2012 8:58 PM >> Subject: MBeans extension? >> >> Hi guys, >> >> just pushed on guithub a poc to ease MBean (JMX ones) usage with CDI. >> >> Here are the sources: https://github.com/rmannibucau/cdi-mbean >> >> do you think we can/should integrate it in DS? >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >>
