Jeff Amiel wrote:
On 6/20/07, Roberto Nunnari <[EMAIL PROTECTED]> wrote:
Yes. That's it. It happens at random times.. not always.
When it happens, all I get instead of the table in the browser is:
Nothing found to display.
makes no sense....sure you don't have a local variable inside the
execute method called stories or something equally silly?...
hehe.. no I don't have a local variable inside the execute method..
in that case the instance variable would never get assigned..
....or even better...maybe another element called 'stories' being put
on the value stack on top of the action class element with the same
name.......
no.. by the way, do you know what scope would stories be put in?
request, session, application, page, or action?
I assume action, as the variable is on the action, but I used to
access it via JSP EL, that doesn't know about action scope, but
only request, session, application and page scopes..
Doesn't display-tag have the ability to set the scope of the
collection you are looking for (like sessionScope. as aprefix or
requestScope.)......instead of the OGNL stuff with the
name="${stories}", just do name="stories". Displaytag should just
find it automagically...or you can play with those prefixes to try to
pinpoint it in case some other element with same name is being placed
first in the search path.
I didn't know I could use just name="stories". I tried that and it
works.. but just like before, at random times, the view doesn't find
the property, even though the execute method prints them on stdout.
humm...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
