I meant to also mention that while other pages in the app use this panel and
do NOT have this problem, those other pages do not have an extension of that
class. I know some annotations do not inherit, but again, the lookupService
is loaded at first.
Entropy wrote
Form and button works fine
I tried marking the properties as transient, which got me past that error,
but then the properties are null after the validation and that is not really
better. :(
Entropy wrote
Form and button works fine without my validator (sounds similar to my last
message but this is the next problem).
LookupService is probably coming from another class loader than the
Wicket classes.
Any particular reason, why you're using Wicket 1.4.x?
The code to resolve the class on deserialization has been improved with
Wicket 1.5.x to use the current thread's context class loader.
Regards
Sven
On
On Wed, Mar 27, 2013 at 4:55 PM, Sven Meier [via Apache Wicket]
ml-node+s1842946n4657592...@n4.nabble.com wrote:
LookupService is probably coming from another class loader than the
Wicket classes.
I'm not sure why that would be. All our pages are launched from the
same menu, my new one
