> > With request scope, the bean is available until the last JSP servicing
> > this request ends. Thus, a page executed via <jsp:forward /> still has
> > access to the beans (provided, of course, they declare the reference
> > themselves via <jsp:useBean />).
> Does it hold for <jsp:include> also?

Yes.

> > With application scope, the bean reference is available to any servlet or
> > JSP page that executes within the same servlet context as the bean (i.e.,
> > the same web application.) This might be used for (bad example) page hits
> > during the application's current execution, or something like that. I
> > would say "Database connections,"
> >
> 'Sorry, I'm not clear on this! Does it have to be the same servlet context?
> In my case, JSP pages are used where, say, AccProducts and Location beans
> are used. That generates 2 different servlets, right? So, this scope'll be
> available for both these, is it?

Yes. What I meant was that each web-application gets its own servlet
context. (I think! I don't use application-scoped beans, so...) As long as
they're in the same application, the bean is accessible.

-----------------------------------------------------------
Joseph B. Ottinger               [EMAIL PROTECTED]
http://cupid.suninternet.com/~joeo      HOMES.COM Developer

===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:

 http://java.sun.com/products/jsp/faq.html
 http://www.esperanto.org.nz/jsp/jspfaq.html
 http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
 http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets

Reply via email to