<jndi-name> should be the global jndi name of the bean,
you don't provide your deployment descriptors so I can't
tell you what it is.
Thank you for your reply. First of all, I don't know what is global JNDI, so could you tell me more about this?
In addition, the the descriptor values changed as you suggestioned, I got the error "Caugth exception: ejb not bound"
Any idea for me? Many Many thanks !!
You still haven't posted your deployment descriptors.
By default jboss binds the ejb into global jndi
at <ejb-name> unless you specify <jndi-name> in jboss.xml
Assuming your ejb has just
You woud write
For more info look at
The <ejb-ref> element defines a reference from one bean to another. So in the xml you wrote your telling jboss the your session bean needs a reference to another session bean.
To fix the problem, I suggest you remove the whole <ejb-ref> thing. Your webclient doesn't need it also. Remove all the <ejb-ref>s from your xmls.
The lookup call you should use in your client should be the <ejb-name> of your bean. For example, if you typed your ejb-name like this:
then you should have a lookup call like this:
The Home object is an RMI-IIOP objects and so the must be cast into RMI-IIOP objects using a special RMI-OOP cast. In short, usign PortableRemoteObject.narrow(...) is the proper way of casting a remote object.
Thank you very much for your support. Now I could deploy ejb to my jBoss. However, I tried session bean only and believe will hit more problem on ejb deployment on the coming futher. This forum must be the way for me to find the answer.