Anything you put in the request/session/application attributes is
available anywhere else you have access to those collections.
It's generally considered bad form to pass data to views that way but if
it makes sense for your application then do it. Note that some
templating technologies (like XSLT) don't provide access to the
attribute collections.
If you're calling session.setAttribute("object1", foo); then you can
access the foo in JSTL as ${object1}.
Jeff
> -----Original Message-----
> From: Thompson, Kris [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 30, 2003 2:43 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [Mav-user] Getting to an object from JSP
>
> I believe so, Jeff or others? As I understand it, model represents
your
> Controller class therefore anything in your jsp that is
${model.something}
> where something is a getter in your controller.
>
> The quick answer is Yes.
>
> >
> > So basically everything the jsp needs should ge accessible
> > with a getter
> > method in the current controller object? (Trying to
> > understand the theory).
> >
> >
> >
> >
> >
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> [INVALID FOOTER]
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
[INVALID FOOTER]
