Re: 1.3, resource locator and properties

Scott, I am no core developer, but I think that creating a issue (preferably with a patch) would be the fastest way to success. Regards, Erik. Scott Swank wrote: Bump. Do any devs have an opinion on this? Should I create a jira instead of asking this on the list? Here is a quick

Re: 1.3, resource locator and properties

Bump. Do any devs have an opinion on this? Should I create a jira instead of asking this on the list? Here is a quick summary so that no one needs to read through the thread: 1. The ResourceNameIterator encapsulates the style/variation/localization strategy 2. The ResourceStreamLocator uses it

Re: 1.3, resource locator and properties

It seems that the problem is that the ComponentStringResourceLoader does not handle the MyApplication.properties (never mind what its javadoc says). Instead the ClassStringResourceLoader does. It is registered in the Settings constructor. The ClassSRL ultimately delegates to super return

Re: 1.3, resource locator and properties

Would a patch be useful for evaluating this? Essentially I'm talking about 1) adding get/setResourceNameIterator to IResourceSettings Settings 2) calling Application.get().getResourceSettings().getResourceNameIterator() from ResourceStreamLocator and ComponentStringResourceLocator - Scott On

Re: 1.3, resource locator and properties

I have subclassed ComponentStringResourceLoader so that I can drive it from a custom ResourceNameIterator (in particular to look in the right directories). In particular, I just overrode public String loadStringResource(Class clazz, final String key, final Locale locale, final String style)

Re: 1.3, resource locator and properties

Can someone at least verify that my e-mail is getting through to the Wicket list? :) On Wed, Apr 16, 2008 at 11:34 AM, Scott Swank [EMAIL PROTECTED] wrote: I have subclassed ComponentStringResourceLoader so that I can drive it from a custom ResourceNameIterator (in particular to look in the

Re: 1.3, resource locator and properties

Hi Scott Could you provide a quickstart? I have some time tomorrow... Scott Swank wrote: I have subclassed ComponentStringResourceLoader so that I can drive it from a custom ResourceNameIterator (in particular to look in the right directories). In particular, I just overrode public String

Re: 1.3, resource locator and properties

Thank you Nino. I'll send the quickstart directly to you since the list doesn't allow attachments. I'm extracting everything from our sandbox app that you're not interested in. I do have the behavior reproduced there. - Scott On Wed, Apr 16, 2008 at 1:02 PM, Nino Saturnino Martinez Vazquez

1.3, resource locator and properties

We are finally upgrading to Wicket 1.3 (in particular to 1.3.3 from 1.2.6) and our StringResourceModels can no longer find their property files, which leaves our web pages containing the following: [Warning: String resource for 'tickets' not found] Our application init method contains:

Re: 1.3, resource locator and properties

Previously we retrieved the CompoundResourceStreamLocator and added our ResourceStreamLocator to it. In 1.2 did this take care of StringResourceLoader too? WebApplicationPath resourceFinder = (WebApplicationPath) getResourceSettings().getResourceFinder();