Hi David,
I'm not able to tell you the intention of the PropertyModel.
My guess for coding to your spec in 1.3 would be:
IModel languageModel = new AbstractReadOnlyModel() {
@Override
public Object getObject() {
return getSession().getLocale().getLanguage(); }
};
in your special case you probably could do this too:
IModel languageModel = new PropertyModel(this,
"session.locale.language")));
But than your 'readonly' intention might be not that clear.
martin
2008/2/13, David Leangen <[EMAIL PROTECTED]>:
>
>
> Hello!
>
> I'm (finally!) migrating to 1.3, so have a few wrinkles to iron out.
>
> Is somebody able to tell me the intention of the PropertyModel? I'm
> wondering if something has changed, or if I just wasn't using it
> correctly before...
>
>
> In one of my panels, I use this type of property:
>
> PropertyModel languageModel = new PropertyModel( this, "language" );
>
> And in the same class, I have a getter like this:
>
> public String getLanguage()
> {
> return getSession().getLocale().getLanguage();
> }
>
> There is no setter and no "language" property.
>
>
>
> This used to work in 1.2.6, but now 1.3.1 complains that there is no
> setter for this class.
>
> Now, I don't even _want_ a setter, but just to see what happens, I add
> in a dummy setter, but wicket still complains that it can't find a
> "language" property.
>
>
> Am I not using the PropertyModel correctly (i.e. according to what
> PropertyModel is intended for)? (If so, this means that I've been using
> it incorrectly for many months without noticing, since it used to work.)
>
> Or, should I be using some other type of model for this?
>
>
> Thanx!
> Dave
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
