This content has been marked as final. Show 1 reply
I'm no expert but these are my initial thoughts:
1) For common class loaders across multiple EAR's use a jboss-app.xml file for each ear with the same loader repository name. This will allow all of your EAR's to load the model entity beans.
<!DOCTYPE jboss-app PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd"> <jboss-app> <loader-repository> sales.millwood.uk.com:loader=sales </loader-repository> <!-- <module> <service>dvd.beans</service> </module> --> </jboss-app> 2) For multiple parts of a "portal" page, where you can load/unload (deploy/undeploy) parts of the page, you can do this very easily in jboss portal (using a web user interface for managing what is displayed on the portal pages (once the portal is deployed). Unfortuneatly until Seam 1 one of the most important features of Seam (the Conversation context) will not be available in JSR 168 portals. But this is being resolved currently so if you start development now, then it will become available during your project development lifecycle. Another thought is whether you can deploy/redeploy wars and ejb3 jar within an ear, without causing all the other modules to be reinitialised. Hope this helps, James