Re: [Stripes-users] retrieve StripesFilter configuration outside of an Stripes request

Yes ServletContextAware suffers the same problem. I think the best option right now, with the current codebase, is to subclass StripesFilter and do whatever you need in init(). This way you are quite sure the filter is there :P A more "Stripey" way to handle this would be a proper initializer com

Re: [Stripes-users] retrieve StripesFilter configuration outside of an Stripes request

Hi Rémi, indeed the init sequence problem is there, but the mbean is going to be called much fewer times than a regular intercepted URL. It doesn't matter too much if the mbean returns an empty map (people using the mbean would know the application is starting). Besides, at the time the MBean is g

Re: [Stripes-users] retrieve StripesFilter configuration outside of an Stripes request

Hi again Juan Pablo, Cool ! Glad to know it works. Indeed, you still have a "init sequence" problem, but I guess that those url bindings are irrelevant until the filter is up. I mean, you get the actual result by invoking the MBean : it returns an empty list of bindings if the filter is not ready

Re: [Stripes-users] retrieve StripesFilter configuration outside of an Stripes request

Hi Rémi, thanks for the tip! :-) Although my JMX MBean doesn't have access to the servlet context, it's also a Spring managed bean, so I've also made it ServletContextAware, which solves the access to the servletContext from the MBean. At the time of servletContext injection, the Stripes Filter h