AuthFilter in WLS SP8 only delegates ServletRequest to do methods

Question

All methods for processing authentication in the new AuthFilter
introduced in WLS 5.1 SP8 have a ServletRequest passed as parameter.
Preferably this should be a HttpServletRequest, so that one could also
get hold of the HttpSession and cache some information at login time. I
realize that e.g. doSuccessAuth will be called at every request after
login, but retrieving a boolean from the session to see if this is the
initial login seems to be a small overhead compared to retrieving the
information I wish to cache at each request. Also one could be certain
that the attributes needed in the cache would be there if the user is
allowed to log in.
A quick'n'dirty way to solve this is to cast the ServletRequest to a
HttpServletRequest within e.g. doSuccessAuth, though this is certainly
not the right way to solve this :)
The AuthFilter class which your Authentication filter must extend is
already a servlet with the service method implemented to 'delegate off
to the correct do method depending on what auth state the Request is
in', according to the AuthFilter documentation. So, wouldn't it be a
feasible idea to have the service method send a HttpServletRequest as
parameter to the do-methods like the servlet container does with the
doGet and doPost methods ?
Anyone agree ?
BEA ?

Answer 1

Is the ServerSessionPool on the same instance as the JMS Server? I believe there is an
          example provided for ServerSessionPools; have you verified that that works in your clustered
          environment?
          -Don
          Ashok Sridhar wrote:
          > One more clarification ... I am using a ServerSessionPool of listeners. I can send/receive
          > messages using the example clients but the serverside pool is not setup. Does
          > anyone know if there is a problem with using Startup classes in WLS Clusters ?