[ http://issues.apache.org/jira/browse/JS2-563?page=all ]
Ate Douma resolved JS2-563.
---------------------------
Resolution: Cannot Reproduce
I've just tested this out on both 2.0-FINAL and 2.1-dev and cannot reproduce
this.
When I set an attribute in the PickANumber portlet (demo application) and try
to look it up in the LoginPortlet (j2-admin application) I get a null value as
expected.
> Request attribute "leak" between web applications?
> --------------------------------------------------
>
> Key: JS2-563
> URL: http://issues.apache.org/jira/browse/JS2-563
> Project: Jetspeed 2
> Issue Type: Bug
> Components: Container
> Affects Versions: 2.0-FINAL
> Reporter: Nils-Helge Garli
>
> Two portlets in separate war files, deployed and placed on the same page.
> Both portlets dispatch to a servlet in the render phase. The second portlet
> on the pages can "see" the request attributes set by the servlet in the first
> portlet application. For instance, if the first portlet dispatches to the
> servlet, and set a request attribute "foo", the servlet in the second portlet
> application can do a request.getAttribute("foo") and get hold of the same
> attribute as the first one set.
> See http://jira.opensymphony.com/browse/WW-1318 for a more detailed
> description, and portlets to reproduce the problem.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
