[
https://jira.jboss.org/jira/browse/JBPORTAL-1832?page=com.atlassian.jira....
]
Antoine Herzog commented on JBPORTAL-1832:
------------------------------------------
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.
Antoine
-object.xml files should be orderable
-------------------------------------
Key: JBPORTAL-1832
URL:
https://jira.jboss.org/jira/browse/JBPORTAL-1832
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.6.2 Final
Reporter: Sylvain FRANCOIS
Attachments: awaysubone-object.xml, awaysubtwo-object.xml, helloworld-object.xml,
homesubone-object.xml, homesubtwo-object.xml
-object.xml files are loaded without any order rule. This makes mangement of portal/page
definitions very difficult with "overwrite" mode since you can't assume if
parent has already been loaded or not.
It should be easy to fix this (I've made a temporary patch) : descriptors URL are
already sorted before parsing, but their parsing results are put in a non-sorted Map (cf.
org.jboss.portal.server.deployment.jboss.PortalDeploymentInfoContext).
PS : my -object.xml files follow this structure (all with 'overwrite' mode) :
portal-object.xml
toppage-x-object.xml (with all its subpages)
toppage-y-object.xml (with all its subpages)
toppage-z-object.xml (with all its subpages)
...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira