Jan, can you also test this patch and see if that works for you in OSGI?
https://issues.apache.org/jira/browse/WICKET-1371 johan On Tue, Jun 19, 2007 at 2:13 PM, Jan Vermeulen <[EMAIL PROTECTED]> wrote: > > After downloading the last changes in Wicket 1.3 TRUNK, we have a NPE in > PropertyResolver, due to the fact that there is no HashMap for the current > application. That's because the init(Application) is never called. > > Debugging the problem, we found that the wicket.properties resource file > where the Initializer is registered is not correctly loaded: > > // Load properties files used by all libraries > final Enumeration resources = > getClass().getClassLoader().getResources( > "wicket.properties"); > while (resources.hasMoreElements()) > {... > > In the code above (Application.initializeComponents()), the enum does not > seem to have any elements, although we see that the resource file is > available, and this code has not been changed lately. > > So what is happening here ? > > Jan. > -- > View this message in context: > http://www.nabble.com/NPE-in-PropertyResolver.getGetAndSetter%28%29-tf3946346.html#a11194510 > Sent from the Wicket - Dev mailing list archive at > Nabble.com<http://nabble.com/> > . > >
