Hi,
On Fri, Jun 22, 2012 at 6:36 PM, Andrew Geery andrew.ge...@gmail.com wrote:
I've recently run across a couple of issues where a proxy'ed class (using
Javassist from Hibernate) has messed up Wicket. When a class is proxy'ed
by Javassist, the class you have (say, Person) isn't really a
I've recently run across a couple of issues where a proxy'ed class (using
Javassist from Hibernate) has messed up Wicket. When a class is proxy'ed
by Javassist, the class you have (say, Person) isn't really a Person class
but something like Person_$$_Javassist_48.
I had registered a converter
On Fri, 22 Jun 2012 11:36:51 -0400
Andrew Geery andrew.ge...@gmail.com wrote:
My question is: should Wicket have realized that the proxy'ed Person
object was actually a Person class and called the appropriate
converter? Looking at this --
