You are viewing a plain text version of this content. The canonical link for it is here.

Posted to pluto-dev@portals.apache.org by "Michael Freedman (JIRA)" <ji...@apache.org> on 2008/03/25 18:05:24 UTC

[jira] Updated: (PLUTO-478) Portlet Dispatching loses wrappers

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

Michael Freedman updated PLUTO-478:
-----------------------------------

    Description: 
When you dispatch using a wrapped request/response object, pluto doesn't preserve the wrapping when it executes the dispatch.  I.e. it upwraps the request/response and dispatches on that.  This prevents portlets from filtering request/responses to/from dispatched/servlet entities.

It would be nice if we added a TCK test for this case as well.  The spec is clear that one can use a wrapped request/response to dispatch to.  Though it doesn't specifically state that this must be preserved, it not only is the reasonable interpreation/expectation but is what clients will be counting on.  Hence for the sake of interoperability, having a TCK test will catch this problem early.

  was:When you dispatch using a wrapped request/response object, pluto doesn't preserve the wrapping when it executes the dispatch.  I.e. it upwraps the request/response and dispatches on that.  This prevents portlets from filtering request/responses to/from dispatched/servlet entities.


> Portlet Dispatching loses wrappers
> ----------------------------------
>
>                 Key: PLUTO-478
>                 URL: https://issues.apache.org/jira/browse/PLUTO-478
>             Project: Pluto
>          Issue Type: Bug
>          Components: portlet container
>    Affects Versions: 2.0.0
>            Reporter: Michael Freedman
>             Fix For: 2.0.0
>
>
> When you dispatch using a wrapped request/response object, pluto doesn't preserve the wrapping when it executes the dispatch.  I.e. it upwraps the request/response and dispatches on that.  This prevents portlets from filtering request/responses to/from dispatched/servlet entities.
> It would be nice if we added a TCK test for this case as well.  The spec is clear that one can use a wrapped request/response to dispatch to.  Though it doesn't specifically state that this must be preserved, it not only is the reasonable interpreation/expectation but is what clients will be counting on.  Hence for the sake of interoperability, having a TCK test will catch this problem early.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.