(bump)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4201169#4201169
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4201169
___
jboss-user mailing list
jboss-user@lists.jboss.org
Yes there is - Spring to the rescue! Here is an example:
In you MBean, decorate your method with annotations like this:
| @ManagedOperation(description = Create a job)
| @ManagedOperationParameters({
| @ManagedOperationParameter(name = accountName, description = The
name
Still haven't found a solution to this - any love here?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4197174#4197174
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4197174
___
Jboss 4.2.2
On the client? This exception is happening on the server, NOT on the client.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4195100#4195100
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4195100
TO CLARIFY:
the exception
javax.naming.NoInitialContextException: Cannot instantiate class:
org.jnp.interfaces.NamingContextFactory [Root exception is
java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
is occurring on the server, not on the client. I can watch it
Gurus,
here is my situation:
I have a JMX bean deployed via Spring's MBeanExporter. Several of the methods
new up an InitialContext() for various operations.
This works just fine when I invoke the methods via the JBoss JMX console. But
if I try to invoke them through JConsole or
