12:47 p.m.
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
12:54 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-4339) add JMX lookup component
[
https://jira.jboss.org/jira/browse/JBSEAM-4339?page=com.atlassian.jira.pl...
]
Samuel Mendenhall updated JBSEAM-4339:
--------------------------------------
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
6:34 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4339) add JMX lookup component
[
https://jira.jboss.org/jira/browse/JBSEAM-4339?page=com.atlassian.jira.pl...
]
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
6:14 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4339) add JMX lookup component
[
https://jira.jboss.org/jira/browse/JBSEAM-4339?page=com.atlassian.jira.pl...
]
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
1:56 p.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-4339) add JMX lookup component
[
https://jira.jboss.org/jira/browse/JBSEAM-4339?page=com.atlassian.jira.pl...
]
Norman Richards updated JBSEAM-4339:
------------------------------------
any further JMX work will be Seam 3
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
1:56 p.m.
New subject: [JBoss JIRA] Assigned: (JBSEAM-4339) add JMX lookup component
[
https://jira.jboss.org/jira/browse/JBSEAM-4339?page=com.atlassian.jira.pl...
]
Norman Richards reassigned JBSEAM-4339:
---------------------------------------
Assignee: Norman Richards
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
Assignee: 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
4:07 p.m.
New subject: [JBoss JIRA] Closed: (JBSEAM-4339) add JMX lookup component
[
https://jira.jboss.org/jira/browse/JBSEAM-4339?page=com.atlassian.jira.pl...
]
Norman Richards closed JBSEAM-4339.
-----------------------------------
Resolution: Done
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
Assignee: 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
5483
days inactive
5618
days old
6 comments
3 participants
participants (3)
-
Dilip Ramji (JIRA) -
Norman Richards (JIRA)
-
Samuel Mendenhall (JIRA)