Yup, that's exactly the issue I had. It's not hard to fix in user code. The hard part is to find the occurrences of the issue in the code.
On Wed, May 13, 2015 at 8:05 AM, Martin Grigorov <[email protected]> wrote: > https://issues.apache.org/jira/browse/WICKET-5906 sounds related. > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, May 11, 2015 at 11:26 PM, Guillaume Smet <[email protected] > > > wrote: > > > Hi, > > > > Still working on the migration to 7. > > > > We used this pattern with Wicket 6: > > new StringResourceModel(propertyModel.getObject(), null, > > propertyModel.getObject(), objectModel, secondaryObjectModel)) > > which was directed to the following constructor: > > StringResourceModel(key, model, defaultValue, Object... parameters) > > > > When migrating to 7, this pattern is silently directed to the following > > constructor: > > StringResourceModel(key, model, Object... parameters) > > thus the replacements are wrong. > > > > The fact that our application is silently broken is kinda annoying. > > > > I ended up moving to: > > new StringResourceModel(propertyModel.getObject(), (IModel<?>) null, > > propertyModel, new Object[] { objectModel, secondaryObjectModel })) > > > > I don't know if there is something to do about it but I thought I might > as > > well get it out here. > > > > -- > > Guillaume > > >
