The basic issue is that each page, including the frameset,
is handled by a different HTTP GET request. If you had
a bean that lived at the session level, you could access
that bean in all of the requests (although syncronization
would be something to watch for).
The major issue as I see it is in the creation of the Bean -
which page creates it. If that happens on the request of the
Frameset, you would could make sure that the bean was setup
by the time the browsers accessed the resulting frameset pages,
and began to request the Framed Pages, certain that the bean
was already instantiated at the session level.
-----Original Message-----
From: A mailing list about Java Server Pages specification and reference
[mailto:[EMAIL PROTECTED]]On Behalf Of Jelane K. Johnson
Sent: Wednesday, April 21, 1999 3:14 PM
To: [EMAIL PROTECTED]
Subject: JSP and Frames - Accessing Bean Info from Frame Pages
I have the following set of framed pages: index, header, body,
footer
I am calling the index (frameset) page from the servlet and I want
to access bean information from the body page, but I keep getting a
'bean not found message.' How do I call the index jsp page and allow
the body page to access the bean properties?
Jelane Johnson
Andersen Consulting
P.S. Is there a JSP FAQ out there anywhere?
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
