Hi there,
I'm working on some portlets which I lay on Springs Portlet MVC framework. Now one question comes around: In these portlets I need some session objects (user info, etc) - to create this objects I was thinking of using a filter. My question is now: Do I have to declare my filter on normal webapp context (web.xml
) or do I need to place the filter on portlet level? (placing portlet filters on portlet.xml
)
If I'm not completely wrong all spring portlets run in the spring context which has access to the normal webapp context, so it should be enough do declare a filter as DelegatingFilterProxy
where my session objects are created.
Am I wrong with this logic?
Update:
Ok - maybe I want something impossible: I just want to create a session bean with user information if an user logs into the portal (JBoss Portal
). I tried filter/listener to achieve this but not one of my approaches works. With porting my JSR-168 portlets to Spring supported portlets I hoped this could be achievable.
I placed a filter into my web.xml
but this is only triggered, if the user logs out - not on login.