In fact, I have a proxy issue.
The proxy of an attribute that didn't get retreive (it is wanted)
raise null pointer exception when corresponding accessor get called
instead of returning null.
Any idea to deal with that ?
On Jul 29, 2009, at 23:38 , Jean-Baptiste BRIAUD -- Novlog wrote:
Hi,
I'm facing an exception since I used fetch plan.
This is very strange, one accessor of my class return null when
using fetch plan and the correct value without using fetch plan.
(fetch plan, include that value)
More strange, when using fetch plan, in the debugger, the value look
like there, and if I call once (in evaluation in the debugger) the
accessor return the correct value.
The place where the value was shown null in the debugger doesn't
show it null anymore after that !
I'm guessing this is due to some enhancement (hook before/after)
that may cause that side effect but I don't know what to do.
I did try to use directly the field rather than the accessor, but it
doesn't change anything.
Another thing, this attribute come from an abstract super class.
All I did in my abstract superclasses was to use a @MappedSuperclass
annotation.
Is there something else to do with super class ?
I try to specify a @Inheritance(strategy =
InheritanceType.SINGLE_TABLE) but it fail when checking the
annotation far before the query.
All that happen during beanutils property description of instance of
my class, all accessors are called genericly by
PropertyUtils.describe(instance);
Could that be an issue ?
Thanks for your help !
