Hi Robert,
What is your need?
In my webapp I wrap the servlet request (in a filter) and put a custom Principal in there. (sounds similar to the message you reference below)
Is it because you'd like to test code using servlet security API but you do not wish to configure the security features of the container?
Correct. I have patched HttpServletRequestWrapper in my working copy. I just figured it was not of interest to the larger group since there was no reply.
no biggie, -Rob
Some past thoughts on this: http://www.mail-archive.com/[email protected]/msg00164.html
-Vincent
-----Original Message----- From: Robert Koberg [mailto:[EMAIL PROTECTED] Sent: jeudi 20 janvier 2005 04:49 To: [email protected] Subject: add setUserPrincipal(Principal) to HttpServletRequestWrapper?
Hi,
Would it be generally useful to add a method like:
private Principal principal;
public void setUserPrincipal(Principal principal) { this.principal = principal; }
public Principal getUserPrincipal() { return this.principal; }
to HttpServletRequestWrapper?
Or how would you suggest using a custom request wrapper in cactus? Is there a property I can set (I did not see one, but I might not know what I am looking for...)?
best, -Rob
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
