Actually, if I get the resource file (wicket.properties) out of the wicket jar, and put it direclty in the classpath of the web application, then it is correctly loaded and processed.
So it's a classloader problem with OSGI. Jan. -- View this message in context: http://www.nabble.com/NPE-in-PropertyResolver.getGetAndSetter%28%29-tf3946346.html#a11199816 Sent from the Wicket - Dev mailing list archive at Nabble.com.
