[ http://issues.apache.org/jira/browse/TOMAHAWK-623?page=all ]
Mario Ivankovits resolved TOMAHAWK-623.
---------------------------------------
Fix Version/s: 1.1.5-SNAPSHOT
Resolution: Fixed
> RedirectTracker and RedirectTrackerRequestMapWrapper remove implementation
> --------------------------------------------------------------------------
>
> Key: TOMAHAWK-623
> URL: http://issues.apache.org/jira/browse/TOMAHAWK-623
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Affects Versions: 1.1.4-SNAPSHOT, 1.1.5-SNAPSHOT
> Environment: Jboss Seam nightly build 20060821, myfaces
> 1.1.4-SNAPSHOT from cvs. Tomahawk and tomahawk-snapshot 1.1.5-SNAPSHOT from
> cvs facelets 1.1.11
> Reporter: German de la Cruz
> Assigned To: Mario Ivankovits
> Fix For: 1.1.5-SNAPSHOT
>
> Attachments: bulk.tar.gz
>
>
> Thanks for this greate component!
> I've probed tomahawk sandbox from cvs yesterday with the surprise it breaks
> my app!!
> After some research, I've found out the problem. It is produced by
> redirectTracker and RedirectTrackerRequestMapWrapper. This component store
> in the manager every bean that has been stored in the request in a redirect.
> I've a SFSB which only lives during a request. Then, it's created and, after
> that, it's destroyed and removed from request. But. There is already a
> reference in the manager. Then, in the next request, i've a reference in the
> request and, event more, it's invalid since it has been destroyed.
> Perhaps what I want is when a bean is remove from the request (with a
> removeAttribute) it must be remove from the manager to avoid this 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
