[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4339) add JMX lookup component

[Dilip Ramji (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBSEAM-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12490435#action_12490435 ] 

Dilip Ramji commented on JBSEAM-4339:
-------------------------------------

Will this intercept MBean invocations and wrap them in a Seam context, or do these MBeans have to be invoked explicitly from within a Seam context? Our legacy app has a "jboss-service.xml" file with lots of MBeans and scheduled invocations set up. I was using the Seam timer feature to simulate invocation of these beans on startup in "components.xml" using the MBeans as components. Trouble is, though, that randomly some of the invocations on these components had null values injected into the dependencies so NPEs would be thrown. Also, this method does not solve the problem that these are MBeans and need to be treated as such. I'm hoping with the MBeanProxy, I'd be able to keep the service definitions as they are, and simply be able to have Seam intercept the invocations and wrap them in a context. 

> add JMX lookup component
> ------------------------
>
>                 Key: JBSEAM-4339
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4339
>             Project: Seam
>          Issue Type: Feature Request
>            Reporter: Norman Richards
>            Priority: Minor
>             Fix For: 2.2.1.CR1
>
>
> There have been several requests for components that do JMX lookups.   While it's easy enough to create components that perform a lookup, we can probably save people time with a Seam component for this, most likely using the JBoss MBeanProxy to provide the Java interface for this.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira