I also read documentation - it may have been on the Pro Wicket book.. I dont recall. Nonetheless I thought it was strange to also reley on toString().. but seeing documentation and examples of toString() pushed me into using it without much thought. And like I said this worked all the way back to Wicket 1.2 . I dont care what it is.. I'll refactor to getString(). It would just be nice to know ahead of time whats coming.
Jan Kriesten wrote: > > > Hi Thomas, > >> Fair enough, was I reading more importance into the second sentence >> (useful for debugging...). I still would not rely on toString() for >> anything but debugging purposes unless someone passes me an object of a >> well known, final class > > right - but there are exceptions to rules. :-) > > In my case, the documentation for IChoiceRenderer.getIdValue() explicitely > suggest using toString(). > > Anyway, clearifcation of the API or a return to the old behavior is > needed: > > https://issues.apache.org/jira/browse/WICKET-1080 > > Regards, --- Jan. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/StringResourceModel-toString%28%29-changed-in-Beta4---why-----Must-use-getString%28%29-now.-tf4638851.html#a13255680 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
