Correction. Default implementation uses any configured roles. Your
implementation can override this and implement whatever logic you want.
- Original Message -
From: "Antony Joseph" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List"
Subject: RE: Request Pro
ailing List"
Subject: RE: Request Processor validation Question
Date: Mon, 14 Mar 2005 10:18:34 -0600
>
> If I use the processRoles(), does that mean I have to use the J2EE
> authentication mechanism for web applications? Using the container
> and declare the applications declarat
List
Subject: Re: Request Processor validation Question
Hi Scott,
Check the javadocs for the RequestProcessor. Any method which has an
ActionMapping as an argument can be used to figure out the action (ex:
mapping.getPath()). If you plan to do authorization the method processRoles()
is a good
-
From: "Scott Purcell"
To: user@struts.apache.org
Subject: Request Processor validation Question
Date: Mon, 14 Mar 2005 09:31:35 -0600
>
> Hello,
> I have extended the RequestProcessor and I am looking for a way to
> find out where the page is going to. The reason for
Hello,
I have extended the RequestProcessor and I am looking for a way to find out
where the page is going to. The reason for this is as follows. I am giving each
user a UserObject when they hit the site. Later on, after they log in, I set
some flags to know they are valid inside the application
5 matches
Mail list logo
