RE: list + search

Sounds like something is mis-wired... maybe an ognl property... I'd hate to think it is under the hood in the property descriptor logic.It would help to see your source code for the HTML template.If you can pass on the whole module, I will try to see if it runs on my 1.2-SNAPSHOT app. It just might. But then again... it might not   :)The latest stuff is fresh and runnable. Alejandro did a fleet job on completing the latest code.  I had though another JUNE run would come from these guys ... but there really isn't much left to do... TRAILS has it all except for a few decorations and cosmetics.I'd encourage you to bump up to the latest binaries if possible. Will save you alot of headache. At least if your trying to customize... you will get better results from trails-core.Best regards
Ken in nashua> Date: Tue, 1 Jul 2008 17:03:16 -0300> From: pablo.grana@...> To: users@...> Subject: Re: [trails-users] list + search> > this is what happens:> > (remember that I put the search form at the top of the DefaultList.html)> > suppose you have 2 text fields to search for.> > a= '___"> b= "___"> > If you post a value in a, then the two fields are cleared. If you post a value > in b, then both field take the same value. It looks like both fields take > whatever value was in b when it was posted.> > Whats more, I suppose that all the fields of the same type are set to the value > of the last field of that type.> > The result list is apparently correct.> > I'll try te send a diff for the roster demo with an example and some screenshots.> > regards.> > Alejandro Scandroli wrote:> > Hi Pablo> > > > I'm sorry but I'm not following. Did you mean that your search form> > it's always being cleared; it's never being cleared, or it's> > "randomly" being cleared.> > Can you show me your code?> > > > Saludos.> > Alejandro.> > > > On Mon, Jun 30, 2008 at 4:06 PM, Pablo Gra~na <pablo.grana@...> wrote:> >> Hi there.> >>> >> I want the search form at the top of the list of entities. Is there an easy> >> way? I put the search component in the DefaultList.html, but it works> >> partially: when the form is recreated, the status of the search page fields> >> are correctly restored, neither cleaned: some values are overwriten with the> >> values in other forms.> >>> >> I know close to nothing about tapestry, but I imagine that the problem is in> >> the way the value for the input tag is handled: instead of storing the value> >> in the page, the search component is used to create a new criterion and> >> reused for the next input tag.> >>> >> I am now hacking a bit (with trails 1.1.1, unfortunately), but I will> >> probably spend some time to get this working for other projects using a> >> 1.2-SNAPSHOT. Any hints?> >>> >> thanks a lot.> >>> >>> >> ---------------------------------------------------------------------> >> To unsubscribe from this list, please visit:> >>> >>   http://xircles.codehaus.org/manage_email> >>> >>> >>> > > > ---------------------------------------------------------------------> > To unsubscribe from this list, please visit:> > > >     http://xircles.codehaus.org/manage_email> > > > > > -- > Pablo Gra\~na> Chief Architect> Globant> Arg Office: +54 (11) 4109 1743> UK  Office: +44 (20) 7043 8269 int 8043> US  Office: +1 (212) 400 7686 int 8043> > > ---------------------------------------------------------------------> To unsubscribe from this list, please visit:> >     http://xircles.codehaus.org/manage_email> >
_________________________________________________________________
Making the world a better place one message at a time.
http://www.imtalkathon.com/?source=EML_WLH_Talkathon_BetterPlace
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email