[jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-1832) -object.xml files should be orderable

Tue Feb 19 20:03:26 EST 2008

    [ http://jira.jboss.com/jira/browse/JBPORTAL-1832?page=comments#action_12399981 ] 

Chris Laprun commented on JBPORTAL-1832:
----------------------------------------

I agree that this is problematic. I have fixed the issue with SetMap, however the problem is deeper than just a sorting issue at one deployment level... So I do agree that there could be a quick fix that would work with your object.xml structure, a more generic solution is required and not immediately obvious.

> -object.xml files should be orderable
> -------------------------------------
>
>                 Key: JBPORTAL-1832
>                 URL: http://jira.jboss.com/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
>
> -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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira