Even though it is a static process, the bean is an instance of a "new'ed"
object running in the VM. It is just the html that is in the jsp that is
static.
On Thu, 13 Jul 2000, Tom Wnuk wrote:
> Using '<%@ include...' is a static process. If you're using
> '<jsp:useBean...' in both that could be causing your problems. Also, why do
> you include page two into page one and then set the action to call page one
> again?
>
> Why not create another JSP page to process the login and then you can always
> do a redirect to whatever page you'd like.
>
> I'm not sure what your code looks like so it's just a guess. You're
> probably not using the '<jsp:usebean...' correctly in this situation. Code
> snippets would help.
>
> Tom
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of hanasaki
> Sent: Thursday, July 13, 2000 5:08 AM
> To: Orion-Interest
> Subject: JSP bug in state saving
>
>
> a.. I have written two JSP pages.
> b.. The first does a JSP:include of the second in one of its table
> cells. Page 1 shows an ID with myBeanX.getID()
> c.. Each of the pages uses MyBeanX with the same variable name and a
> scope of session.
> d.. The included page, page 2, is actually a login page that does a
> myBeanX.setID = <id for login from the page> and then calls the main page,
> page one, as its action. Page 2 also displays the current id with
> myBeanX.getID().
> e.. When page 1 is called, from page 2, it shows the previous ID while
> page 2, the included page, shows the "just set ID". Page 2 is the expected
> behavior. Page 1 is laggin behind.
> Comments, suggestions would be appreciated.
> Thank you.
>
>
