I guess we have to use listener to load spring's context

[Topxp Lee]

    <filter>
        <filter-name>Acegi Filter Chain Proxy</filter-name>
        <filter-class>net.sf.acegisecurity.util.FilterToBeanProxy</filter-class>
        <init-param>
            <param-name>targetClass</param-name>
            <param-value>net.sf.acegisecurity.util.FilterChainProxy</param-value>
        </init-param>
    </filter>

The filter will find ApplicatinContext before initialization of spring's servlet. So it'll cause an exception.

I guess we have to use listener to load spring's context when use Acegi .

Would it be correct ?

[jas]

I believe using ContextLoaderListener works for most people, though it did not for me. I'm stuck with JRun 4, and it apparently initializes the filters ahead of the listeners. Even with my Acegi filters configured for lazy init, I could not get the root application contenxt loaded in time.

I ended up creating my own ContextLoaderFilter and configured it as the first filter in the chain. This class is a direct ripoff of the Spring ContextLoaderListener code and it does the same thing in the Filter init() method.

If ContextLoaderListener does not work for you, I can post my ContextLoaderFilter if you need it.

Best of luck,

Jeff

[Topxp Lee]

Hi,Jeff

My AppServer is JBoss4,using ContextLoaderListener works for me now. But I'm not sure that it'll works suppose I use tomcat/weblogic/websphere/Resin etc. I had not test still.

Your idea about ContextLoaderListener is very well. It can ensure the applicationcontext loaded in time. I'll use it if I get into trouble when deploy in other appserver.

Thanks your reply. ^_^

[jas]

You're welcome! Good luck!

Jeff