It works with the classloader of the current thread, so that's OK. And yes, I was surprised to find a non-optional initialization like that of the PropertyResolver to be defined in an Initializer that might not always be called. So 100% correct to move that to an internalInit.
Jan. -- View this message in context: http://www.nabble.com/NPE-in-PropertyResolver.getGetAndSetter%28%29-tf3946346.html#a11212249 Sent from the Wicket - Dev mailing list archive at Nabble.com.
