[
https://issues.apache.org/jira/browse/BEEHIVE-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlin Rogers resolved BEEHIVE-1181.
------------------------------------
Resolution: Fixed
Implemented this enhancement in SVN revision 515658. I also added a new JUnit
test to cover the ScopedServletUtils class.
> Make ScopedServletUtils provide an alternative to getting the ScopedResponse
> via caching mechanism
> --------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-1181
> URL: https://issues.apache.org/jira/browse/BEEHIVE-1181
> Project: Beehive
> Issue Type: Improvement
> Components: NetUI
> Affects Versions: 1.0, 1.0.1, 1.0.2
> Reporter: Carlin Rogers
> Assigned To: Carlin Rogers
> Fix For: V.Next
>
>
> Currently, the ScopedServletUtils.getScopedResponse() routine caches the new
> ScopedResponse result of the first call in the outer request. Then on any
> subsequent calls it just returns the cached ScopedResponse from the outer
> request.
> In some cases there may be multiple calls to getScopedResponse() for a
> particular scope and a need to pass in a different real Response parameter.
> However, in these cases the returned ScopedResonse in the subsequent calls
> will be the cached one which was created in the first call to
> getScopedResponse() and wraps a different real Response. A modification to
> ScopedServletUtils could allow one to get a new ScopedResonse instance that
> wraps the different real Response rather than the cached ScopedResonse.
> Could add a new method to ScopedServletUtils, such as updateScopedResponse(),
> that would allow callers to get the new ScopedResponse instance. The method
> would also replace the cached ScopedResponse on the outer request with the
> new ScopedResponse.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
