• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

servlet filter not working in websphere portal 6.0

 
Gyan Shankar
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We are using struts portlet bridge to migrate a struts application onto websphere portal server.
It works fine.

We need to use a servlet filter however in the portal environment the filter is ignored.
The filter works fine within tomcat version of the build.
Any idea if we need to configure anything special to make it work?
 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Are you using JSR168 portlets?

JSR168 portlets don't require a Servlet mapping in the web.xml file, which is where Servlet Filters are configured.

PortletFilters are a new, upcoming features with JSR268. You may have a problem getting them to work with JSR168.

Good luck.

-Cameron McKenzie
 
Gyan Shankar
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think it is the IBM portlet api.
We are using the struts-portlet bridge.
We have just changed the request processor in the struts-config.xml to com.ibm.portal.struts.portlet.WpRequestProcessor.

Any idea how to get a normal servlet filter work in the websphere portal server?
 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well, you'd have to configure the filter in the web.xml file, but I would imagine it would then effect every portlet that comes in, not just one or two in particular.

JSR-268, the next version of the Portlet API, will address this, and make the whole situation much easier.

-Cameron McKenzie
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic