David Jencks wrote:
> Did you look at how ServiceCreator does it? That might work for you also.
> Basically you ask the mbeanserver to create your object (sub-service) for
> you using a specific classloader, then it remembers for you, you don't need
> to worry about the mbeanRegistry.
>
I want
Did you look at how ServiceCreator does it? That might work for you also.
Basically you ask the mbeanserver to create your object (sub-service) for
you using a specific classloader, then it remembers for you, you don't need
to worry about the mbeanRegistry.
(all of this "as I recall")
david jenc
Hi Adrian,
arghh, I think I am doing registration terribly wrong.
There is sth which I didn't tell you, because I didn't
think it was of any relevance.
The MBeans involved are my own JMSProvider. The
"root"-service is:
fs4p.eartest:service=MS4PServer
This one provides a non-null result when I
Ok, this is what I found out so far:
In my "root"-service I implement MBeanRegistration to obtain
the jmxserver to register further sub-services to.
This implements MBeanServer.
This is where I register my MBeans calling registerMBean(..).
But the class I queried the "org.jboss.mx.classloader"
>From: Michael Bartmann <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: Re: [JBoss-user] JMX and ear-scope
>Date: Thu, 12 Sep 2002 15:03:15 +0200
>
>Hi Adrian,
>
>Your workaround sounds ok, but I have some 20 ear-scoped applicat
Hi Adrian,
Your workaround sounds ok, but I have some 20 ear-scoped applications, with
the same single offending method in each, so I decided to stay with my
serialization
"below the API" with a byte[] arg. (I can do this by myself, but the
management
GUI is written by Mehrdad (remember him?),
ian
>From: Michael Bartmann <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: [JBoss-user] JMX and ear-scope
>Date: Tue, 10 Sep 2002 18:59:07 +0200
>
>Suppose I have two classes ClassA (an MBean) and ClassB (implements
>Serializable)
Suppose I have two classes ClassA (an MBean) and ClassB (implements
Serializable).
Both classes live inside an ear-scope.
There is an instance of ClassA which is registered with the JMX-server.
ClassA has a method "void m(ClassB b)".
This method m is called through an RMIAdaptor from an other JVM
