Seemingly (I haven't done this but actually I need to and probably will try it):

1) extend org.apache.struts.action.RequestProcessor
2) override either the processPreprocess method, or the processMapping method, either of which is invoked *before* processActionForm
3) in processPreprocess, issue redirect to login page or error page and return false if, say, your "User" object does not exist as a Session attribute
or
3) in processMapping, return an alternative ActionMapping (to your login page or error page -- one which does not require a Session-scoped form for setup) if the "User" object does not exist.
4) edit the "controller" element of struts-config.xml to install your custom RequestProcessor


Hope that helps,

Erik



Ricardo Andres Quintero wrote:

It sounds good but i dont know how to do it!
can u explain to me how to?

On Tue, 31 Aug 2004 17:30:44 -0400, Erik Weber wrote


Perhaps you could override one of the RequestProcessor methods, and check for the existence of a known Session attribute, before Struts tries to work with the nonexistent form?

Erik

Ricardo Andres Quintero wrote:



Hello Guys
i notice this error that when the session expirates, if an action that uses a
beanform is requested, and validate is true, the framework normally tries to
execute the validate method of the bean, but you know the beanform just doesnt
exist anymore, but the request can not be treated for the action, so a


cannot find bean quincenaForm in scope session

message is presented instead of showing a customized message like
your session has expired or whatever similar.

How can i solve this problem?
--
Ricardo Andrés Quintero R.
Ubiquando Ltda.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Ricardo Andrés Quintero R.
Ubiquando Ltda.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]





--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to