Mhh, this approach is giving me a headache. Sometimes the inner
formcomponent models are not wrapped around the outer formcomponent
compound model returned by the overridden getModel(), but directly
around the parent model instead (which is also a compound one). It's
as if the model is accessed dir
I worked out this easier and cleanse way to wrap the model of the
outer component:
public DateComponent(String id) {
this(id, null);
}
public DateComponent(String id, IModel model) {
super(id, model);
}
public IModel getModel() {
return new CompoundProp
looks good without actually running the code :)
-igor
On 4/9/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
Well, here is what I've done based on your suggestions. Please review
this and tell me if it can be improved, if you are so kind:
1) An inherited model that looks into the passed model. I
Well, here is what I've done based on your suggestions. Please review
this and tell me if it can be improved, if you are so kind:
1) An inherited model that looks into the passed model. If it's not
null it returns a propertymodel for the component id a la
CompoundPropertyModel. If it's null it re
maybe have FormComponentFeedbackBorders for the individual
components and then a global feedback panel to catch the general
ones (install a filter to ignore reporters that have feedback borders)
Carlos Pita-4 wrote:
>
> Hi all,
>
> suppose you have to implement some form input component that
On 4/9/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
1) How can I use a compound property model without naming the nested
form components with their full path (ie. 'birthDate.year' instead of
simply 'year').
use the model luke
what is below is some pseudocode, it is not the best way to do this
> 1) How can I use a compound property model without naming the nested
> form components with their full path (ie. 'birthDate.year' instead of
> simply 'year').
>
> 2) If I add a validator to the form component panel (for panel level
> validation), can I assume that the nested component models will
Hi Eelco,
I've looked at the examples. There are a couple of things that still
troubles me:
1) How can I use a compound property model without naming the nested
form components with their full path (ie. 'birthDate.year' instead of
simply 'year').
2) If I add a validator to the form component pan
When nested form is submitted, the form components in surrounding
models are given the user input, but they are not processed. So the
input is "persisted" during request, but not validated and processed.
The inner (nested) form, that is submitted is both validated and if
validation succeeds, the mo
> > as a formcomponent itself. and actually wicket does support embedded forms.
>
> Can you expand on this? Will nested forms be validated and bound
> before their containers?
Look at wicket.examples.forminput.Multiply and
wicket.extensions.yui.calendar.(Date)TimeField for examples.
Eelco
--
> there is a FormComponentPanel that can embed other form components, and act
Great! Btw, is there something more like a border or fragment, to
"inline" the markup?
> as a formcomponent itself. and actually wicket does support embedded forms.
Can you expand on this? Will nested forms be validate
there is a FormComponentPanel that can embed other form components, and act
as a formcomponent itself. and actually wicket does support embedded forms.
-igor
On 4/9/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
Hi all,
suppose you have to implement some form input component that is
composed fro
12 matches
Mail list logo
