I think you will have trouble with RMI code mobility. I certainly did when
trying to make MBean services JINI aware.
I couldn't get the JBoss class server to work - it looks broken to me on a very
cursory examination. Without this (custom classloader annotations) you are
stuck with setting the
Or you could copy the file over if you have the server's deploy directory
mapped to your machine via Samba or NFS or something...
Or use FTP or HTML to upload the file, using the commons net library from
apache...
I do this sort of thing with Ant all the time (using a deploy target in an Ant
Sorry that this is such a late response...
I was actually trying to use the injection mechanism for MBeanServer,
ObjectName etc - foo and bar are just for illustration ;)
But I couldn't get ...injection id=MBeanServer setMethod=setMBeanServer...
accepted by the XML validation phase of
I can't seem to deploy a service with an XMBean descriptor containing
| descriptors
|
| ...
|
| injection id=foo setMethod=bar /
|
| /descriptors
|
The 1.2 version of the dtd seems to require id and setMethod subelements, but
doesn't define them. Is the DTD broken, or
It may be obvious but if you can, write a little code that iterates over the
naming enumeration of your initial context, and print out what content it has,
if any. This might give you a better idea of which naming service you are
actaully connected to.
You could compare this with the JNDIView
I'm playing around with different approaches to dealing with isolated EARs, and
I get this error when:
a) I've scoped the classloader for the EAR:
jboss-app
loader-repository
Cyrus.classloading:loader=application registry
loader-repository-config
Marcel,
I've added a note in the JMX FAQ on the wiki. I've included the code for the
classes I had to create, and some explanation of why I needed them - in case
anyone can come up with a better solution.
Let me know if the instructions etc. are OK or fall short in any way and I'll
fix the
I don't think there is a general J2EE solution because you can't change the ENC
once the MDB is deployed - so it has to remain listening to the same queue and
you can't change the env-entry values.
You could use setters/getters on your EJBs, but you would lose these changes
whenever you get a
I have successfully added a remote notification listener using the RMIAdaptor,
but I had to do a bit of work first - there must be a better way! But in case
anyone wants to know how I did it:
you need a remote version of the non-remote NotificationListener interface -
there is one in JBoss 4:
Thanks for the reply, Dimitris.
I think that MBeanServerConnection is just another interface for the
RMIAdaptor. My problem is that the RMIAdaptor needs a serializable
NotificationListener when you call addNotificationListener - I think this will
be the case whether you call this through a
Well, I tried adding a notification listener using the RMIAdaptor, and it
definitely adds the listener to the local JBoss MBeanServer - I got printouts
on the server console, not my local console, with a simple test listener.
This is pretty much what I expected, given that it insisted that the
I used to use code like this in 3.2.3:
RMIAdaptor adaptor = ic.lookup(jmx/rmi/RMIAdaptor);
MBeanServer server = new RMIConnectorImpl(adaptor);
I need to add a NotificationListener to an MBeanServer - if I use the adaptor
it requires a serializable listener - presumably I would have to create a
12 matches
Mail list logo
