[
https://issues.apache.org/jira/browse/JS2-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randy Watler reassigned JS2-876:
--------------------------------
Assignee: Randy Watler
> 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: Randy Watler
> Fix For: 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
