[ANNOUNCE] WicketStuff 6.22.0 is released

Hi, WicketStuff core 6.22.0 based on Apache Wicket 6.22.0 is released and available at Maven Central. The changelog since 6.21.0 is: Martin Tzvetanov Grigorov (5): [build] Use Wicket 6.22.0-SNAPSHOT [fast2] Update fast serializer to 2.43 WICKET-6091 NPE in RequestLoggerRequestC

[ANNOUNCE] Wicket 6.22.0 released

The Apache Wicket PMC is proud to announce Apache Wicket 6.22.0! This release marks another minor release of Wicket 6. We use semantic versioning for the development of Wicket, and as such no API breaks are present breaks are present in this release compared to 6.0.0. Using this release -

[ANNOUNCE] Wicket 7.2.0 released

The Apache Wicket PMC is proud to announce Apache Wicket 7.2.0! This release marks another minor release of Wicket 7. We use semantic versioning for the development of Wicket, and as such no API breaks are present breaks are present in this release compared to 7.0.0. Using this release --

[ANNOUNCE] Apache Wicket 7.2.0 released

The Apache Wicket PMC is proud to announce Apache Wicket 7.2.0! This release marks another minor release of Wicket 7. We use semantic versioning for the development of Wicket, and as such no API breaks are present breaks are present in this release compared to 7.0.0. Using this release --

Re: Wicket model problem

It's hard to give specifics as the form is very complex. I do have a general example of a pattern prevalent throughout the form. The pseudo code goes something like this: // Page class MyPage extends Page { onInitialize() { Panel p = PanelFactory.createPanel("myPanel", "myObject");

Re: Wicket model problem

Hi! Perhaps this is stating the obvious since it looks like you know what you are doing, but just to be sure: Does your LoadableDetachableExpressionModel call detach on its “parent” model? This is the most frequently occurring source of model leaks I have seen. Since the last model in the chain

Re: Wicket model problem

Thanks for the reply. I suspect this is exactly the case we have created for ourselves. Although we have a good grasp on the detach process I suspect that there are places where this rule of thumb is not being followed. Although the example I gave is somewhat fictitious, any of the LDMs we have

Re: Wicket model problem

Hi, I think the only way to track this is with custom code (or with aspects for example). Since the contract of IModel only has detach() (and not isDetached()), this cannot be tracked easily. What I would do in such a case is probably to add a requestcyclelistener which walks a page after a r

Re: Wicket model problem

see the LoadableDetachableModel # isAttached() method which return the attached status of this model instance François Le 19 févr. 2016 à 16:47, Bas Gooren a écrit : > Hi, > > I think the only way to track this is with custom code (or with aspects for > example). > > Since the cont

Re: Wicketstuff editable grid - 7.1.0

My mistake about the inmethod grid dependency. I don't know why I saw compilation error in editable grid class when removed inmethod grid jar from classpath. For debugging the respond method as your suggestion, I do see correct class types for each rowItem (as attachment). But it fails with follow

Re: Wicketstuff editable grid - 7.1.0

Just realized that last two lines could be confusing: the decisionCode is the property of class PcaCodes in pcapanel, but showing up for exccodepanel row item. On Fri, Feb 19, 2016 at 12:06 PM, Mihir Chhaya wrote: > My mistake about the inmethod grid dependency. I don't know why I saw > compilat

Re: Wicket model problem

You can also use a IDetachListener to check that no one LDM (field) is attached after the page#detach() has been called. In the Application#init() you can add getFrameworkSettings().setDetachListener( new IDetachListener() { @Override public void on

Re: Wicketstuff editable grid - 7.1.0

Ok, so creating a small project with two panels(Person and Customer) and a page for similar use case resulted in following stacktrace. The panels are added in the order of PersonPanel, CustomerPanel in the parent page. The line# 163 in onSave method of EditableGrid is calling EditableGrid.this.onS

Quesitont about .repeater.DataTableFilterToolbarPage : mutliple fitered

Hello, The repeater.DataTableFilterToolpage demonstrates a unique filter. My questions are : - I