have you put the "immediate" attribute on the link? regards,
Martin On Thu, 27 Jan 2005 16:18:06 +0100, Werner Punz <[EMAIL PROTECTED]> wrote: > Hi, I have a weird problem, where I dont know what the cause is. > Following Situation, I am trying to do a search form with a result > data table within one page. > > What I am doing, is that the search basically is performed via a custom > Data model (which works quite nicely) > The Query is done via a custom query bean which indirectly has a session > scope (I have a history cache with session scope) > > What happens is following, the search form should pass the search > parameters to the query bean, the data model of the table should call > the bean and pass the filtered results back to the table view. > > Well that works sort of, the problem and I dont have any clue why this > happens is, that I have to start everything twice until the parameters > are passed down the query objects and the query is performed. > > It seems to me that the order is following: > a enter the query params manually, trigger a submit, render the page, > fill the form parameters into the query bean.... > Which is kindof weird and does not make sense. > > The query bean accessors are standard setter and getters and > the query is basically started by pressing a command link which itself > triggers a method. > > I must be missing something here, it seems to me the method is called > before the query params are passed into the bean and it definitely is > called before the page is rerendered. > > Did anybody already encounter this weird problem? > >
