Analyzing the ORM testsuite
by Sanne Grinovero
Hi all,
I'm trying to analyze the memory usage of current master of Hibernate
ORM; I started looking because of OOM errors on the PostgreSQL
testsuite (as mentioned in another thread).
So far I've seen that Mockito is allocating a "lot of stuff"; I might
be able to improve some things in that area but it's a distraction
from my goal as clearly we use Mockito even when not running the
PostgreSQL backed tests and that seems to run fine. But it's polluting
the data reports so making it hard (and slow!) to verify if there is a
real issue.
I could use some help to verify some tangential issues though; when
running the testsuite locally it's taking much longer than what I've
been used to see for the same testsuite some weeks ago, and I have
some failures - regularly seeing the same failures.
These are triggered by running a default build, on H2:
> Task :hibernate-core:test
org.hibernate.test.criteria.CriteriaLockingTest >
testSetLockModeDifferentFromNONELogAWarnMessageWhenTheDialectUseFollowOnLockingIsTrue
FAILED
org.junit.runners.model.TestTimedOutException
org.hibernate.test.criteria.CriteriaLockingTest >
testSetLockModeNONEDoNotLogAWarnMessageWhenTheDialectUseFollowOnLockingIsTrue
FAILED
java.lang.Exception
org.hibernate.test.criteria.CriteriaLockingTest >
org.hibernate.test.criteria.CriteriaLockingTest FAILED
java.lang.Exception
org.hibernate.test.locking.warning.LockNoneWarmingTest >
org.hibernate.test.locking.warning.LockNoneWarmingTest FAILED
java.lang.Exception
6307 tests completed, 4 failed, 327 skipped
Yet the puzzling point: on ci.hibernate.org I don't see these failures
happening, nor the testsuite time seems to have increased of any
significant amount (it regularly completes in somewhere between 15 and
20 minutes). It takes me more than an hour to get this result on a
machine which would normally complete the testsuite in 8 minutes, and
I got the same 4 failures when re-running it a second time.
Could other developers also please checkout master - specifically at
commit 291d4a3eeaa2ade32a42cfbcad5868b2114c34fe - and let me know if
it works allright for you and if the build time is consistent with the
usual times for your machine? I need to understand what might be
different between my workstation and the CI server.
I might even have some great improvements ready to reduce the
testsuite time, but I'm not comfortable in committing them in this
context.
Thanks,
Sanne
8 years
Fwd: Build failed in Jenkins: hibernate-orm-master-pgsql #1038
by Steve Ebersole
I'm going to disable this build until we have a chance to figure out why it
breaks constantly
---------- Forwarded message ---------
From: Hibernate CI <ci(a)hibernate.org>
Date: Tue, Apr 17, 2018 at 8:35 AM
Subject: Build failed in Jenkins: hibernate-orm-master-pgsql #1038
To: <steve(a)hibernate.org>, <christian.beikov(a)gmail.com>, <
rdrg.turini(a)gmail.com>, <sanne(a)hibernate.org>, <jonathan.bregler(a)sap.com>, <
chris(a)hibernate.org>, <github(a)s.traiectum.net>, <arichir(a)altissia.com>, <
dreborier(a)gmail.com>, <mihalcea.vlad(a)gmail.com>
See <
http://ci.hibernate.org/job/hibernate-orm-master-pgsql/1038/display/redir...
>
Changes:
[rdrg.turini] HHH-12451 - Fixing JDBC and Java Type order for CurrencyType
[Sanne Grinovero] HHH-12493 Further reduce allocations of ByteBuddy engines
[Sanne Grinovero] Amend an out of date javadoc comment referring to CGLIB
------------------------------------------
[...truncated 128.65 KB...]
org.hibernate.test.collection.delayedOperation.ListAddTest > classMethod
FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.delayedOperation.BagDelayedOperationTest >
classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.delayedOperation.SetDelayedOperationTest >
classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.delayedOperation.ListDelayedOperationTest >
classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.bag.PersistentBagTest > classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.bag.PersistentBagContainsTest > classMethod
FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.bag.BagElementNullBasicTest > classMethod
FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.bag.MultipleBagFetchHqlTest > classMethod
FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.bag.BagDuplicatesTest > classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.bag.MultipleBagFetchTest >
testEntityWithMultipleJoinFetchedBags FAILED
java.lang.OutOfMemoryError
org.hibernate.test.collection.custom.basic.UserCollectionTypeAnnotationsVariantTest
> classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.custom.basic.UserCollectionTypeHbmVariantTest
> classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.custom.parameterized.ParameterizedUserCollectionTypeHbmVariantTest
> classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.custom.parameterized.ParameterizedUserCollectionTypeAnnotationsVariantTest
> classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.dereferenced.UnversionedCascadeDereferencedCollectionTest
> classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.dereferenced.UnversionedNoCascadeDereferencedCollectionTest
> classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.dereferenced.VersionedNoCascadeDereferencedCollectionTest
> classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.dereferenced.VersionedCascadeDereferencedCollectionTest
> classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.multisession.MultipleSessionCollectionWarningTest
> classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.multisession.MultipleSessionCollectionTest >
classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.list.ListIndexReferenceFromListElementTest >
classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.list.ListElementNullBasicTest > classMethod
FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.list.PersistentListTest > classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.collection.backref.map.compkey.BackrefCompositeMapKeyTest
> classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.connections.BasicConnectionProviderTest >
initializationError FAILED
java.lang.OutOfMemoryError
org.hibernate.test.connections.HibernateCreateBlobFailedCase > classMethod
FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.SchemaMigratorHaltOnErrorTest >
testHaltOnError FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.MigrationTest >
testIndexCreationViaSchemaUpdate FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.MigrationTest >
testSameTableNameDifferentExplicitSchemas FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.MigrationTest > testSimpleColumnAddition
FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.idbag.IdBagSequenceTest >
testIdBagSequenceGeneratorIsCreated FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.QuotedTableNameSchemaUpdateTest >
testSchemaUpdateWithQuotedTableName FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.IdentifierHelperTest >
testAutoQuotingDisabled FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.inheritance.tableperclass.SchemaCreationTest
> testUniqueConstraintIsCorrectlyGenerated FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.inheritance.ForeignKeyNameTest >
testJoinedSubclassForeignKeyNameIsNotAutoGeneratedWhenProvided FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.inheritance.ForeignKeyNameTest >
testSubclassForeignKeyNameIsNotAutoGeneratedWhenProvided FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.inheritance.hhh_x.InheritanceSchemaUpdateTest
> testBidirectionalOneToManyReferencingRootEntity FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.SchemaUpdateWithViewsTest > classMethod
FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.SchemaUpdateTest >
testSchemaUpdateAndValidation[0] FAILED
java.lang.OutOfMemoryError
java.lang.NullPointerException at SchemaUpdateTest.java:135
org.hibernate.test.schemaupdate.SchemaUpdateTest >
testSchemaUpdateAndValidation[1] FAILED
java.lang.OutOfMemoryError
java.lang.NullPointerException at SchemaUpdateTest.java:135
org.hibernate.test.schemaupdate.SchemaMigrationTargetScriptCreationTest >
classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.index.ComponentIndexTest >
testTheIndexIsGenerated FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.index.IndexesCreationTest >
testTheIndexIsGenerated FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.TestFkUpdating > testUpdate FAILED
java.lang.OutOfMemoryError
java.lang.NullPointerException at TestFkUpdating.java:53
org.hibernate.test.schemaupdate.SchemaUpdateProceedOnErrorTest >
testHaltOnError FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.SchemaExportTest > testBothType FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.SchemaExportTest > testCreateAndDrop FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.SchemaExportTest >
testCreateAndDropOnlyType FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.SchemaExportTest > testGenerateDdlToFile
FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.SchemaExportTest >
testHibernateMappingSchemaPropertyIsNotIgnored FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.manytomany.ForeignKeyNameTest >
testJoinedSubclassForeignKeyNameIsNotAutoGeneratedWhenProvided FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.TableCommentTest > classMethod FAILED
org.hibernate.testing.junit4.CallbackException
Caused by: java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.SchemaUpdateTableBackedSequenceTest >
testCreateTableOnUpdate FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.CommentGenerationTest >
testSchemaUpdateScriptGeneration FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.SchemaUpdateDelimiterTest >
testSchemaUpdateApplyDelimiterToGeneratedSQL FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.PostgreSQLMultipleSchemaSequenceTest > test
FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.ConnectionsReleaseTest >
testSchemaUpdateReleasesAllConnections FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.ConnectionsReleaseTest >
testSchemaValidatorReleasesAllConnections FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.SchemaUpdateHaltOnErrorTest >
testHaltOnError FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.foreignkeys.ForeignKeyDropTest >
testForeignKeyDropIsCorrectlyGenerated FAILED
java.lang.OutOfMemoryError
org.hibernate.test.schemaupdate.foreignkeys.JoinedInheritanceForeignKeyTest
> testForeignKeyHasCorrectName FAILED
java.lang.OutOfMemoryError
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread "pool-2501-thread-1"
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread "pool-234-thread-1"
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create name string at JPLISAgent.c line: 807
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create name string at JPLISAgent.c line: 807
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
*** java.lang.instrument ASSERTION FAILED ***: "!errorOutstanding" with
message can't create byte arrau at JPLISAgent.c line: 813
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread "pool-2514-thread-1"
Exception: java.lang.OutOfMemoryError thrown from the
UncaughtExceptionHandler in thread "pool-2378-thread-1"
Build timed out (after 120 minutes). Marking the build as failed.
Build was aborted
Recording test results
Warning: user rdrg.turini(a)gmail.com has no permission to view
hibernate-orm-master-pgsql #1038, but sending mail anyway
Warning: user sanne(a)hibernate.org has no permission to view
hibernate-orm-master-pgsql #1038, but sending mail anyway
Warning: user jonathan.bregler(a)sap.com has no permission to view
hibernate-orm-master-pgsql #1038, but sending mail anyway
Warning: user chris(a)hibernate.org has no permission to view
hibernate-orm-master-pgsql #1038, but sending mail anyway
Warning: user github(a)s.traiectum.net has no permission to view
hibernate-orm-master-pgsql #1038, but sending mail anyway
Warning: user arichir(a)altissia.com has no permission to view
hibernate-orm-master-pgsql #1038, but sending mail anyway
Warning: user mihalcea.vlad(a)gmail.com has no permission to view
hibernate-orm-master-pgsql #1038, but sending mail anyway
8 years
Hibernate OGM 5.4.0.Alpha1 release
by Davide D'Alto
We’re happy to announce the release of Hibernate OGM 5.4.0.Alpha1.
Hibernate OGM is now compatible with Hibernate ORM 5.3 (still a
candidate release) and JPA 2.2. We support Infinipan 9.2 and JBoss
modules are now available as WildFly feature packs.
You can run server-side JavaScript on MongoDB or Java code in
Infinispan Embedded as if they were stored procedures using the JPA
approach.
When using the Infinispan Remote dialect, it is now possible to
configure new caches using the @CacheConfiguration annotation.
You can find all the details in the blog post:
http://in.relation.to/2018/04/17/hibernate-ogm-5-4-Alpha1-released/
Thanks,
Davide
8 years
Hibernate Search 5.10.0.Beta2
by Yoann Rodiere
Hi,
We just published 5.10.0.Beta2, the second beta release for the 5.10
branch. This release mainly includes an upgrade to WildFly 12 for the JBoss
modules, but it also adds a few bugfixes and improvements.
Check out our blog for more information about this release:
http://in.relation.to/2018/04/13/hibernate-search-5-10-0-Beta2/
--
Yoann Rodiere
yoann(a)hibernate.org / yrodiere(a)redhat.com
Software Engineer
Hibernate NoORM team
8 years
HHH-8944 - ColumnTransformer handling is too aggressive in qualifying "column names"
by Steve Ebersole
Anyone know of places where we document ColumnTransformer read-fragment
handling as qualifying columns other than the column the transformer is
attached to? E.g., consider:
@Column( name="dob" )
@ColumnTransformer( read="SYSDATE - dob / 365", ... )
public int getAge() { ... }
Currently, Hibernate will try to qualify both "SYSDATE" and "dob" with
table alias. The simple fix is to simply limit the qualification to the
column that the transformer is attached to ("dob"). Just want to make sure
that we do not document anywhere that multiple column references will all
be replaced. E.g. (contrived):
@Column( name="dob" )
@ColumnTransformer( read="(SYSDATE - dob / 365) + offset", ... )
public int getAge() { ... }
The question is whether both "dob" and "offset" columns will get
qualified. Allowing this is much more involved, requiring that we somehow
allow configuration of all the referenced columns that should be qualified
(which has its own set of difficulties when it comes to multi-table
structures).
I propose the simple solution, unless there are any objections
8 years
JDK 11 Early Access build 8 available
by Rory O'Donnell
Hi Sanne,
**JDK 11 EA build 8, *****under both the GPL and Oracle EA licenses, is
now available at **http://jdk.java.net/11**. **
*
* Newly approved Schedule, status & features
o http://openjdk.java.net/projects/jdk/11/
* Release Notes:
o http://jdk.java.net/11/release-notes
* Summary of changes
o https://download.java.net/java/early_access/jdk11/8/jdk-11+8.html
*Notable changes in JDK 11 EA builds since last email:*
* Build 8:
o If you have a library that uses the Selector API heavily then
now would be a good time to test it out. [1]
* Build 7
o The VM option "-XX:+AggressiveOpts" is deprecated in JDK 11 and
will be removed in a future release.
* Build 6:
o JDK-8193033 : remove terminally deprecated
sun.misc.Unsafe.defineClass. Users should use the public
replacement `java.lang.invoke.MethodHandles.Lookup.defineClass`
which was added in Java SE 9. [2]
**
*SURVEY: The HotSpot Serviceability Agent (SA) *[3]
* If you have used, or have (support) processes that utilize the
Serviceability Agent or related APIs, then we would definitely
appreciate if you would complete this survey:
https://www.surveymonkey.com/r/CF3MYDL
Regards,
Rory
[1] http://mail.openjdk.java.net/pipermail/nio-dev/2018-April/004964.html
[2]
https://docs.oracle.com/javase/9/docs/api/java/lang/invoke/MethodHandles....
[3] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-April/001052.html
--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland
8 years
HipChat / JIRA / Atlassian account(s) login
by Sanne Grinovero
Many of us reported problems with HipChat today / recently.
It seems Atlassian has merged accounts of HipChat and various other
services, like our
JIRA.
I would suggest to reset your password and consider that your new
password will apply to all (most?) of your Atlassian accounts:
I'm not sure what they did exactly, but after resetting my password on
JIRA a couple of days back, now to login on HipChat I had to use that
same password.
HTH
8 years
[HSEARCH][V6-POC] Bug tracking for the Search 6 POC
by Yoann Rodiere
Hello,
With the Search 6 POC getting closer and closer to something we can merge,
and thus more and more complex, we are starting to see quite a lot of TODOs
piling up.
I've been tracking most of them in a Google Doc
<https://docs.google.com/document/d/16PAa__LsxyLZcbW3q1MvgyIznh4ZnCYLupbNM...>
so far, and it's fine for big architectural topics, but for small things
it's clearly inadequate.
What would you all think if we started to use the main Hibernate Search
project to track the small TODOs we have in the Search 6 POC? We would
probably have to add some JIRA Components that only make sense in Search 6
("indexing", ...), but beyond that I don't think this would cause much
trouble.
The tickets would all be Tasks targeting version 6, and we could tag them
with a new "POC-6.0" component if you think it's necessary. Examples of
tasks would be:
- Native sorts in the Lucene Sort DSL extension
<https://docs.google.com/document/d/16PAa__LsxyLZcbW3q1MvgyIznh4ZnCYLupbNM...>
- Native predicates in the Lucene Predicate DSL extension
<https://docs.google.com/document/d/16PAa__LsxyLZcbW3q1MvgyIznh4ZnCYLupbNM...>
- Rework the Lucene DSL implementations to fail fast when parameter
conversion errors occur
<https://docs.google.com/document/d/16PAa__LsxyLZcbW3q1MvgyIznh4ZnCYLupbNM...>
- Polish and test Stream indexing (add CompletableFuture returns in
particular)
- Decide wether to use absolute or relative object path in "nested"
search predicates
If this feels like too much garbage for the main bug tracker, we can create
a separate JIRA project instead. But then this will add to the trouble
we'll have to go through when merging (commits referring to tickets from
another project).
Sanne, all, WDYT?
--
Yoann Rodiere
yoann(a)hibernate.org / yrodiere(a)redhat.com
Software Engineer
Hibernate NoORM team
8 years
