in JBoss Portal 2.7 you will be able to use portlet filters defined by JSR 286 to achieve that result.
Meanwhile a way that may work is to use a servlet filter in your application and configure it using dispatcher tag such as:
<filter-mapping> <filter-name>MyFilter</filter-name> <url-pattern>/jbossportlet</url-pattern> <dispatcher>INCLUDE</dispatcher> </filter-mapping>
I think this should work but I have not tested it. The "/jbossportlet" url pattern is the special servlet injected at runtime in the portlet application to make the portlet container dispatch in the war file containing your portlets.
that's odd.. i need to define a filter-mapping without defining a filter element? that works? and then, what objects would the filter inject into my portlet? in request scoped attributes? i'm sorry, it's not clear to me..
MyFilter is implicitely the filter you will implement, sorry for not being more explicit.
this is still not clear to me..
say i implement a filter MyFilter. how can i use it to inject a portal level object into the portlet application?