portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ate Douma <...@douma.nu>
Subject Warning: [Was: [jira] Resolved: (JS2-728) Provide a Portals Bridges common.PortletResourceURLFactory implementation for Jetspeed]
Date Thu, 31 May 2007 16:06:39 GMT
Fellow developers,

I've just implemented a new Portals Bridges common interface in Jetspeed-2 trunk.

For those of you building off the trunk (but not building bridges), you need to update your
local version of the 
org.apache.portals.bridges:portals-bridges-common-1.0.2-RC.jar in your maven (1 and/or 2)
The latest version is already uploaded to the maven-1 and maven-2 repositories at www.bluesunrise.com
so just deleting the jar from your local repository will 
do the trick.



Ate Douma (JIRA) wrote:
>      [ https://issues.apache.org/jira/browse/JS2-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> Ate Douma resolved JS2-728.
> ---------------------------
>     Resolution: Fixed
> Implemented
>> Provide a Portals Bridges common.PortletResourceURLFactory implementation for Jetspeed
>> --------------------------------------------------------------------------------------
>>                 Key: JS2-728
>>                 URL: https://issues.apache.org/jira/browse/JS2-728
>>             Project: Jetspeed 2
>>          Issue Type: New Feature
>>          Components: Aggregation, Ajax, Container
>>    Affects Versions: 2.1.1
>>            Reporter: Ate Douma
>>            Assignee: Ate Douma
>>             Fix For: 2.1.1
>> Portals Bridges now provides a PortletResourceURLFactory interface, see PB-65, which
is defined for creating direct Portlet access urls, somewhat similar to what the Portlet API
2.0 ResourceURL will bring natively.
>> For Jetspeed-2 it will be quite easy to provide an implementation of this interface
by serving a (Render) request over the portlet-pipeline.
>> The only requirement will be that the portlet-pipeline is defined (under that name)
in the Spring assembly as it will be invoked using a PortalReservedParameters.PIPELINE request
>> One caveat: By default (although configurable) Jetspeed-2 stores navigational state
in the session, so parameters set on the RenderURL as created by our PortletResourceURLFactory
implementation might be saved too. But that is not what should happen as these ResourceUrls
should not change the nav-state.
>> So, I'll define additional reserved (portal) request parameters to indicate the provided
request nav-state is to be treated as transient. 

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org

View raw message