That might work. Basically, if you create an EJB3, then the JAR file should contain the local and remote interface classes and the implementation class. The remote interface class needs to be included in the client's classpath - for a simple test it is usually easier to just include it in the client's JAR file. To summarize: somejb.jar: org.xxx.yyy.EjbRemote.class org.xxx.yyy.EjbLocal.class org.xxx.yyy.EjbImpl.class client.jar: org.xxx.yyy.EjbRemote.class org.xxx.yyy.Client.class In Ant, when building the client you can use the 'includes' directive of a fileset to grab **/*Remote.class from the EJB build directory. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245000#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...