View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820273#3820273
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820273 I tried to deploy titan.jar for ex12_1 and I encountered the exception: "CustomerEJB has no local home interface" . I read through the forum and found that other people also encountered the same problem for other exercises. Actually CustomerEJB does not have any local home interface nor local interface. Nothing about local (home) interface is described in ejb-jar.xml, too. Why will jboss try to find a local home interface for it? One thing in common for all those exercises with this deployment problem is that, EJB with only remote interface tries to access EJB with only local interface. I suspect this is the cause of the problem. So I remove the AddressEJB which has only local interface (of course, CustomerEJB will change some code) and redeploy again. This time no error!!! Then I tried to use session bean to access entity beans which has only local interface, there is also no problem. So the conclusion I made is that, in a jar, if both entity beans with only remote interface and entity beans with only local interface are used together, jboss will have problems in deploying this jar. Any other suggestion? ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
