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] Created: (JS2-728) Provide a Portals Bridges common.PortletResourceURLFactory implementation for Jetspeed
Date Thu, 31 May 2007 15:31:15 GMT
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 parameter.

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. 

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

View raw message