The javadoc pretty clearly says that this is "useful for debugging and so on...". What lead you to believe this would always return a user-readable string?
Thomas > -----Original Message----- > From: Chris Lintz [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 17. Oktober 2007 10:29 > To: [email protected] > Subject: StringResourceModel toString() changed in Beta4 - > why??? Must use getString() now. > > > Hi all, > I swapped beta3 for beta4 and to my surprise all of my > StringResourceModels that have worked (even back to 1.2) > suddenly dont work. The toString() call no longer returns > the resource String. I dont see this in the release notes so > to say the least, this was a very frustrating find. > > For example, this use to work: > > public String getPageTitle() > { > return new StringResourceModel("page.title", this, new > Model(this)).toString(); } > > Now I have to say: > > public String getPageTitle() > { > StringResourceModel("page.title", this, new > Model(this)).getString(); } > > A subtle change that that took some time to finally track > down... Why did this change? I believe the toString() is > referenced in many docs. > > > chris > > -- > View this message in context: > http://www.nabble.com/StringResourceModel-toString%28%29-chang > ed-in-Beta4---why-----Must-use-getString%28%29-now.-tf4638851. > html#a13249098 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
