Never heard of anything like this... On 10/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Of course I can design around the issue, but I would prefer not to. This component of the application is internal only, to the amount of data passed in the request is not as big of a deal. The point was to eliminate unneccessary pagination, which I have seen have a history of aggrivating users working on large datasets. I am just trying to find out if this is a known issue before I work on putting together a simpler recreation of the problem for a bug report. If this capacity of the framework can only work within a threshold, then it seems like a bug, be it in the framework or the docs. > -------- Original Message -------- > Subject: Re: Bug with large dynamic forms? > From: Jabbar <[EMAIL PROTECTED]> > Date: Sun, October 15, 2006 4:22 pm > To: "Tapestry users" <users@tapestry.apache.org> > > Hello, > > I've never had to show hundreds of objects. Can't you reduce the > number of objects to show? > > On 15/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Sorry about that, this is with version 4.0.2. > > > > > -------- Original Message -------- > > > Subject: Bug with large dynamic forms? > > > From: [EMAIL PROTECTED] > > > Date: Sun, October 15, 2006 4:16 pm > > > To: users@tapestry.apache.org > > > > > > Hello all! > > > > > > I think I way be experiencing a bug in tapestry but wanted to find out > > > if anyone else had experienced it or has heard about it. > > > > > > When I have a large dynamic form, with fields rendered for a couple > > > hundred objects in my collection, the Form component seems to wig out > > > and not render the formids hidden field properly. > > > > > > Instead of the expected > > > value="imagesList,title,date,location,tags,rotate,description,title_0,d > > > ... etc. I see that it renders (for the formids hidden field) a value > > > attribute that looks like value=<1000+ spaces> />. No quotes, just > > > value=, then over a thousand spaces, then the close of the tag. > > > > > > I struggled all day with the form not working, then noticed this weird > > > formids value in the rendered page source. After failing to see what I > > > was doing incorrectly, I finally gave up and just for a random stab, > > > tested my page with a dataset of only 6 objects instead of a few > > > hundred. And it worked! > > > > > > -- Thaddeus > > > > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > > > -- > Thanks > > A Jabbar Azam > > --------------------------------------------------------------------- > 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]
