Am 02.10.2012 08:48, schrieb Martin Grigorov:
Hi,
On Mon, Oct 1, 2012 at 7:05 PM, Michael Mosmann <mich...@mosmann.de> wrote:
I have no specific problem, more a general...
I think most time a model access uses only getObject(). Throwing exceptions on
setObject in AbstractReadOnlyModel could be avoided with the right interface is
there. An in between of my last refactoring i could see that (to this point)
nothing violated the intention. The right interface would prove this...
I would like to see in method signatures or c-tor params that a component does
not change a model value.
I hope i could explain my intention good enough:)
Which methods in Wicket APIs will use IReadableModel/IWriteableModel
instead of IModel ?
Label is a perfect candidate, AbstractReadOnlyModel could have the right
interface...
.. in my second refactoring attempt i got some overloading with generics
trouble, so i will try it again with smaller steps but with
IWriteableModel..
mm:)
