Wanted to point out that I have a new Gradle PoC branch in SVN at
https://svn.jboss.org/repos/hibernate/core/branches/gradle2 Of special
interest, this branch supports generating intellij project from the
source. The Gradle guys have been really awesome in helping me to get
this ready. You'll ne
Ok, now that is reasonable :) And looking through the source (for Field
at least) is does circumvent a lot of checks if accessible is set.
So I can move the '!ReflectHelper.isPublic' check into the catch blocks
to continue to error in cases where we *need* to call setAccessible; for
other cases I
Guys,
I'me now done with the level of abstraction and fluidity I wanted out of the
query DSL. Please review before we push that out. Key features:
- fluent API
- use the field bridge system: type is passed, not raw string
- use the analyzer transparently
- simple use case simple, complex use
"We do in fact utilize setAccessible in the Hibernate code"
Yes, but if I am not mistaken only if the method/field is not public. From
code: !ReflectHelper.isPublic(theClass, method) )
method.setAccessible(true);
We could increase performance easily if we call setAccessible even for
public methods
All info here - http://in.relation.to/15699.lace
--Hardy
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Perhaps. We do in fact utilize setAccessible in the Hibernate code and
so when I did performance testing I did that as well as it most closely
matched our actual usage. Most likely it applies the checks "up front"
when setAccessible is called.
I'll take a look at the test and the numbers when i
Hi,
I have done some tests that are more pure in that they do not involve the
application logic.
Java version: jdk1.6.0_19 32-bit
Results include both client and server mode tests. Numbers represent 100 000
000 invocations time in milliseconds.
The result format is the following:
server_mode_
