Answers inline

"xavieruk" wrote:
Hello All

 <mbean code="playground.org.ms.mbeans.ConfigService"
 name=":service=ConfigService,name=ConfigService">
 <attribute name="JndiName">ConfigService</attribute>
 </mbean>

My Question(s):
1. After successful deployment, I'm unable to see this MBean bound to JNDI NamingService. I didn't find the ConfigService in JNDIView. Is there anything I've to do to reflect this service into JNDI NS? I don't want to use NonSerializableFactory methods to do this. Am I assuming that deploying the MBean with the above configuration will bind to JNDI? If yes, what is the way I can do this?

"xavieruk" wrote:

2. If I know the JNDI Name, Is it right to lookup for this Bean as follows(JRun didn't have any problem for this kind of lookup and getter):

Context ctx = ...
Object obj = ctx.lookup("ConfigService");
Object mbean = PortableRemoteObject.narrow(obj,ConfiService.class)
// now I got the bean, I call the methods on this?
Configuration conf = mbean.getConfigForTestServer();

"xavieruk" wrote:

3. I understand I can use RMIAdaptor to invoke the methods on the MBean. The only disadvantage in this way is the client should import jboss class(RMIAdaptor) which is not an ideal way. So I'm tending to go the alternative suggested above.

As far the rmiadapter thing, did you check out the link that i had given above.?

Assume that i need to invoke the flushCache method on
jboss.j2ee:jndiName=com.yoyo.AddressJNDI,service=EJB

i would create a urlconnection to the following URL
http://localhost:8080/jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.j2ee:jndiName=com.yoyo.AddressJNDI,service=EJB&methodName=flushCache

where ur objectname would go in the name request and methodName would be the name that you want to call.

You have to bind it yourself. In your MBean you need something like:

String jndiName;

public void setJndiName(String name){
 InitialContext ctx = new InitialContext();
 this.jndiName=name;
 ctx.bind(name, this);
}

public String getJndiName(){
 return jndiName;
}

the jndiname in my objectname is just how jboss creates the objectname. Its an EJB and i dont really set any object for that. So having an jndiName or not in the objectname should make no difference.
Are you sure you included the domain(jboss.j2ee) as well as the name included in the HTTP URL?

Can you make your bean implement Serializable?

Also, some info here:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=49048&postdays=0&postorder=asc&start=10

Unless something has changed recently, MBeans are *NOT* remote objects.

You can either
a) use RMIAdaptor to access things via the MBean server (which you would like to avoid)

b) Use HTML adaptor (not a good choice IMHO)

c) Bind an RMI stub for your service to the JNDI tree

My company does "c" (but in a clustered/load balanced way, so you'd need to adjust if you don't do clusters)

example

 HARMIServerImpl server = new HARMIServerImpl(
 haPartition, //your HA partition handle
 "ReplicantName", // unique name for your service, call it anything
 ServiceInterface.class, //exposed interface clients use
 serviceInstance, // actual MBean instance you want to access
 0, // RMI port, zero for automatic
 null, //
 null, //
 null, //
 callBackHandler //handler to be notified when other cluster members come/go
);
new InitialContext().bind("MyService",server.createHAStub(new RoundRobin()));