Re: TextField updated via AJAX not sent in form?

2016-01-27 Thread Viktor Micskó
Hi, Thank you, this was the reason indeed. Just for the archive: forms in tables seem to work fine as long as you don't update form fields via AJAX, but Labels are updated correctly. Kind Regards, Viktor Micsko On Wed, Jan 27, 2016 at 9:33 AM, Thomas Matthijs wrote: > >

Re: TextField updated via AJAX not sent in form?

2016-01-27 Thread Martin Grigorov
Hi, Wicket behaves the same way in both cases. It is just that the browser doesn't send request parameter for "price" when the HTML is invalid. That's why it is null at the server side. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jan 27, 2016 at 11:13

TextField updated via AJAX not sent in form?

2016-01-27 Thread Viktor Micskó
Hi, I found an interesting behavior, which finally I avoided in this project due to changing requirements, but it still bothers me, so I thought I'd ask anyways, perhaps I'm missing something trivial. The basic idea is that there is list of sales data in a table (think of it like a sales

[ANNOUNCE] WicketStuff 7.2.0 Released

2016-01-27 Thread Martin Grigorov
WicketStuff core 7.2.0 based on Apache Wicket 7.2.0 is released and available at Maven Central. The changelog since 7.1.0 is: Martin Tzvetanov Grigorov (40): Bump version to 7.2.0-SNAPSHOT Bump version of sub-modules to 7.2.0-SNAPSHOT [select2] Use proper JS and CSS

Re: Wicket Presentation

2016-01-27 Thread Martijn Dashorst
I'm still considering it. Unfortunately it falls right in a very busy period for me. What kind of presentation would you like to go to? What kind of subjects should be covered? Martijn On Tue, Jan 26, 2016 at 7:20 PM, Jered Myers wrote: > Is anybody planning any

Re: TextField updated via AJAX not sent in form?

2016-01-27 Thread Thomas Matthijs
> o) I also found that this only happens when the markup looks like this, > i.e. the form is inside the table (See HomePage.html): > > > >... > > > > ...but not when the form is outside (see WorkingPage.html) > > > >... > > > > The first markup would be preferred so that