say).
Arif.
> -Original Message-
> From: Charlie Toohey [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 13, 2002 1:23 PM
> To: Tomcat Users List; Zhiyong Li
> Subject: Re: session question for tomcat 4.0.1 and 4.0.2
>
> First, of all, the assumption is that yo
First, of all, the assumption is that you have not turned off session support
using the JSP page directive, i.e. you do NOT have
<%@ page session="false">
The default is "true", so as long as you do not have this, you are fine.
Now, session.isNew() would continually return "false" if the followi
put the object in the request with setParameter().
the scope for this object is the request... it will be destroyed when you
call the 2nd servlet.
[]´s
Daniel A.
anil wrote:
> Hello,
>
> I do have servlet that process request and forward to another servlet.
> like.
> ->request-> Servle
If you just want the request object (the parameters) to be passed call the
servlet2 with the request object and finish what you're doing and the
request object is gong after that. Simple.
You can also create an hashtable in the session with those values from the
request object and delete the hasht
jus
- Original Message -
From: "anil" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 23, 2001 4:51 AM
Subject: Re: ===>Session Question<===
> Hi Warren,
>
> Thanks for the magic to destroy the session object when the response is
> d
-
From: anil [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 23, 2001 11:04 AM
To: [EMAIL PROTECTED]
Subject:Re: ===>Session Question<===
Thanks for the idea Alin. But that will invalidate all the
attributes in the
session. I want to kee
Thanks for the idea Alin. But that will invalidate all the attributes in the
session. I want to keep some. And some to keep only in the request context (what
ever you call).
request.getSession(true) -> this will create new session if you do not have a
session. I am not sure what will happen with
Hi Warren,
Thanks for the magic to destroy the session object when the response is
delivered to client. That's the idea. I have some attributes that I do not want
to go away as long as tomcat lives but need to have the freedom to change. some
to live only for the request.
Like say that I have a o
No, I do not want to invalidate whole session. I have some varibales that I
want keep. But I want some to alive only in the request.
thanks
anil
Alin Simionoiu wrote:
> have you try to invalidate the session ?
>
> - Original Message -
> From: "anil" <[EMAIL PROTECTED]>
> To: "tomcat" <
Sent: Tuesday, May 22, 2001 5:26 PM
Subject: RE: ===>Session Question<===
> hi anil,
>
> i hope i've got your intention, you want to pass an object graph from
> servlet1 to servlet2. tomcat provides session management through
> request.getSession().setAttribute() thes
hi anil,
i hope i've got your intention, you want to pass an object graph from
servlet1 to servlet2. tomcat provides session management through
request.getSession().setAttribute() these objects are accessible for the
duration of the session. If you only want the object graph to live for the
lif
have you try to invalidate the session ?
- Original Message -
From: "anil" <[EMAIL PROTECTED]>
To: "tomcat" <[EMAIL PROTECTED]>
Sent: Tuesday, May 22, 2001 12:26 PM
Subject: ===>Session Question<===
> Hello,
>
> I do have servlet that process request and forward to another servlet.
>
4 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Session Question
>
>
>
> John,
> In what ways may I have amend my pages
().
This means the page cannot be a static one.
John.
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 15, 2001 1:34 PM
Subject: Re: Session Question
>
> John,
> In what ways may I have amend my pages due to c
cc:
Subject: Re: Session Question
The session is usually used to persist objects between
tranactions with the client (browser).
If you are gathering several input fields to write to
the database towards the end of the "session" then
using the session is the way to go.
Or, you could use Java Script to gather all of the
input field
When it comes to form data, I always make a user object and bind this to a
session. The user object will contain all my put/get calls. Therefore, I
usually don't care what frame and/or page a user is on as long as the
session is up, I have the user object to "get" my data. Then you can have
ano
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 15, 2001 12:54 PM
Subject: Session Question
> I am currently writing a pretty complex data entry HTML page for an
> application. The HTML has 7 different frames where data is input, one
> represent
18 matches
Mail list logo