I believe adding volatile="true" to your loop will cause the loop to not serialize your object.
http://tapestry.apache.org/tapestry5/tapestry-core/component-parameters.html#orgapachetapestrycorelibcomponentsloop Josh On 10/12/07, Jean-Philippe Steinmetz <[EMAIL PROTECTED]> wrote: > > Hi all, > > I have a page that has a loop to iterate over some objects in a list and > display them as I need. I don't want to use a grid component because it > doesn't match the needs I need. I am not creating a table, I am creating a > selection box for a form. So my template looks like this: > > School: <select name="schoolId"> > > <t:loop source="schools" value="currentSchool"> > > <option value="currentSchool.id">${currentSchool.name} - > ${currentSchool.location}</option> > > </t:loop> > > </select> > > where my getSchools function returns a List of School objects. These > School > objects I have used successfully in grid components and other various > parts > of my application. When I try and run this page I get the following error: > > Error serializing component action for component Classrooms/Modify:loop: > School > > So I take it that I need to serialize the component but if so why does the > grid component work with the same list of objects? Is there another way I > can accomplish this without serializing the class? > > Jean-Philippe Steinmetz > > -- -- TheDailyTube.com. Sign up and get the best new videos on the internet delivered fresh to your inbox.
