Re: Problem with too long urls

2006-10-30 Thread Julian Sinai
ent: Sunday, October 29, 2006 3:46:23 PM Subject: Re: Problem with too long urls If you don't want to mess with DataSqueezers and other esoterical stuff, you could use the FormLinkRenderer by MindBridge, you can download it from http://www.t-deli.com/. In short, specifying the "rende

Re: Problem with too long urls

2006-10-30 Thread Julian Sinai
riginal Message From: Sam Gendler <[EMAIL PROTECTED]> To: Tapestry users Sent: Sunday, October 29, 2006 3:36:05 PM Subject: Re: Problem with too long urls Generally, this occurs because Tapestry has been forced to serialize an object, or a collection of objects, to the form in order ensure

Re: Problem with too long urls

2006-10-29 Thread DarĂ­o Vasconcelos
If you don't want to mess with DataSqueezers and other esoterical stuff, you could use the FormLinkRenderer by MindBridge, you can download it from http://www.t-deli.com/. In short, specifying the "renderer" attribute of any DirectLink will automatically turn the request into a POST instead of GE

Re: Problem with too long urls

2006-10-29 Thread Sam Gendler
Generally, this occurs because Tapestry has been forced to serialize an object, or a collection of objects, to the form in order ensure consistency when the form is rewound. You can prevent this by defining a 'DataSqueezer' for your entities which will allow you to send a simple primary key from