Improving bean shell script / JMX integration

[genman]

http://jira.jboss.com/jira/browse/JBAS-2862

I was wondering if anybody had any thoughts or concerns. I rather like the idea of being able to do this:

<server>
 <mbean name="example:service=Test">
 <depends> ...
 <code language="bsh">
String name = "joe";
void invoke() {
 System.out.println("invoke " + name);
}
 </code>
 </mbean>

And you get the MBean attribute "name" and operation "invoke" for free.

I've also been working on this: http://jira.jboss.com/jira/browse/JBAS-2855 by the way.

[dimitris]

I've experimented a bit with supporting multiple scripting languages in an mbean (using BSF) here http://wiki.jboss.org/wiki/Wiki.jsp?page=ScriptingListener

If I remember, a problem is to find out, in a portable way, what are the implemented methods/attributes in a script.

[genman]

I guess that'd be mostly a problem with the framework you're using.

If you're using BeanShell, you can get the declared variables and methods fairly easily by calling Interpreter.getNamespace.

[starksm64]

"genman" wrote:
http://jira.jboss.com/jira/browse/JBAS-2862

I was wondering if anybody had any thoughts or concerns. I rather like the idea of being able to do this:

Yes, this is mixing the SARDeployer and BeanShell deployer in the same descriptor and is a mess. Such a change should be done as an extension to the SARDeployer deployer.