[
https://issues.apache.org/jira/browse/PLUTO-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma resolved PLUTO-540.
-----------------------------
Resolution: Fixed
've implemented this on portal-driver side now.
No optimization done yet, but at least its now integrated with the new
container api again.
Further optimization is (for the portal-driver) not a critical requirement
right now.
> New PortletURLListenerService
> -----------------------------
>
> Key: PLUTO-540
> URL: https://issues.apache.org/jira/browse/PLUTO-540
> Project: Pluto
> Issue Type: Improvement
> Components: portal driver, portlet container
> Affects Versions: 2.0.0
> Reporter: Ate Douma
> Assignee: Ate Douma
> Fix For: 2.0.0
>
>
> Below copied (in part) from email discussion on the Pluto dev list, see also:
> http://www.nabble.com/More-required-Pluto-2.0-SPI-and-implementation-refactoring-issues-td21973310.html
> *** PortletURLGenerationListener implementation and usage
> This issue is similar to the issue with the FilterManager implementation (see
> PLUTO-539): on each PortletURL creation all portlet deployment descriptor
> defined PortletURLGenerationListener classes are recreated on the fly while
> these are expected to be stateless singleton instances anyway.
> =====
> I've replaced the old PortletURLListener with a PortletURLListenerService to
> solve this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
