portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Resolved: (JS2-1225) Synchronize JetspeedPortletFactory maintained caches on PortletRegistry changes
Date Tue, 23 Nov 2010 02:22:17 GMT

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

Ate Douma resolved JS2-1225.
----------------------------

    Resolution: Fixed

JetspeedPortletFactory has been extended to implement RegistryEventListener and it will synchronize
(and/or flush) its internal portlet caches on PortletRegistry changes.
To enable this feature, the following new Spring assembly configuration needs to be added
for existing Jetspeed 2.2.2-SNAPSHOT based portals:

  <!-- register JetspeedPortletFactory as RegistryEventLister on the PortletRegistry -->
  <bean id="registerPortletFactoryPortletRegistyEventListener" class="org.springframework.beans.factory.config.MethodInvokingFactoryBean">
    <meta key="j2:cat" value="default or registry" />
    <property name="targetObject"><ref bean="portletRegistryImpl"/></property>
    <property name="targetMethod"><value>addRegistryListener</value></property>
    <property name="arguments">
      <list><ref bean="portletFactory"/></list>
    </property>
  </bean>

The above configuration is already added to the default Spring assembly in registry.xml
 

> Synchronize JetspeedPortletFactory maintained caches on PortletRegistry changes
> -------------------------------------------------------------------------------
>
>                 Key: JS2-1225
>                 URL: https://issues.apache.org/jira/browse/JS2-1225
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Portlet Factory, Portlet Registry
>    Affects Versions: 2.2.1
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>             Fix For: 2.2.2
>
>
> JetspeedPortletFactory maintains several (small) internal caches which currently are
only cleared/reset on deregistration of an portlet application.
> For portlet (definition) scoped caches like their ResourceBundle or the PortletConfig
these needs to be flushed or synchronized when portlet definition changes are processed in
the PortletRegistry.

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


Mime
View raw message