PrincipalSessionAttributeFilter does not forward request to next filter/resource in chain.

I noticed that when the PrincipalSessionAttributeFilter is enabled within JBOSS and you try to navigate in a browser to a web app resource, the resource never gets call because the filter does not foward to the next filter/resource in the chain.

I was hoping by enabling this filter I would have a way to call my custom login modules logout operation on session expiration. At a minimum enable me to get the principal name so that I can make appropriate database logout calls.

It was my understanding that the PrincipalSessionAttributeFilter would place the Principal within the session so that I could access it within a SessionListener when the session is destroyed.