That is mostly correct. You create the new EAR project at the same time as your EJB project. The ear does not go into your EJB project, an entirely separate project gets created for it. Try creating a new EJB project and look for the checkbox. The new EJB project wizard also also allows you to create a separate client project which is also automatically maintained with the required client interface classes. I had to add a packaging configuration to the client project properties in order to create the client jar. So unlike with the automatically updated EAR, I had to right-click on the client project and 'Run Packaging' to build the client jar. Another client project issue I ran into is the generated interfaces extend other interfaces such as javax.ejb.EJBObject. The library reference for these (J2EE 1.4 Libraries (JBoss-IDE)) is not not automatically added to the generated client project's build classpath, so I had to add it myself. I'm not sure if this is the way it is intended to work, or is just a beta issue. Considering how far the IDE team has been able to go in automating EAR generation and deployment, it's hard to believe they intend those extra steps to be required for the client JAR. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980982#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...