portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randy Watler (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Assigned: (JS2-876) Allow reuse of PorletWindow and PortletEntity accross multiple PSML pages, also when using DBPageManager
Date Sun, 25 Oct 2009 05:44:59 GMT

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

Randy Watler reassigned JS2-876:

    Assignee: Ate Douma  (was: Randy Watler)

SVN commits 829496 in 2.2.1-SNAPSHOT and 829497 in 2.1.4-SNAPSHOT have added persistent fragment
ids to the DBPM and refined copy/merge PSML operations to preserve fragment ids on import/export
and folder moves.

As noted, the 1:1:1 relationship above can now be maintained with the DBPM as was done with
the Castor PSML PM. If there is other work involved to resolve this issue, it should be external
to the PM layers.

> 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.2.2
>   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
> 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

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message