The collection can be in any scope (request, session, application, page). I usually have an action which is invoked which when executed places the results in the request scope where the tag can retrieve it by its named attribute.
For example I might have a SearchAction which executes a search and places the results as a collection in the request scope under the name "results". My tag syntax would be something like this: <display:table pagesize="10" name="results" scope="request" requestURI="/do/search"> <!-- other stuff here --> </display> robert > -----Original Message----- > From: Mehta, Chirag (IT) [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 28, 2003 11:49 AM > To: Struts Users Mailing List > Subject: RE: Display Taglib > > > ServletExec v4.1. I think it might be something to do with the scope. > > If the display taglib is iterating over a collection, what scope should > the collection be and where should it be declared? > > > -----Original Message----- > From: Robert Taylor [mailto:[EMAIL PROTECTED] > Sent: 28 August 2003 16:21 > To: Struts Users Mailing List > Subject: RE: Display Taglib > > I'm using the Display Taglib with ServletExec and haven't had any > issues. What version are you using? > > robert > > > -----Original Message----- > > From: Mehta, Chirag (IT) [mailto:[EMAIL PROTECTED] > > Sent: Thursday, August 28, 2003 10:07 AM > > To: [EMAIL PROTECTED] > > Subject: Display Taglib > > > > > > Has anyone had experience using the Display taglib with ServletExec. > I'm > > getting the following error on the jsp page with no error in the log > > file. It used to work fine using Tomcat > > > > ServletException in:GIM2ResultsContents.jsp] null' > > > > Please help. > > > > Thanks > > > > Chirag > > > > > > -- > > NOTICE: If received in error, please destroy and notify sender. > > Sender does not waive confidentiality or privilege, and use is > > prohibited. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- > NOTICE: If received in error, please destroy and notify sender. > Sender does not waive confidentiality or privilege, and use is prohibited. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
