You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org> on 2005/05/03 16:06:14 UTC

[jira] Resolved: (TAPESTRY-58) getParameterNames in RequestContext

     [ http://issues.apache.org/jira/browse/TAPESTRY-58?page=all ]
     
Howard M. Lewis Ship resolved TAPESTRY-58:
------------------------------------------

     Resolution: Invalid
    Fix Version: 4.0

Didn't use your patch, but the request processing pipeline in 4.0 does exactly what you described; it uses a ServletRequestWrapper to make it look like the data posted in the multipart form was posted as with a normal request.

> getParameterNames in RequestContext
> -----------------------------------
>
>          Key: TAPESTRY-58
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-58
>      Project: Tapestry
>         Type: Bug
>   Components: Framework
>     Versions: unspecified
>  Environment: Operating System: Other
> Platform: Other
>     Reporter: Hugh Leather
>     Assignee: Howard M. Lewis Ship
>      Fix For: 4.0
>  Attachments: Changes.zip
>
> A suggested change to let the request found from the RequestContext work fully 
> even in the context of file uploads.

-- 
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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org