(see below)
Troy Hart wrote:
>I haven't used tiles yet so I am in unfamiliar territory here, but I
>think you are not precluded from subclassing the request processor when
>you adopt them. I have noticed that there is a base RequestProcessor
>that must be used with tiles applications but it woul
:54:12 -0500
> > >>From: Eddie Bush <[EMAIL PROTECTED]>
> > >>Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> > >>To: Struts Users Mailing List <[EMAIL PROTECTED]>
> > >>Subject: Re: validating existence of session attributes i
PROTECTED]>
> >>Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> >>To: Struts Users Mailing List <[EMAIL PROTECTED]>
> >>Subject: Re: validating existence of session attributes in all Actions
> >>
> >>Do RequestProcessors sta
PROTECTED]>
>>Subject: Re: validating existence of session attributes in all Actions
>>
>>Do RequestProcessors stack like filters? This is a point I'm not clear
>>on.
>>
>
>No. There is one and only one request processor per application module
>(just
Unfortunately, the understanding I have is that Tiles is going to
override the RequestProcessor when the plugin initializes itself. Maybe
that's a Cedric question. Do you know what it does, Chuck? I guess I
could dig into the source for a definitive answer. But it doesn't
appear that Reque
Yes, my confusion was whether or not it is "additive" though. Can you
have multiple subclasses (independent - no relationships between them
other than that they all extend the same class - not extending
one-another) and them "add" instead of "replace" functionality?
I got tied up and didn'
Take a look at the processPreprocess() method in the
RequestProcessor class. I have seen this method used for
similar types of purposes.
Just a suggestion,
chuck
> Do RequestProcessors stack like filters? This is a point I'm not clear
> on. My reason for suggesting he subclass Action is tha
On Tue, 30 Jul 2002, Eddie Bush wrote:
> Date: Tue, 30 Jul 2002 12:54:12 -0500
> From: Eddie Bush <[EMAIL PROTECTED]>
> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> To: Struts Users Mailing List <[EMAIL PROTECTED]>
> Subject: Re: validating exist
Do RequestProcessors stack like filters? This is a point I'm not clear
on. My reason for suggesting he subclass Action is that: 1) It works
fine for me 2) I want to use Tiles (which is going to, I believe
override the ReqProc - the plugin automatically does this, I think). I
think ReqProc i
by putting this logic in the front controller
(RequestProcessor/ActionServlet) component you break the dependency on
the base action and life is good again...
Troy
On Mon, 2002-07-29 at 17:10, Struts Newsgroup (@Basebeans.com) wrote:
> Subject: Re: validating existence of session attributes i
Subject: Re: validating existence of session attributes in all Actions
From: "David Chu" <[EMAIL PROTECTED]>
===
Ah, thanks, I ended up creating a subclass of Action,
VerifySessionVarsAction, whos perform() verifies certain session variables
then calls performWithVerifiedUser().
ActionServlet or RequestProcessor (which ever is
appropriate for your app).
Hope this helps,
Troy
On Sat, 2002-07-27 at 12:55, Struts Newsgroup (@Basebeans.com) wrote:
> Subject: validating existence of session attributes in all Actions
> From: "David Chu" <[EMAIL PROTECTED
self using o.a.s.action.Action then subclass that. by doing this,
you automatically have that functionality in any actions your write with
your newly created action as their base.
Regards,
Eddie
Struts Newsgroup (@Basebeans.com) wrote:
>Subject: validating existence of session attributes in all
Subject: validating existence of session attributes in all Actions
From: "David Chu" <[EMAIL PROTECTED]>
===
What is the best way to check across all (or most) Actions that certain
session attributes are set? I could do an if test inside each Action's
perform() but I was wo
14 matches
Mail list logo
