I've scanned other models as well, and will apply this to AbstractPropertyModel too.
I also included/created a unit test for this issue. See http://issues.apache.org/jira/browse/WICKET-621 Martijn On 6/6/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
All, I'm not sure the usecase is general, but in our application we have a couple of classes that implement IDetachable, but not IModel, and these are put into a CompoundPropertyModel The thing is that the CompoundPropertyModel does an instanceof check for IModel instead of the slightly more general IDetachable. Are there any objections to changing that check to IDetachable instead of IModel? Martijn -- Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org
-- Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org
