Not sure about the best solution, but we use:
public static Class checkForCGLIB(Class type)
{
if (type.getName().contains("CGLIB"))
{
return type.getSuperclass();
} else return type;
}
Kalle
On 8/29/07, Jan Vissers <[EMAIL PROTECTED]> wrote:
>
> Pro
BeanPropertySelectionModel cleared up my
problems.
JB
> -Original Message-
> From: Jan Vissers [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 29, 2007 5:54 AM
> To: Marcus Schulte
> Cc: Tapestry users
> Subject: Re: T4.1.2 / Spring 2.0.6 / Hib3 Lazy loading and
> Propert
Problem indeed has to do with the 'equality' check that is performed...
In there a class check likeif( obj instanceof MyClass ) is done, but
obj is a CGLIB enhanced instance, which yields to an unequal class.
What is the best solution to solve this?
-J.
Marcus Schulte wrote:
One thing to b
One thing to be aware of is that the same db-row, in two different
Hibernate-Session, corresponds to two different objects. So with
session-per-request, if your PSModel is loaded in one request, and your
value-parameter-object in another. If you don't override
Object.equalsappropriately, Tapestry c
Hi,
I'm witnessing some 'interesting' behavior, using lazily loaded
collections (Hibernate) combined with PropertySelectionModel stuff. Before
getting into too much detail - using my JUnit tests I can prove that
traversing the (nested) objectgraph actually has the information (albeit
via CGLIB pro
