there is no specific designed solution for that no.
you could also override component.initModel() for that
On Fri, Mar 14, 2008 at 11:34 AM, Vitaly Tsaplin <[EMAIL PROTECTED]>
wrote:
> Many thanks Johan,
>
> I am just going to explain why I need it. Lets say we have a
> component which accepts one or some models as a parameter(s). So it
> can apply initial values to its internal component hierarchy. But in
> case of use the CompoundPropertyModel we have no chance to do such
> preparations in a constructor. Probably you would suggest a better way
> to do it? Is there any specifically designed solution to fit this
> situation?
>
> Vitaly
>
> On Fri, Mar 14, 2008 at 10:39 AM, Johan Compagner <[EMAIL PROTECTED]>
> wrote:
> > override this method:
> >
> >
> > /**
> >
> > * [EMAIL PROTECTED]
> org.apache.wicket.model.IComponentAssignedModel#wrapOnAssignment(
> > org.apache.wicket.Component)
> >
> > */
> >
> > *public* IWrapModel wrapOnAssignment(*final* Component component)
> >
> > {
> >
> > *return* *new* AssignmentWrapper(component, propertyName);
> >
> > }
> >
> >
> > On Thu, Mar 13, 2008 at 3:32 PM, Vitaly Tsaplin <
> [EMAIL PROTECTED]>
> > wrote:
> >
> >
> >
> > > Hi everyone,
> > >
> > > Is there any way to be notified somehow just after the
> > > CompoundPropertyModel is resolved by the component hierarchy?
> > >
> > > Vitaly
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
