Not sure what you're getting at. IModel is sort of hungarian notation: Interface for Model. Not idiosyncratic. Read the definition of Idiosyncratic Interfaces:
"If a general interface is implemented by only one class (whose implementation may be modified over time, but with no two alternatives occurring in the same project), we call this interface idiosyncratic." The corollary is when multiple implementations exist of one interface, it is a Family Interface or general interface according to [1]. Just because one article suggests that all things named IFoo are idiosyncratic, doesn't mean it is the truth... Martijn [1] http://www.jot.fm/issues/issue_2005_07/article1/ On Tue, Jun 21, 2011 at 10:08 AM, IO <niezus...@googlemail.com> wrote: > Hi, in Wicket there are many idiosyncratic interfaces, such as IModel <T>. I > often see that these interfaces are implemented several times in a project. > An idiosyncratic interface should be implemented only once in a project. Can > someone explain that to me? > > IO. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/idiosyncratic-interfaces-such-as-IModel-IVisitor-tp3613440p3613440.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
