I changed the PagingToolbar to set the visibility at onConfigure to avoid early initialize the QueryResult. You can test on the next snapshot from now at http://oss.sonatype.org/content/repositories/snapshots/org/wicketstuff/inmethod-grid/1.4.15-SNAPSHOT/
On Tue, Dec 14, 2010 at 4:40 PM, Pedro Santos <[email protected]> wrote: > you can get the jar at: > http://repo1.maven.org/maven2/org/wicketstuff/inmethod-grid/1.4.14/ > > > On Tue, Dec 14, 2010 at 4:37 PM, Daniel Soneira <[email protected] > > wrote: > >> I'll try to put a quickstart together tomorrow. >> >> I'm not really using maven in my tool chain (ant guy) so I get the binary >> releases from here: >> >> http://wicketstuff.org/maven/repository/ >> >> >> On 14.12.2010 19:21, Pedro Santos wrote: >> >>> ops, I miss that, can u send a quickstart? The last version is 1.4.14, >>> you >>> can use >>> >>> <dependency> >>> <groupId>org.wicketstuff</groupId> >>> <artifactId>inmethod-grid</artifactId> >>> <version>1.4.14</version> >>> </dependency> >>> >>> >>> >>> On Tue, Dec 14, 2010 at 4:12 PM, Daniel Soneira >>> <[email protected]>wrote: >>> >>> PagingToolbar is not my code. >>>> It's a class of inmethod-grid (wicketstuff project). So I have no >>>> influence >>>> on that. That's what I would do if it _was_ my code though ;) >>>> Maybe inmethod-grid adapts the new onConfigure / onInitialize methods. >>>> I'm >>>> currently using 1.4.1 which I _think_ is the latest official release. >>>> >>>> >>>> On 14.12.2010 18:52, Pedro Santos wrote: >>>> >>>> use the onConfigure to set the paging-toolbar >>>>> >>>>> onConfigure(){ >>>>> setVisible( getDataGrid().getTotalRowCount() != 0); >>>>> } >>>>> >>>>> On Tue, Dec 14, 2010 at 3:39 PM, Daniel Soneira >>>>> <[email protected]>wrote: >>>>> >>>>> Hi there, >>>>> >>>>>> In the private method Form#isMultiPart the visitor algorithm does not >>>>>> check >>>>>> for components that implement IFormVisitorParticipant. >>>>>> >>>>>> Here is my use case (I've been debugging quite some time to find the >>>>>> source >>>>>> of recent problems I've encountered): >>>>>> >>>>>> Within a form I have a nested In-Method PagingNavigator (with a >>>>>> read-only >>>>>> text field) that returns FALSE for >>>>>> IFormVisitorParticipant#processChildren. >>>>>> Also the grid uses some filtering criteria that the user can change >>>>>> (some >>>>>> text fields - also children of the form). >>>>>> >>>>>> Hierarchy: >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------------------ >>>>>> form >>>>>> -- filter >>>>>> -- criteria-1...x >>>>>> -- grid >>>>>> -- paging-toolbar >>>>>> -- paging-navigator [IFormVisitorParticipant -> >>>>>> processChildren() >>>>>> returns false] >>>>>> -- text-field >>>>>> -- search-button >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------------------ >>>>>> When the form is submitted (via SEARCH button) the following happens: >>>>>> >>>>>> Form#isMultiPart() tries to determine if that text field is visible in >>>>>> the >>>>>> hierarchy; which at some time (through recursion) asks the toolbar. >>>>>> The >>>>>> paging-toolbar contains the following code: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------------------ >>>>>> @Override >>>>>> public boolean isVisible() { >>>>>> return getDataGrid().getTotalRowCount() != 0; >>>>>> } >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------------------ >>>>>> This queries the data provider which at that point can not use the >>>>>> current >>>>>> filtering criteria - because they are not submitted yet. Therefore the >>>>>> results in the grid are wrong. >>>>>> The text field is ignored for validation / updating of the model. That >>>>>> works as expected. >>>>>> In my option the text-field should not be visited at all since its >>>>>> parent >>>>>> (navigator) specifies otherwise. >>>>>> >>>>>> Note, that prior to wicket 1.4.12 I didn't have this problem (I was >>>>>> using >>>>>> 1.4.10 before where there is no check for visibleInHierarchy in >>>>>> Form#isMultiPart). >>>>>> I've looked at the source code of Form#isMultiPart in 1.4.14 and >>>>>> 1.5.M3 >>>>>> and >>>>>> both seem to be the same. >>>>>> >>>>>> Should I create a JIRA issue for that (I think it's a bug) or is there >>>>>> an >>>>>> easy workaround that I miss? >>>>>> >>>>>> Kind regards, >>>>>> Daniel Soneira >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> 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] >> >> > > > -- > Pedro Henrique Oliveira dos Santos > -- Pedro Henrique Oliveira dos Santos
