Mailing-List: contact jetspeed-dev-help@portals.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jetspeed Developers List" <jetspeed-dev@portals.apache.org>
Date: Tue, 8 Mar 2011 02:09:59 +0000 (UTC)
From: "Ate Douma (JIRA)" <jetspeed-dev@portals.apache.org>
To: jetspeed-dev@portals.apache.org
Message-ID: 
 <506859771.3442.1299550199589.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Resolved: (JS2-876) Allow reuse of PorletWindow and
 PortletEntity accross multiple PSML pages, also when using DBPageManager
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JS2-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ate Douma resolved JS2-876.
---------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.2.2)
                   2.2.1
                   2.1.4

Resolved earlier by Randy in good enough manner.

> Allow reuse of PorletWindow and PortletEntity accross multiple PSML pages, also when using DBPageManager
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JS2-876
>                 URL: https://issues.apache.org/jira/browse/JS2-876
>             Project: Jetspeed 2
>          Issue Type: Improvement
>    Affects Versions: 2.2.0
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>             Fix For: 2.1.4, 2.2.1
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> The current XML (Castor) based PSML PageManager has a nice "feature" in that a PortletWindow/EntityId only is resolved within the current loaded PSML page.
> Meaning: it is possible to reuse the same *fragment* id (which maps back to portletWindow/EntityId) across multiple pages.
> This is very useful for certain type of portlets like calendars etc. for which you want to maintain and interact with only on "singleton" entity basis.
> However, this is currently impossible to do with the Database PageManager, as there a fragment Id actually is tied uniquely to one specific page.
> As result, current XML based PSML portals which make use of this feature cannot switch to database PSML.
> To resolve this, the Fragment/PortletWindow/Entity model needs to be enhanced to support a more flexible relationship definition between them, instead of the current hardcoded 1-1-1 relationship.
> This also means that the PSML model will need to be enhanced as well, as I think we need to be able to support reusing both PortletWindows and/or Entities (independently) for multiple fragments.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org