Igor Vaynberg <mailto:[EMAIL PROTECTED]> wrote: > On Thu, Oct 30, 2008 at 5:13 AM, Kai Mütz <[EMAIL PROTECTED]> > wrote: >> package-level properties sounds good. This is what I am looking for >> currently. Is there a plan to port PackageStringResourceLoader to >> 1.3.x branch? > > no plan so far. this is a new feature and we dont generally roll new > features into a maintenance release. > >> If not, what is the best way to provide properties for multiple >> Pages/WebResources in 1.3.x if I do not want to put them into >> application.properties? > > there is no way to do that in core. you can take my mods from above > commit and build a new istringresourceloader and add it to your > application.
Ok, I have added a PackageStringResourceLoader to my application and it works for WebPages. Thanks. Now I want to use those resources within a DynamicWebResource via Localizer which seems to be impossible because Localizer.getString() requires a component. Is there another way to implement internationalized webresource? Regards, Kai --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
