Couldn't we just pretend that a target MBean implemented some interface,
then use the dynamic proxy api to generate something that would map the
estetically clean method calls into MBeanServer.invoke() calls? The target
bean could implement that inteface, but we don't really care if it does...
on
> > Ummm urrrk I have a big problem with assuming
> there
> > is only one registered object of each class. If
> you
> > return a collection of all registered objects of a
> > requested class this is ok with me, although I
> don't
> > see yet how useful it is.
>
> This is clearly for "singleton"
> This makes alot of sence... almost so that I wonder
> why the JMX folks did
> not make it this way from the start... perhaps the
> JINI guys wanted all the
> glory.
Jason, I really like the "ra-ra-ra-ism" of your attitude, that being said, the JMX
folks didn't do it this way for a good reason
> Ummm urrrk I have a big problem with assuming there
> is only one registered object of each class. If you
> return a collection of all registered objects of a
> requested class this is ok with me, although I don't
> see yet how useful it is.
This is clearly for "singleton" programming,
> Ar
Ummm urrrk I have a big problem with assuming there is only one registered object of
each class. If you return a collection of all registered objects of a requested class
this is ok with me, although I don't see yet how useful it is. Are you keeping track
of inheritance or returning objects o
JBoss daily test results
SUMMARY
Number of tests run: 216
Successful tests: 202
Errors:11
Failures: 3
[time of test: 26 December 2001 5:43 GMT]
[java.version: 1
This makes alot of sence... almost so that I wonder why the JMX folks did
not make it this way from the start... perhaps the JINI guys wanted all the
glory.
How do you map the classname to the ObjectName?
Does this mean that the references returned are of the type requested, thus
the ugly MBeanS
from the depth of the deployers,
I am actually thinking of something slightly different that might help you guys. I
use the new org.jboss.system.Registry to lookup native MBean interfaces in the server,
it an intuitive way to hook up components in the run-time. Right now I lookup by
ObjectNa
JBoss daily test results
SUMMARY
Number of tests run: 216
Successful tests: 202
Errors:11
Failures: 3
[time of test: 26 December 2001 4:45 GMT]
[java.version: 1
JBoss daily test results
SUMMARY
Number of tests run: 216
Successful tests: 202
Errors:11
Failures: 3
[time of test: 26 December 2001 3:35 GMT]
[java.version: 1
JBoss daily test results
SUMMARY
Number of tests run: 220
Successful tests: 202
Errors:15
Failures: 3
[time of test: 26 December 2001 2:49 GMT]
[java.version: 1
User: d_jencks
Date: 01/12/25 07:35:18
Modified:src/main/org/jboss/resource/adapter/jdbc/xa
XAManagedConnectionFactory.java
Log:
Made matchManagedConnection work even if user is null. (May happen if user and
password are specified in URL)
Revision Chan
User: d_jencks
Date: 01/12/25 07:35:17
Modified:src/main/org/jboss/resource/adapter/jdbc/local
JDBCManagedConnectionFactory.java
Log:
Made matchManagedConnection work even if user is null. (May happen if user and
password are specified in URL)
Revision
13 matches
Mail list logo
