Well here's a trace of what happens that causes the problem : During the RESOLVE_TARGET step of RequestCycle, the target is trying to be resolved using the DefaultRequestTargetResolverStrategy, which first inside the resolveRenderedPage() method uses Session.getPage() to get the page,(which adds it to the usedPages map,a hidden side-effect imho),and then calls resolveListenerInterfaceTarget() where it retrieves the Component for the path and calls isVisibleInHierarchy() on it. This method throws an exception in my application, which is caught back in the RequestCycle. Now, the target didn't have a chance to be added to requestTargets, but the page has been added to the usedPages. In the detach phase, the requestTargets are detached one by one, which in this case is only the exception page generated. So when i push back and click on another link with the same page id, it'll fall into the loop mentioned, cause the thread hasn't been cleared. I guess this somehow means a problem with the usedPages map, where it should be cleared on an exception.
Iman ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
