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

Posted to dev@tapestry.apache.org by "Patrick Moore (JIRA)" <de...@tapestry.apache.org> on 2007/11/01 10:12:51 UTC

[jira] Created: (TAPESTRY-1876) RequestCycle unnecessarily secretive about QueryParameterMap key values

RequestCycle unnecessarily secretive about QueryParameterMap key values
-----------------------------------------------------------------------

                 Key: TAPESTRY-1876
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1876
             Project: Tapestry
          Issue Type: Improvement
    Affects Versions: 4.1.4
            Reporter: Patrick Moore


RequestCycle has QueryParameterMap but does not expose the KeySet for this map. We have an Encoder that has an informal set of parameters. The Encoder needs to create a "special", well-known key that holds the list of keys in order for the matching service to find and use all the data. 

This method really breaks down when we have 'decorator' encoders, these also need to know about the "special". Would be more correct if RequestCycle would not be secretive and simply expose the keySet for QueryParameterMap.


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