RE: Container Managed Authentication and roles attribute on actio n

[Jarnot Voytek Contr AU HQ/SC <Vo...@MAXWELL.AF.MIL>]

>In your web.xml file, you can define the page that is used for any
>particular status code (including 400).  Check out the <error-page>
>directive.

That's a workable solution, but a bit of kludge - assuming that the user can
get a error-code of 400 for other reasons than not being authorized.  I
guess I was hoping for a way to trap the response before it left the struts
code, perform some logic, and forward to another page (maybe the one they
just came from).

Thanks,
Voytek Jarnot

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: Container Managed Authentication and roles attribute on actio n

["Craig R. McClanahan" <cr...@apache.org>]

On Tue, 29 Oct 2002, Jarnot Voytek Contr AU HQ/SC wrote:

> Date: Tue, 29 Oct 2002 14:33:04 -0600
> From: Jarnot Voytek Contr AU HQ/SC <Vo...@MAXWELL.AF.MIL>
> Reply-To: Struts Users Mailing List <st...@jakarta.apache.org>
> To: 'Struts Users Mailing List' <st...@jakarta.apache.org>
> Subject: RE: Container Managed Authentication and roles attribute on
>     actio n
>
> >In your web.xml file, you can define the page that is used for any
> >particular status code (including 400).  Check out the <error-page>
> >directive.
>
> That's a workable solution, but a bit of kludge - assuming that the user can
> get a error-code of 400 for other reasons than not being authorized.  I
> guess I was hoping for a way to trap the response before it left the struts
> code, perform some logic, and forward to another page (maybe the one they
> just came from).
>

A different approach would be to subclass RequetProcessor and override the
processRoles() method to do something differnt.

> Thanks,
> Voytek Jarnot

Craig


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>