Thanks Igor, I created https://issues.apache.org/jira/browse/WICKET-2090
igor.vaynberg wrote:
the problem is wicket tester doesnt run wicket through the entire
web-request workflow and you are hooking into a part that is not being
hit. i have a good idea of where to add an extension point,
the problem is wicket tester doesnt run wicket through the entire
web-request workflow and you are hooking into a part that is not being
hit. i have a good idea of where to add an extension point, please
open a jira issue so i can attach a patch there and you can see if it
will work for you.
On Fri, Feb 6, 2009 at 9:06 AM, cpopetz cpop...@gmail.com wrote:
This works great when running in-container, but isn't playing well with
tests that use ajax. When an ajax link is clicked in-container, the full
request cycle is step()ed through. But BaseWicketTester.clickLink(), which
I
Hi,
I'm currently responsible for maintaining the Seam/Wicket integration for
the Seam team. Seam maintains a conversational context, a session-based
map that is keyed by an id associated with a set of requests. Previously
the wicket integration worked by wrapping every redirect or outgoing