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-605) Query string parameters should not (by default) be provided to portlets to be compliant to JSR 168 spec requirements
Date Tue, 31 Oct 2006 21:43:16 GMT
Query string parameters should not (by default) be provided to portlets to be compliant to
JSR 168 spec requirements 

                 Key: JS2-605
                 URL: http://issues.apache.org/jira/browse/JS2-605
             Project: Jetspeed 2
          Issue Type: Bug
          Components: Container
    Affects Versions: 2.1-dev
            Reporter: Ate Douma
         Assigned To: Ate Douma
            Priority: Minor
             Fix For: 2.1, 2.1-dev

Jetspeed currently provides query string parameters to all portlets on the page requested.
When a portlet already has a request parameter with the same name, the values are provided
as an array where the query string parameters take precedence.
Example: with a query string parameter color=red and portlet parameter color=blue, the portlet
will receive color=[red,blue].

Although the JSR 168 specs (PLT.11) doesn't make it very explicit this shouldn't be allowed
(and the TCK definitely doesn't validate it),
the portlet 1.0 API javadoc for PortletRequest.getParameter(String) *is* explicit on this:
"Only parameters targeted to the current portlet are accessible."

But, existing installations of Jetspeed-2 might already depend on this "feature".
I won't simply "fix" this by making Jetspeed-2 strict to the specs, but instead make this
feature optional/configurable although by default it should be specs compliant.

The solution will allow for three possible usages:
a) strict - no query string parameters will be visible to portlets (default)
b) portlet scoped parameters take precedence (like color=[blue,red] from the example above)
c) query string parameters take precedence (like color=[red,blue] from the example above which
is the current implementation)

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

View raw message