goto the jboss admin via the web browser and check the name that the bean has bean placed under in the jndi tree. if you have deployed a jar in an ear, then the name may be preceded by the ear name in jndi. so check http://localhost:8080 and view the jmx entries for you bean.
Thanks for your reply.. I have already done that, I went to the JNDI view and the bean is not there.When i checked the server log of jboss, it says ejb3 is not registered.
One more thing I noticed is that before installing EJB3, when i start the jboss it runs fine and the console doesn't show any error, but after installing jboss-EJB-3.0_RC9-FD, when i start the jboss the console shows a lot of exceptions saying mbeans are already registered.Am i doing something wrong?? I am deploying it on the default server of jboss... is it something to do with jboss installation?? Please reply.
This does look like an instalation problem. did you install jboss using the installer. If not then i think you have to look at the jboss wiki on how to migrate from ejb3 RC8 to RC9. there are some differences you need to take into acount. I think ejb 3.0 RC9 is part of the 4.0.5 the latest jboss version.
I am using 4.0.5 the latest jboss version but still facing same problem please help me out
I got it resolved. I am pasting the code over here
public class client
public static void main(String args)
Properties p = new Properties();
InitialContext ctx = new InitialContext(p);
System.out.println("Got initial COntext "+ctx.lookup("FacadeBean/remote"));
FacadeRemote lFacadeRemote = (FacadeRemote) ctx.lookup("FacadeBean/remote");
System.out.println("Got Facade Remote Bean");
The change that I have made is adding the properties instance. I have another file in my directory called jndi.properties, but I still had to put it inside my code. I am not sure why I need to do it since I already have jndi.properties.... anyways its working fine..
Thanks for the reply..