Re: How to provide default sorting as descending order to a grid?

2010-03-07 Thread Stephan Windmüller
On 08.03.2010 07:06 Chitrangada Sarkar wrote: We have developed a customised grid component using the grid.class.I want to provide default sorting as descending order.For this i have provided a sorting model similar to that of DefaultGridSortModel but the value of a sortColumnId is not getting

How to provide default sorting as descending order to a grid?

2010-03-07 Thread Chitrangada Sarkar
Hi , We have developed a customised grid component using the grid.class.I want to provide default sorting as descending order.For this i have provided a sorting model similar to that of DefaultGridSortModel but the value of a sortColumnId is not getting persisted,so unable to do any sorting.Any

Re: [T5.2.0] two problems when extending Autocomplete

2010-03-07 Thread Joost Schouten (ml)
My apologies, there was a problem in my code that for some reason only started playing up after the latest commits. I mixed in both the Autocomplete and my own ForceAutocomplete which extends Autocomplete. This caused the problem and for some reason worked in the previous versions. Thank you f

Re: [T5.2.0] two problems when extending Autocomplete

2010-03-07 Thread Joost Schouten (ml)
Thanks for fixing this so quickly. I'll try to dive into the problem of generateResponseMarkup(MarkupWriter writer, List matches)) no longer being called and report back on it. Cheers, Joost Howard Lewis Ship wrote: On Fri, Mar 5, 2010 at 7:39 PM, Joost Schouten (ml) wrote: Hi, I have f

Re: AjaxFormLoop Exception on 5.1.0.2 upgrade

2010-03-07 Thread Thiago H. de Paula Figueiredo
On Sun, 07 Mar 2010 15:12:49 -0300, wdahu wrote: I solved this problem. It is not caused by org.apache.tapestry5.services.ComponentSource.getPage(pageName) in my Dispatcher only by the argument of this method. I used the example from http://wiki.apache.org/tapestry/Tapestry5HowToControlAccess a

Re: AjaxFormLoop Exception on 5.1.0.2 upgrade

2010-03-07 Thread wdahu
I solved this problem. It is not caused by org.apache.tapestry5.services.ComponentSource.getPage(pageName) in my Dispatcher only by the argument of this method. I used the example from http://wiki.apache.org/tapestry/Tapestry5HowToControlAccess and there is int nextslashx = path.length();