not serializable exception

Hello, After upgrading to wicket 6.21.0 I've get a strange serialization error when adding the debug bar to ajax target. I do this on every ajax event in development and it worked until today. The stacktrace extras: Caused by: java.lang.RuntimeException: An error occurred while getting the model

Re: not serializable exception

Hi, It seems to be caused by https://github.com/apache/wicket/commit/562d43ccdd7f305f8ca641817f4b63a07ee8b6a6 As the commit message says this container should be removed before the end of the request cycle, so it won't lead to such problem in the normal cases. But combined with the DebugBar it

Quetsion to nesting Forms and reflecting states of FormComponents after ajax refreshs

Hi Wicket Pros, I have a quite special case here and a question concerning nested form submits and FormComponent/Raw-Input Handling. This is my component tree: Page Form A DropDownChoice1 displaying selected 'Car 1' Form B

Event listeners not working after Javascript actions

I have a page with a Tabbed interface(not wicket) that performs actions before and after the domready signal. It has it's own signal for when it is complete: $( document ).on( "wb-ready.wb", function( event ) { //The page is fully loaded now. } The rendering order is like this: 1) Tab 1

Re: Event listeners not working after Javascript actions

Hi, On Thu, Nov 19, 2015 at 10:44 PM, EC James wrote: > I have a page with a Tabbed interface(not wicket) that performs actions > before and after the domready signal. > > It has it's own signal for when it is complete: > $( document ).on( "wb-ready.wb", function(

Re: Quetsion to nesting Forms and reflecting states of FormComponents after ajax refreshs

Hi Sven > so you have two components using the same model? Interesting. I didn't mentioned the details in my previous mail to reduce the description of the case. Yes, its a shared model, because Form B is contained in a dialog. And Form A comes from the Wizard (internal / needed for step

Re: Quetsion to nesting Forms and reflecting states of FormComponents after ajax refreshs

Hi Patrick, so you have two components using the same model? Interesting. Easiest solution would be to clear the rawInput on DropDownChoice1: choice1.clearInput(); If you don't have access to the dropDown from your submitting code, you might use component events to signal the car