The problem might have something to do with the way you have defined the
scope of your bean. If it is "request," then you will lose the original
contents of the bean when the user submits the form.
Here's an example,
ACTION: Populate form bean, and forward to jsp
STRUTS: display jsp
USER: Submi
to stop the
shutdown process once it starts.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 07, 2005 12:40 PM
To: Struts Users Mailing List
Cc: Struts Users Mailing List
Subject: RE: Re: Session problem
"James Harig" <[EMA
ting down the system while they are still on it..." was that
Weblogic is telling me that there are active sessions, even though I
have invalidated the session once the user logs out. So I don't know if
a person is still logged in, or if it is those extra sessions that are
being handed out b
Hi,
Here's my take on the subject
The key here is that you want the users to finish what they are doing before
you let the server shut down. This means a few things:
1. If the webapp uses the concept of logging in, new "login sessions" shouldn't
be allowed. Attempts to login should be re
Hi Fea,
It isn't working for you because boolean is a primitive type, and can't be
instantiated. The DynaActionForm can only be used with classes, so you will
need to use java.lang.Boolean to support boolean values.
I hope this helps,
James
-Original Message-
From: fea jabi [mailto:
Hi Gaet,
If you are interested in knowing what is going on, you can look at the java
servlet that is generated from your .jsp. For Tomcat, the servlets are in the
/work directory.
-Original Message-
From: Gaet [mailto:[EMAIL PROTECTED]
Sent: Monday, November 21, 2005 12:46 PM
To: St
6 matches
Mail list logo
