In my specific case it is Wicket 1.3, AbstractDetachableModel, setObject();
but I image it would apply in other cases as well.
Does anyone else see any value to making this small change to the exception
message?
Currently:
throw new WicketRuntimeException(unable to set object + object + ,
easiest way is to create a jira issue
-igor
On 2/23/07, ChuckDeal [EMAIL PROTECTED] wrote:
In my specific case it is Wicket 1.3, AbstractDetachableModel,
setObject();
but I image it would apply in other cases as well.
Does anyone else see any value to making this small change to the
