Skip to Content
0
Former Member
Nov 13, 2006 at 05:11 PM

Portal requests don't hit the deployed J2EE filter

13 Views

Hi,

What I am tring to obtain is that all requests are filtered via a J2EE filter. I've deployed the filter and tested it successfully. The filter mapping was set to "/*" so that it catches all requests. It works fine when tested at the J2EE level.

The problem comes when I tested it within the portal. The filter doesn't seem to be hit (because upon hitting some values are stored in the HttpSession. A session dump shows interesting results; the test at the J2EE level (via a servlet) shows the values set correctly in the session, as below:

Session_Id: (J2EE779911300)ID0720145750DB10614845087046755149End
Session Creation Time:Mon Nov 13 11:57:12 EST 2006
Session_class:class com.sap.engine.services.servlets_jsp.server.runtime.client.ApplicationSession
TEMP_LANG fr

The test at the portal level (via a portal application PAR deployment, jsp) shows different results, even if the session ID stays the same. Both tests were made in the same browser window.

Session_Id:(J2EE779911300)ID0720145750DB10614845087046755149End
Session Creation Time:Mon Nov 13 10:45:28 EST 2006
Session_detail:class com.sap.engine.services.servlets_jsp.server.runtime.client.ApplicationSession
PCSESSION_username@com.sap.netweaver.coll.appl.ui.rtc.SessionManager: 
http://sapportals.com/xmlns/cm.lastRequest: 
NavSessionKey: 
http://sapportals.com/xmlns/cmsession_user: 
PCSESSION_Guest@my.new.logon.default: 
NavigationContextWID1163432756846: 
com.sap.portal.desktop.theme: 
PCSESSION_username@com.sap.portal.navigation.detailedtree.DetailedNavigationTree: 
com.sap.portal.desktop.url: 
com.sap.netweaver.bc.wdf2.model.scope.HttpSessionScope: 
com.sap.portal.desktop.user: 
com.sap.portal.desktop.page: 
NavigationContext: 

Now the question: why the filter is not being invoked? Also, where is the object named TEMP_LANG from the first test? What am I missing here?

Thank you,

Adrian