It's worse than I thought: I turned back the upgrade, and it seems it didn't enter in the old code neither. So the NPE is a consequence of something that went wrong before already (although we never noticed). Seems we never got to the Initializer, but we never noticed, since it only explicitly registered interfaces that register themselves implicitly.
We're running with in Equinox OSGI platform, and the implementation of the Enumeration returned by the classloader is a 'sun.misc.CompoundEnumeration'. It seems to have loaded the propertyFile, because it is visible within the enumeration instance, but the hasNextElement() returns 'false'. Someone has had any problems with loading resources in OSGI ? Jan. -- View this message in context: http://www.nabble.com/NPE-in-PropertyResolver.getGetAndSetter%28%29-tf3946346.html#a11196540 Sent from the Wicket - Dev mailing list archive at Nabble.com.
