orielly ejb3 book, @RemoteBinding problem

[Ash More']

hi,
i am currently practising examples from orielly ejb3 book,
in the 4th chapter(i.e chapter 24 of workbook), i am running the example as given in the book,

The session bean is as follows:

@Stateless
@org.jboss.annotation.ejb.RemoteBinding 
(jndiBinding="TravelAgentRemote")
public class TravelAgentBean implements TravelAgentRemote{
 @PersistenceContext(unitName="titan")
private EntityManager manager;
 
    public void createCabin(Cabin cabin) {
...........

The client is as follows:

public class Client {
    public static void main(String [] args) {
        try {
            Context jndiContext = getInitialContext( );
            Object ref = jndiContext.lookup("TravelAgentRemote");
            TravelAgentRemote dao = (TravelAgentRemote)
                PortableRemoteObject.narrow(ref,TravelAgentRemote.class);
 
            Cabin cabin_1 = new Cabin( );
            ....
            ....

However i get the following errors:

javax.naming.NameNotFoundException: TravelAgentRemote not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
at sun.reflect.GeneratedMethodAccessor84.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(Unknown Source)
at com.titan.clients.Client.main(Client.java:16)

however when i try the following in client code it works:

public class Client {
    public static void main(String [] args) {
        try {
            Context jndiContext = getInitialContext( );
            Object ref = jndiContext.lookup("TravelAgentBean/remote");
            TravelAgentRemote dao = (TravelAgentRemote)
                PortableRemoteObject.narrow(ref,TravelAgentRemote.class);
 
            Cabin cabin_1 = new Cabin( );
            .....

why is @org.jboss.annotation.ejb.RemoteBinding
(jndiBinding="TravelAgentRemote") not working

[Jaikiran Pai]

Which version of JBoss and Java do you use? Are you sure the application (containing the EJB) has deployed successfully without any errors? Also, use the JNDIView to check whether your bean is actually bound to "TravelAgentRemote".

[Ash More']

hi,
i am using jboss 4.2.0 GA , java 1.6
i am trying the examples as is from the workbook(currently on chapter 4, workbook chapter 24)

well 24.1 and 24.3 both work
24.1 using jndiContext.lookup("TravelAgentBean/remote");

24.3 using jboss.xml as

<jboss>
   <enterprise-beans>
      <session>
         <ejb-name>TravelAgentBean</ejb-name>
         <jndi-name>TravelAgentRemote</jndi-name>
      </session>
   </enterprise-beans>
</jboss>

however 24.2 i.e using @org.jboss.annotation.ejb.RemoteBinding(jndiBinding="TravelAgentRemote")does not work

the JNDIView does not have TravelAgentRemote named bean.

is there anything else required to be configured along with @RemoteBinding annotation ??

[Ash More']

Problem solved.
Solution: Do not keep duplicate copies of session bean having @RemoteBinding in C:\JBoss\jboss-4.2.0.GA\server\default\deploy directory. I had used the same named (TravelAgentBean) session bean in two different applications and had deployed both the applications in C:\JBoss\jboss-4.2.0.GA\server\default\deploy directory. This created problems with @RemoteBinding.
[ May 15, 2008: Message edited by: Ash More' ]