Yeah, the properties file aren’t in the application’s package. It would be handy if Localizer just used a Class instead of a Component. However, your info was enough of a push to get me where I needed (in combination with ConvertingPropertyVariableInterpolator).
Thanks! -Lon On Wed, Oct 5, 2016 at 7:38 PM, Martin Grigorov <martin.grigo...@gmail.com> wrote: > Hi, > > The component could be null. In this case it will fallback to > YourApplication.properties. > I guess this won't work for you too. > > Why don't you just use ResourceBundle? > > On Oct 6, 2016 5:29 AM, "Lon Varscsak" <lon.varsc...@gmail.com> wrote: > > > Hey all, > > > > How can I get a localized string (from a properties file) inside of a > > library I have without the use of a Component. I have a controller class > > (nothing to do with components), but I’d like to have this class (In a > > non-application jar) return an error message to the application localized > > (with dynamic values), but I can’t see how to do it. Localizer only > allows > > passing in a component (and not just any class). > > > > Ideas? > > > > Thanks! > > > > -Lon > > >
