[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3670) Wicket filter shouldn't unconditionally set up scopes.
[
https://jira.jboss.org/jira/browse/JBSEAM-3670?page=com.atlassian.jira.pl...
]
Clint Popetz updated JBSEAM-3670:
---------------------------------
Attachment: wicketFilterContexts-take-2.patch
I've revised this patch as follows. In order to support testing of seam wicket apps,
SeamWebApplication needs to be responsible for setting up scopes, because we won't
have our filter hierarchy at test time. So move the context code to SeamWebApplication.
In addition, allow the destruction of contexts after each request to be delayed, so that
in testing one can query the values of wicket components that have injections after a
request, in order to determine if they received their proper values.
This patch replaces the previous one attached to this report.
Wicket filter shouldn't unconditionally set up scopes.
------------------------------------------------------
Key: JBSEAM-3670
URL: https://jira.jboss.org/jira/browse/JBSEAM-3670
Project: Seam
Issue Type: Patch
Reporter: Clint Popetz
Assignee: Clint Popetz
Attachments: wicketFilterContexts-take-2.patch, wicketFilterContexts.patch
This breaks out the changes from 3645 with this comment:
Seam's WicketFilter currently sets up scopes unconditionally if it is installed. This
causes faces requests to fail because the SeamPhaseListener also sets up and tears down
scopes, and so when the wicket filter finishes and tries to tear down its scopes, it finds
them gone and an exception occurs. I've changed WicketFilter to not set up scopes, but
instead to have WicketFilterInstantiator's anonymous subclass of the real WicketFilter
install the scopes _if_ wicket has determined the request is a wicket request.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira