no problem...
the funny thing is, is that if i put my own beans in a set, everything works
fine with the write tag. it just has a problem accessing the getValue
method on a Map.Entry. also, i tried a <jsp:getProperty name="subjectEntry"
property="value" /> and i got an illegal access error as well. shouldn't
this work? anyone have any clues? i searched the lists, but didn't see
anything pertaining to having problems treating a Map.Entry as a bean. is
it because it's actually an inner class of a Map that implements the
Map.Entry interface?
thanks!
chris
| chris wilson || web dev ||| [EMAIL PROTECTED] || | www.wondergeek.com |
|
> -----Original Message-----
> From: Michael Westbay [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 28, 2000 7:02 PM
> To: [EMAIL PROTECTED]
> Subject: Re: attempting to use iterate and write tags with maps
>
>
> Wilson-san wrote:
>
> > i believe that the first scope defines where the subjects beans
> is (in this
> > case, an attribute of the request) and the second one defines where the
> > subjectEntry bean is (created by the iterate tag, so it should
> only be page
> > scope)... right?
>
> I'd like to get a better understanding of this, too. So, what
> you're saying
> is that in
>
> > > > <logic:iterate name="subjects" id="subjectEntry" scope="request"
>
> the "subjectEntry" is defined for the "page" with data ("subjects") that
> was passed as a (or defined in the) "request"?
>
> > > > <bean:write name="subjectEntry" property="value" scope="page" />
>
> Then the current iteration of "subjects," which is this "subjectEntry,"
> belonging to this "page" has its "value" retrieved (via getValue)?
>
> OK. I think I get it now. Thank you. I just regret that it didn't help
> out your situation.
>
> --
> Michael Westbay
> Work: Beacon-IT http://www.beacon-it.co.jp/
> Home: http://www.seaple.icc.ne.jp/~westbay
> Commentary: http://www.japanesebaseball.com/
>
