I finally got it to work. It was nothing to do wit JNDI name or jboss.xml. In fact jboss.xml is not required. The ejb-name in ejb-jar.xml is enough to be referenced by a client. The problem was that the ear wasnt deployed at all. There was some problem with the soure code in remote interface. The method signature did not throw RemoteException. But the surprising thing was jBoss did not complain when I deployed it. It did not throw any errors or messages or exception. This is what misled me into going to debug somewhere else. I would have expected JBOSS to throw some message to the least saying the ear was not deployed.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834015#3834015 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834015 ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
