On Thu, 12 Jun 2008, David Nedrow wrote: > Couldn't resolve model type of > Model:classname=[org.apache.wicket.model.CompoundPropertyModel > $ > AttachedCompoundPropertyModel > ]:nestedModel > = > [Model:classname > =[org.apache.wicket.model.CompoundPropertyModel]:nestedModel=[username > = "regular"]] for [MarkupContainer [Component id = password, page = > com.vzbi.ncs.argfrp.webapp.FilterRequest.app.LoginPage, path = > 0:signInPanel:signInForm:password.PasswordTextField, isVisible = true, > isVersioned = false]], please set the type yourself. > > Not setting the model does not seem to create a problem, but it would > seem that the system would prefer that models be set where applicable.
I think that the problem is not actually the lack of model, but that Wicket cannot figure out to what type of object the model of the formcomponent is supposed to contain. Calling passwordField.setType(TypeOfMyPasswordObject.class) might help. The type can also be supplied in the constructor. > Is that the case? I have to admit, I'm a little anal about clearing > all warnings in my apps. I know the feeling :) Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations Oy <URL: http://www.ri.fi/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
