[
https://jira.jboss.org/browse/GTNWSRP-72?page=com.atlassian.jira.plugin.s...
]
Chris Laprun commented on GTNWSRP-72:
-------------------------------------
Basically, WSRPPortletInvoker.checkPortletContext only works if getPortlets has been
previously called which is not always the case the first time checkPortletContext is
invoked. A quick fix would be to call getPorlets all the time in checkPortletContext but
this would be a major performance issue. As it is getPortlets is already suboptimized
since it needs to loop over the deployed portlets twice.
A proper implementation of the feature will need to listen to portlet deploy/undeploy
events by having RegistrationPolicy listen to ManagedObjectRegistryEvents so that it can
update itself when needed instead of having to examine the complete list of portlets all
the time. More generally, we need to review the design since it will be part of the
supported API and I think it still needs some work.
Update management of portlet contexts for specific registrations
----------------------------------------------------------------
Key: GTNWSRP-72
URL:
https://jira.jboss.org/browse/GTNWSRP-72
Project: GateIn WSRP
Issue Type: Bug
Components: Producer
Affects Versions: 2.0.0-CR03
Reporter: Matt Wringe
Assignee: Chris Laprun
Fix For: 2.1.0
Each registration should be able to have particular portlet contexts assigned to it. This
will allow for the following to occurs:
- only allow cloned portlets for a particular registration to be accessible to the
registration which created it
- allow for portlet filtering based on registration, ie could do have portlets available
only to registered consumers, or only to a particular registration
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira