FYI,
I created similar functionality of CGLIBs "fast reflection" for our AOP
framework and it had an unnoticeable affect on the performance of the
framework. This was with Sun JDK 1.4.1_02 on Linux. Considering that
Hibernate's overhead is probably a lot higher, I don't think it will
have an
It has meaning for trivial methods "getters/setters" or "empty" constuctors.
I am not sure, but looks like Sun JDK 1.4.1_02 generates code to optimize
native method invokation too.
- Original Message -
From: "Bill Burke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 2
Bill Burke wrote:
> I created similar functionality of CGLIBs "fast reflection" for our AOP
> framework and it had an unnoticeable affect on the performance of the
> framework. This was with Sun JDK 1.4.1_02 on Linux. Considering that
> Hibernate's overhead is probably a lot higher, I don't think
p.s. the BulkBean class also now throws an exception detailing which
property failed, so you can print a better error message.
Hooray! You have no idea how much forum posts this will save us
---
This sf.net email is sponsored by:ThinkG
It is possible to find problem outside generated code for optimization:
setValues(bean,values);
}catch( NullPointerException npe){
for( int i = 0; i < propertyCount; i++ ){
if( types[i].isPrimityve() && values[i] == null ){
throw new NullPointerException( "can not set null for
Fellow Hibernaters,
I'm receiving an Exception in a Hibernate application I've built, and I'm
a bit confused as to why this might be happening. The code at where the
Exception is thrown is quite simple, and I think this might be a bug in
Hibernate itself. I've searched Google for this to no avai
