StringResourceModel interpolation in resource key is broken

Having:

new StringResourceModel("details.disabled.${disabled}", this.model)

... and isDisabled returns a boolean naturally.

In Wicket 1.5, the StringResourceModel now does some heavier processing on the key, thus the boolean value is converted first using the registered converter and then inserted into the resource key; resulting in keys like "details.disabled.yes" or "details.disabled.ja" etc which are even language dependent!