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

[Norman Richards (JIRA)]

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

Norman Richards commented on JBSEAM-4339:
-----------------------------------------

Ok, at your prompting, I've added the following to Seam_2_2 as a first pass.  I've ported the JBoss MBeanProxy to Seam.  So, you can register a seam-managed mbean proxy:

    <jmx:mbean object-name="jboss:service=JNDIView" proxy-class="MyView" name="jndi" />

Where proxy-class is a standard JBoss typed mbean proxy interface.  For example: 

public interface MyView {
    public String listXML();
}

#{jndi.listXML()} would dump the jndiview XML into your page, for example.  

I guess for only EL access, we shouldn't be forced to create typed proxy interfaces, but I would guess @In usage would be the more normal usage, in which case the proxy interface is critical.

There's still plenty of time to give feedback on this. 

> 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