Hello, I did a Wiki about a way to do that. see : http://wiki.jboss.org/auth/wiki/PortletandPageDeploymentOrder
the way I do it is to package the parts of the portal (main default portal, portal x, portal y, ...) in different Sar (or War) with all their code things related to it. This is a convenient architecture to both develop and deploy parts of the whole portal(s) independently. you can look at the way Sar are used for the portal itself, to organise your code and portal artifacts. by the way : I thaught of including files... but that is not really nice, is it ? using the packaging of JBoss, and architecture of the developed code looks better to me. This also allow to have your own JXM services, EJB, etc... being deployed in the proper order. If a portlet needs a JXM service (configuration ?) in it's initialization phase... it must be deployed before the portlet... etc... It is also more clean for production side of the portal management. Antoine View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166091#4166091 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166091 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
