Thanks for the suggestions. I'll try them out.
Cheers,
Jadeler
--- Aladin Alaily <[EMAIL PROTECTED]> wrote:
> Hi Jadeler,
>
> In response to your question about managing session
> objects, I would
> propose two methods:
>
> 1) Write a CustomRequestProcessor (which extends the
> struts
> RequestProcessor), and put your management code in
> there. As a struts
> programmer, you know that all requests *should* go
> through this
> processor. This way, if you (or someone else)
> forgets to extend a base
> class (as was suggested in another post), your
> validation still takes place.
>
> 2) Write a filter as you suggested. Plain and
> simple. The advantage of
> the filter is that it is not struts dependent and it
> can be mapped to
> specific urls. Consequently, not all requests will
> pass through the
> filter (unless you specify the map as '/').
>
> Good Luck.
> Aladin
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
__________________________________________________________
Find your next car at http://autos.yahoo.ca
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
