I think some of the problems you are experiencing are part of a bug I found in the current version of protoype, which I've yet to patch back to them. (I only found and fixed it a day or so ago).
Those interested in tapestry/ajax would benefit from taking a look at tacos.sourceforge.net. The current release has a few ajax components, and the current release being worked on (mostly in the mailing list) is providing a comprehensive support system for ajax tapestry logic that should fit most peoples needs. It will hopefully provide equivalent functionality to that of projects like ruby on rails... The ajax branch being worked on is also heavily involved in integrating Rico, which ~will~ mean LiveGrid as well, so interested parties may want to take a peak.. jesse On 8/18/05, Ben Wong <[EMAIL PROTECTED]> wrote: > > Don't know if anyone still cares, but I solved the problem (with the > recommendations of others in this list) by using a servlet filter. The > servlet filter simply checks the incoming URL and rewriting any '?' to '&' > in the query string (e.g. httpRequest.getQueryString()). I must admit it is > a hack but it worked for me. > > On another related note, I gave up on the Rico LiveGrid because I couldn't > get it to refresh with new records. And sometimes it was firing off queries > to the db at random times. I am sure it is a user problem (not LiveGrid's > fault), but I didn't have any more time trying to get it to work. The > documentation on what the parameters are and how to set them properly also > wasn't there. I also realize that we don't have tables that have thousands > of records (not yet anyway) - so the requirement to use LiveGrid just wasn't > there. > > I think it is cool technology and I plan to try to use it again in the > future. > > Thanks all those who help, > Ben > > > > -----Original Message----- > > From: Darío Vasconcelos [mailto:[EMAIL PROTECTED] > > Sent: Friday, August 12, 2005 10:39 AM > > To: Tapestry users > > Subject: Re: Rico Ajax / Tapestry - How to Call Tapestry URL > > > > I do think it would make a cleaner solution. Better yet, if the > > parameters could be wrapped into a Tapestry-like URL, it would turn > > LiveGrid into an almost-native component. Maybe someone with > > experience in Tapestry/Ajax integration could help you... > > > > Ben (the original poster) might enlighten us by telling us how he > > worked it out... > > > > On 8/12/05, Richard Cowin <[EMAIL PROTECTED]> wrote: > > > Hi, > > > I am the designer of Rico's LiveGrid. > > > Please, excuse my Tapestry ignorance. > > > > > > If LiveGrid supported a fixed parameter for the > > "?service=external/foo&", > > > would that make a cleaner solution for this issue? If so, this seems > > > like a reasonable thing for LiveGrid to support and I will post an > > issue > > > for it. > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > I have enough money to last me the rest of my life, unless I buy > > something. > > Jackie Mason > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
