Ok, with JBoss 3.2.xyou should not be editing the classpath of the server to include the interfaces to your beans.
In the past I have deployed session beans in one jar that use session beans in another jar without problems (I haven't tried using entities in another jar but I am assuming that the behaviour is the same). Alternatively you could just package everything into an ear so that the different components can be deployed together. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3843086#3843086 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3843086 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
