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".
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
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 ??
Joined: Apr 20, 2008
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' ]
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: orielly ejb3 book, @RemoteBinding problem