Thank you for the responses. Here is the packaging details: for the EJB3 deployment: panel-server.ejb3: class files for both client & server META-INF/persistence.xml META-INF/jboss.xml (security domain declaration) for the portlet deployment: panel-email.war: WEB-INF/classes (portlet related classes) WEB-INF/lib/panel-client.jar (client jar for session & interfaces) WEB-INF/email-object.xml WEB-INF/portlet-instances.xml WEB-INF/portlet.xml WEB-INF/web.xml unibrew: you indicated that I should not have client classes in both places, but my past experience (regular webapps, not portlets) is that to hot-deploy and not affect multiple applications I need to have them in both places and have call-by-value & such configured (which I believe I do). I am able to do this with my regular test war file. My goal is to have appropriate packaging to allow updates to the EJB3 application without needed to redeploy all the portlets & other applications (jbpm will be in the mix also). Thank you for the help, gary. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961102#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...