Hi everyone, did anyone encounter the following situation ? :
1. If you have wicket filter and jsecurity filter in your web.xml , you need to declare the jsecurity filter mapping _before_ the wicket filter mapping. Otherwise, you will get the error about your security manager not being bound to thread context or jvm. I suspect a bug in the wicket filter that prevents it from passing the filter execution to the next filters in the chain because once I swap them and let the jsecurity filter before the wicket filter all is ok. 2. I also got some jetty/jsecurityfilter exceptions while swapping these 2 filters but they are inconsistent because I do not get them now, at all. Will post them when I'll get them again. Anyway, did you meet the situation described at 1) ? I can consistently reproduce 1) with Wicket-1.4-rc1 and rc2 , JSecurity trunk sources , Spring 2.5.6, Jetty 6.1.14. Regards, Razvan
