[
https://issues.apache.org/jira/browse/WICKET-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Heider closed WICKET-1079.
----------------------------------
Resolution: Invalid
Fix Version/s: 1.3.0-beta4
Never mind. Sorry for creating a bogus issue. I think I was confused and
have worked it out.
> LoadableDetachableMode.toString calls super.toString which will result in
> stack overflow
> ----------------------------------------------------------------------------------------
>
> Key: WICKET-1079
> URL: https://issues.apache.org/jira/browse/WICKET-1079
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-beta4
> Environment: Windows/JDK 6
> Reporter: Timothy Heider
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.3.0-beta4
>
>
> When I turn on Wicket DEBUG LoadableDetachableModel.toString gets called. My
> object descending from this class does not define it, so this code crashes:
> public String toString()
> {
> StringBuffer sb = new StringBuffer(super.toString());
>
> sb.append(":attached=").append(attached).append(":tempModelObject=[").append(
> this.transientModelObject).append("]");
> return sb.toString();
> }
> super.toString is not defined, so it calls itself.
> Obvious workaround is to define toString in the object, but took some time to
> figure out.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
