Using "targetFilterLifecycle" filter init parameter seems to have cleared up
my issue. I think this feature should be better documented in the spring
into guide.
<init-param>
<param-name>targetFilterLifecycle</param-name>
<param-value>true</param-value>
</init-param>
Basically for each Spring DelegatingFilterProxy I declared - I needed to set
this property. Now my filter init methods are been called as expected. I
reckon that MyFaces 2.1 is reliant on a Filter/Listener to get a reference
to the servlet context, this is why I had the unexpected behaviour with
MyFaces. Just a guess.
Thanks drmike01 for the info on Filter config - this helped.
--
View this message in context:
http://shiro-user.582556.n2.nabble.com/Shiro-seems-to-prevent-myfaces-from-using-JNDI-tp7577577p7577599.html
Sent from the Shiro User mailing list archive at Nabble.com.
