Re: Form Processing problem on pages with Border - Wicket 1.4.1

2009-09-28 Thread Pedro Santos
onents > in the border, but can't that be an optional thing? > > In my onSubmit() method, I can always call > FormComponent.visitComponentsPostOrder(border, new > FormModelUpdateVisitor(this)); But with the way it is now, I have no way > to opt out of having my components updated.

Re: Form Processing problem on pages with Border - Wicket 1.4.1

2009-09-25 Thread Flavius
I can always call FormComponent.visitComponentsPostOrder(border, new FormModelUpdateVisitor(this)); But with the way it is now, I have no way to opt out of having my components updated. Is anybody else who uses borders having an issue like this? -- View this message in context: http://www.nab

Form Processing problem on pages with Border - Wicket 1.4.1

2009-09-24 Thread Flavius
I am migrating a project from 1.3.6 to 1.4.1. I've run into a problem and I'm not sure if this is a bug or not. Most of the pages have a border and the border has a DropDownChoice in it (as well as other components). Technically it's in a panel in the border. The Form objects are typically chil

Form Processing problem on pages with Border - Wicket 1.4.1

2009-09-23 Thread Flavius
I am migrating a project from 1.3.6 to 1.4.1. I've run into a problem and I'm not sure if this is a bug or not. Most of the pages have a border and the border has a DropDownChoice in it (as well as other components). Technically it's in a panel in the border. The Form objects are typically chil

Re: Form Processing problem on pages with Border - Wicket 1.4.1

2009-09-22 Thread Pedro Santos
I mean override the updateModel :P On Tue, Sep 22, 2009 at 11:03 AM, Pedro Santos wrote: > The internalUpdateFormComponentModels method in 1.3.6 didn't look for the > border and visit it's components. It's not obvious to me why this needs to > be done now in 1.4. > > The objective is to notify

Re: Form Processing problem on pages with Border - Wicket 1.4.1

2009-09-22 Thread Pedro Santos
The internalUpdateFormComponentModels method in 1.3.6 didn't look for the border and visit it's components. It's not obvious to me why this needs to be done now in 1.4. The objective is to notify form's event to generic containers... When the form is submitted, the DropDownChoice's value is bein

Form Processing problem on pages with Border - Wicket 1.4.1

2009-09-22 Thread Flavius
I am migrating a project from 1.3.6 to 1.4.1. I've run into a problem and I'm not sure if this is a bug or not. Most of the pages have a border and the border has a DropDownChoice in it (as well as other components). Technically it's in a panel in the border. The Form objects are typically chil

Form Processing problem on pages with Border - Wicket 1.4.1

2009-09-21 Thread Flavius
I am migrating a project from 1.3.6 to 1.4.1. I've run into a problem and I'm not sure if this is a bug or not. Most of the pages have a border and the border has a DropDownChoice in it (as well as other components). Technically it's in a panel in the border. The Form objects are typically chil

Form Processing problem on pages with Border - Wicket 1.4.1

2009-09-20 Thread Flavius
I am migrating a project from 1.3.6 to 1.4.1. I've run into a problem and I'm not sure if this is a bug or not. Most of the pages have a border and the border has a DropDownChoice in it (as well as other components). Technically it's in a panel in the border. The Form objects are typically chi