portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott T Weaver (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-315) Premature access to portal can break access to portlets.
Date Thu, 21 Jul 2005 17:34:47 GMT
    [ http://issues.apache.org/jira/browse/JS2-315?page=comments#action_12316387 ] 

Scott T Weaver commented on JS2-315:
------------------------------------

David, the lookup only happens if the PortetDefintion of an entity is null, if it is not,
not look up is performed.

Code from PortletEntityImpl

    public PortletDefinition getPortletDefinition()
    {
        // there are cases when jetspeed gets initialized before
        // all of the portlet web apps have.  In this event, premature
        // access to the portal would cause portlet entities to be cached
        // with their associated window without there corresponding PortletDefinition
        // (becuase the PortletApplication has yet to be registered).
        if(this.portletDefinition == null)
        {
            setPortletDefinition(registry.getPortletDefinitionByIdentifier(getPortletUniqueName()));
        }
        return this.portletDefinition;
    }

> Premature access to portal can break access to portlets.
> --------------------------------------------------------
>
>          Key: JS2-315
>          URL: http://issues.apache.org/jira/browse/JS2-315
>      Project: Jetspeed 2
>         Type: Bug
>   Components: Deployment, Portlet Entities and Preferences
>     Versions: 2.0-M4
>     Reporter: Scott T Weaver
>     Assignee: Scott T Weaver
>      Fix For: 2.0-M4, 2.0-FINAL

>
> When the portal is first deployed, and a user attempts to access the portal before the
portlet apps have been deployed into Tomcat, the portlets do not display correctly.  This
is to be expected, as the target portlet app is yet to register itslef into the portlet registry.
 However, due to caching of portlet windows and hence portlet entities, this cannot be corrected
and the portal must be bounced.
> To fix this, I have added logic to the PortletEntityImpl that allows it to try and load
it's related PortletDefinition by looking using the Fragment that is associated with saod
entity to pull the PortletDefinition from the registry, even in the case of the PortletEntity
being cached.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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