SV: StringResourceModels doesn't seem to detach properly

2012-01-04 Thread Einar Bjerve
: Martin Grigorov [mailto:mgrigo...@apache.org] Sendt: 3. januar 2012 16:36 Til: users@wicket.apache.org Emne: Re: StringResourceModels doesn't seem to detach properly Hi, It is intended. IModel#detach() is called only if this model is assigned to a component. Since no one calls #detach

Re: StringResourceModels doesn't seem to detach properly

2012-01-04 Thread Martin Grigorov
...@apache.org] Sendt: 3. januar 2012 16:36 Til: users@wicket.apache.org Emne: Re: StringResourceModels doesn't seem to detach properly Hi, It is intended. IModel#detach() is called only if this model is assigned to a component. Since no one calls #detach() on the StringResourceModel it has

Re: StringResourceModels doesn't seem to detach properly

2012-01-04 Thread Einar Bjerve
it was consistent, in 1.5 it isn't. Best regards Einar Bjerve -Opprinnelig melding- Fra: Martin Grigorov [mailto:mgrigo...@apache.org] Sendt: 3. januar 2012 16:36 Til: users@wicket.apache.org Emne: Re: StringResourceModels doesn't seem to detach properly Hi, It is intended

StringResourceModels doesn't seem to detach properly

2012-01-03 Thread Einar Bjerve
If a StringResourceModel contains a model for property substitutions, and there has not been assigned a component it is relative to on construction time, it will not detach the property substitution model. If there is assigned a component on construction time, the property substitution model

Re: StringResourceModels doesn't seem to detach properly

2012-01-03 Thread Martin Grigorov
Hi, It is intended. IModel#detach() is called only if this model is assigned to a component. Since no one calls #detach() on the StringResourceModel it has no idea when to call detach() on its inner model. You need to call SRM.detach() in #onDetach() in the component where it is used. Then it