6 p.m.
Unsubscribe
On Jan 14, 2010, at 10:27 AM, hibernate-dev-request(a)lists.jboss.org wrote:
Send hibernate-dev mailing list submissions to
hibernate-dev(a)lists.jboss.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.jboss.org/mailman/listinfo/hibernate-dev
or, via email, send a message with subject or body 'help' to
hibernate-dev-request(a)lists.jboss.org
You can reach the person managing the list at
hibernate-dev-owner(a)lists.jboss.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of hibernate-dev digest..."
Today's Topics:
1. Re: Weird backref issue within the AttributeFactory (Was Re:
Some code questions) (Emmanuel Bernard)
2. Re: Weird backref issue within the AttributeFactory (Was Re:
Some code questions) (Adam Warski)
3. Re: [hibernate-announce] Hibernate 3.5.0-Beta-3 release
(Hardy Ferentschik)
4. Re: Solution for failing Isolated query cache tests in
Hibernate trunk (Steve Ebersole)
5. Re: Weird backref issue within the AttributeFactory (Was Re:
Some code questions) (Steve Ebersole)
6. Re: [hibernate-announce] Hibernate 3.5.0-Beta-3 release
(Steve Ebersole)
7. Re: [hibernate-announce] Hibernate 3.5.0-Beta-3 release
(Steve Ebersole)
8. 3.5.0-Beta-3 has different behaviour on commit as
3.5.0-Beta-2, is this intended? (Guenther Demetz)
9. Re: [hibernate-announce] Hibernate 3.5.0-Beta-3 release
(Chris Bredesen)
10. Re: Weird backref issue within the AttributeFactory (Was Re:
Some code questions) (Emmanuel Bernard)
11. Re: 3.5.0-Beta-3 has different behaviour on commit as
3.5.0-Beta-2, is this intended? (Emmanuel Bernard)
----------------------------------------------------------------------
Message: 1
Date: Thu, 14 Jan 2010 13:57:40 +0100
From: Emmanuel Bernard <emmanuel(a)hibernate.org>
Subject: Re: [hibernate-dev] Weird backref issue within the
AttributeFactory (Was Re: Some code questions)
To: Hardy Ferentschik <hibernate(a)ferentschik.de>
Cc: hibernate-dev <hibernate-dev(a)lists.jboss.org>
Message-ID: <4813641E-9302-4F7A-85D8-B63135E71A54(a)hibernate.org>
Content-Type: text/plain; charset=us-ascii
Right, I tried to explain the failure in the first email. But AFAIK the bug has been there
for a little while (ie before the work i've done in the last couple of days).
On 14 janv. 2010, at 13:54, Hardy Ferentschik wrote:
We disabled the test yesterday in order to do the release.
It was failing in w/ and w/o a fix to Emmanuel's code.
--Hardy
On Thu, 14 Jan 2010 09:24:23 -0300, Adam Warski <adam(a)warski.org> wrote:
Hello,
Though it uncovered a weird problem.
When I run the entire envers test suite, I pass with flags up.
When I specifically run VersionsJoinTableRangeComponentNamingTest
That's probably because the test is disabled in the suite :).
------------------------------
Message: 2
Date: Thu, 14 Jan 2010 14:04:07 +0100
From: Adam Warski <adam(a)warski.org>
Subject: Re: [hibernate-dev] Weird backref issue within the
AttributeFactory (Was Re: Some code questions)
To: Emmanuel Bernard <emmanuel(a)hibernate.org>
Cc: hibernate-dev <hibernate-dev(a)lists.jboss.org>
Message-ID: <BAD821FC-0A63-43F5-9699-F6D7B600BEC6(a)warski.org>
Content-Type: text/plain; charset=us-ascii
Hello,
Right, I tried to explain the failure in the first email. But AFAIK the bug has been there
for a little while (ie before the work i've done in the last couple of days).
yes, it's there for at least two weeks. I mentioned it on IRC before but I guess it
didn't draw any attention.
I didn't create a JIRA issue as it's in the new metamodel stuff so I figured that
you're actively working on it. But at least it serves as a good testcase for it :)
--
Adam
------------------------------
Message: 3
Date: Thu, 14 Jan 2010 10:17:20 -0300
From: "Hardy Ferentschik" <hibernate(a)ferentschik.de>
Subject: Re: [hibernate-dev] [hibernate-announce] Hibernate
3.5.0-Beta-3 release
To: "Emmanuel Bernard" <emmanuel(a)hibernate.org>, "Steve
Ebersole"
<steve(a)hibernate.org>
Cc: hibernate-dev(a)lists.jboss.org
Message-ID: <op.u6ixu6b2qxbac6(a)aleppo.lan>
Content-Type: text/plain; charset=iso-8859-15; format=flowed;
delsp=yes
I think we could do the same with the version string as we do in Validator
( and maybe Search, not sure ). There we
read the version string from the MANIFEST file. The nice things about this
is that the version in the MANIFEST is
dynamically created during the build.
Generally there are quite a few things we can do in the build
configuration for annotations and entitymanager.
The plugin configuration should be better synced with the parent pom and
there are quite a few obsolete docbook resources
checked in. Maybe the whole docbook stuff should be moved into the
documentation directory.
I will try to sort a few of these things out for the next release.
--Hardy
On Thu, 14 Jan 2010 07:34:50 -0300, Emmanuel Bernard
<emmanuel(a)hibernate.org> wrote:
Yeah!
I've just noticed one glitch (except the NPE I managed to add ;) ). The
Version numbers in the logs are not updated for annotations and entity
manager.
We should add them to the release procedure.
Or simply remove them now that ANN and HEM are part of Core. The only
drawback I see is that HEM runs before Core but I guess we could trigger
the call to the static version display from HEM to Core.
------------------------------
Message: 4
Date: Thu, 14 Jan 2010 08:31:56 -0600
From: Steve Ebersole <steve(a)hibernate.org>
Subject: Re: [hibernate-dev] Solution for failing Isolated query cache
tests in Hibernate trunk
To: Emmanuel Bernard <emmanuel(a)hibernate.org>
Cc: hibernate-dev(a)lists.jboss.org, "JBoss.org development list"
<jboss-development(a)lists.jboss.org>
Message-ID: <1263479516.2706.444.camel(a)localhost.localdomain>
Content-Type: text/plain
Oddly it does that already. Its just that only Serailaizable.class is
ever passed
http://fisheye.jboss.org/browse/Hibernate/core/trunk/core/src/main/java/o...
This has to do with the "static" nature of the type system.
On Thu, 2010-01-14 at 11:19 +0100, Emmanuel Bernard wrote:
On 13 janv. 2010, at 19:10, Steve Ebersole wrote:
So, getReturnedClass().getClassLoader() is not the answer here.
There is the only answer unfortunately. Really you'd want the Class of
the class implementing Serializable, but given how Hibernate's "type
system" works currently, that's not an option.
Well it could be an option if you do like Annotations does for EnumType and pass the
returned class as a parameter of SerializableType but frankly that's a bit painful.
--
Steve Ebersole <steve(a)hibernate.org>
Hibernate.org
------------------------------
Message: 5
Date: Thu, 14 Jan 2010 08:35:06 -0600
From: Steve Ebersole <steve(a)hibernate.org>
Subject: Re: [hibernate-dev] Weird backref issue within the
AttributeFactory (Was Re: Some code questions)
To: Emmanuel Bernard <emmanuel(a)hibernate.org>
Cc: hibernate-dev(a)lists.jboss.org
Message-ID: <1263479706.2706.446.camel(a)localhost.localdomain>
Content-Type: text/plain
Ah, backrefs!
Just disregarding them makes the most sense for sure from the JPA
perspective since they are "virtual attributes" and solely a hibernate
construct.
On Thu, 2010-01-14 at 11:29 +0100, Emmanuel Bernard wrote:
On 13 janv. 2010, at 20:37, Hardy Ferentschik wrote:
I have a couple of question regarding some recent code changes. The first one seems to be
the cause of a
test failure in VersionsJoinTableRangeComponentNamingTest (Envers). It actually causes a
NullPointerException.
Have a look at:
http://fisheye.jboss.org/browse/Hibernate/core/trunk/annotations/src/main...
Right, I fixed the problem, sorry about that.
Though it uncovered a weird problem.
When I run the entire envers test suite, I pass with flags up.
When I specifically run VersionsJoinTableRangeComponentNamingTest
I've got a
java.lang.IllegalArgumentException: Cannot determine java-type from given member [null]
at
org.hibernate.ejb.metamodel.AttributeFactory$BaseAttributeMetadata.<init>(AttributeFactory.java:591)
at
org.hibernate.ejb.metamodel.AttributeFactory$SingularAttributeMetadataImpl.<init>(AttributeFactory.java:671)
at
org.hibernate.ejb.metamodel.AttributeFactory$SingularAttributeMetadataImpl.<init>(AttributeFactory.java:661)
at
org.hibernate.ejb.metamodel.AttributeFactory.determineAttributeMetadata(AttributeFactory.java:542)
at
org.hibernate.ejb.metamodel.AttributeFactory.buildAttribute(AttributeFactory.java:81)
at org.hibernate.ejb.metamodel.MetadataContext.wrapUp(MetadataContext.java:177)
at org.hibernate.ejb.metamodel.MetamodelImpl.buildMetamodel(MetamodelImpl.java:66)
at
org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:79)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:752)
at org.hibernate.envers.test.AbstractEntityTest.init(AbstractEntityTest.java:94)
at org.hibernate.envers.test.AbstractEntityTest.init(AbstractEntityTest.java:82)
The member is null because the "property" has a backref getter and hence no
member is returned by NORMAL_MEMBER_RESOLVER. I think we should ignore backref properties
Does that make sense? If we agree, I will go and apply a fix.
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4797
Also have a look at
http://fisheye.jboss.org/browse/Hibernate/core/trunk/annotations/src/main...
You create a AssertionFailure, but then don't throw it? I guess this is just missing a
'throw' before the new.
yep, fixed.
--
Steve Ebersole <steve(a)hibernate.org>
Hibernate.org
------------------------------
Message: 6
Date: Thu, 14 Jan 2010 08:35:58 -0600
From: Steve Ebersole <steve(a)hibernate.org>
Subject: Re: [hibernate-dev] [hibernate-announce] Hibernate
3.5.0-Beta-3 release
To: Emmanuel Bernard <emmanuel(a)hibernate.org>
Cc: hibernate-dev(a)lists.jboss.org
Message-ID: <1263479758.2706.447.camel(a)localhost.localdomain>
Content-Type: text/plain
We should probably just remove them I think. Pretty annoying to see the
same version output over and over and over.
On Thu, 2010-01-14 at 11:34 +0100, Emmanuel Bernard wrote:
Yeah!
I've just noticed one glitch (except the NPE I managed to add ;) ). The Version
numbers in the logs are not updated for annotations and entity manager.
We should add them to the release procedure.
Or simply remove them now that ANN and HEM are part of Core. The only drawback I see is
that HEM runs before Core but I guess we could trigger the call to the static version
display from HEM to Core.
On 14 janv. 2010, at 06:28, Steve Ebersole wrote:
JPA support is coming along nicely!
See the highlights and links to all the goodies at
http://in.relation.to/Bloggers/Hibernate350Beta3Release
--
Steve Ebersole <steve(a)hibernate.org>
Hibernate.org
_______________________________________________
hibernate-announce mailing list
hibernate-announce(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-announce
--
Steve Ebersole <steve(a)hibernate.org>
Hibernate.org
------------------------------
Message: 7
Date: Thu, 14 Jan 2010 08:41:51 -0600
From: Steve Ebersole <steve(a)hibernate.org>
Subject: Re: [hibernate-dev] [hibernate-announce] Hibernate
3.5.0-Beta-3 release
To: Hardy Ferentschik <hibernate(a)ferentschik.de>
Cc: hibernate-dev(a)lists.jboss.org
Message-ID: <1263480111.2706.453.camel(a)localhost.localdomain>
Content-Type: text/plain
On Thu, 2010-01-14 at 10:17 -0300, Hardy Ferentschik wrote:
I think we could do the same with the version string as we do in Validator
( and maybe Search, not sure ). There we
read the version string from the MANIFEST file. The nice things about this
is that the version in the MANIFEST is
dynamically created during the build.
We do this with core as well in terms of dynamic. We use that bytecode
injjection maven plugin i wrote.
Generally there are quite a few things we can do in the build
configuration for annotations and entitymanager.
The plugin configuration should be better synced with the parent pom and
there are quite a few obsolete docbook resources
checked in. Maybe the whole docbook stuff should be moved into the
documentation directory.
We have this "unclean" problem even in core:
http://fisheye.jboss.org/browse/Hibernate/core/trunk/documentation/manual...
and others. I had just been waiting till we get around to actually
concolidating all the docs to go through that all at once. Feel free to
do it or piece of it now though.
--
Steve Ebersole <steve(a)hibernate.org>
Hibernate.org
------------------------------
Message: 8
Date: Thu, 14 Jan 2010 15:51:37 +0100
From: Guenther Demetz <guenther.demetz(a)wuerth-phoenix.com>
Subject: [hibernate-dev] 3.5.0-Beta-3 has different behaviour on
commit as 3.5.0-Beta-2, is this intended?
To: "hibernate-dev(a)lists.jboss.org" <hibernate-dev(a)lists.jboss.org>
Message-ID: <4B4F2F79.7020109(a)wuerth-phoenix.com>
Content-Type: text/plain; charset="ISO-8859-15"; format=flowed
-until 3.5.0-Beta-2 a ConstraintViolationException during commit caused
an implicite rollback and the exception was wrapped into a
javax.persistence.RollbackException
-now with 3.5.0-Beta-3 the same ConstraintViolationException during
commit is wrapped into a javax.persistence.PersistenceException without
implicite rollback
Is this a wanted behavior change?
If yes, where it is documented?
best regards
G.D.
------------------------------
Message: 9
Date: Thu, 14 Jan 2010 09:57:58 -0500
From: Chris Bredesen <cbredesen(a)redhat.com>
Subject: Re: [hibernate-dev] [hibernate-announce] Hibernate
3.5.0-Beta-3 release
To: hibernate-dev(a)lists.jboss.org
Message-ID: <4B4F30F6.6090301(a)redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 01/14/2010 05:34 AM, Emmanuel Bernard wrote:
Or simply remove them now that ANN and HEM are part of Core. The only
drawback I see is that HEM runs before Core but I guess we could
trigger the call to the static version display from HEM to Core.
They're still separate jars though, right? If so, I'd prefer to leave
the version info there so that we can rule out mismatched distros by
looking at logging.
-CB
------------------------------
Message: 10
Date: Thu, 14 Jan 2010 16:12:33 +0100
From: Emmanuel Bernard <emmanuel(a)hibernate.org>
Subject: Re: [hibernate-dev] Weird backref issue within the
AttributeFactory (Was Re: Some code questions)
To: Steve Ebersole <steve(a)hibernate.org>
Cc: hibernate-dev(a)lists.jboss.org
Message-ID: <EE63F97C-172B-4EB3-9576-E19A4F74DCB8(a)hibernate.org>
Content-Type: text/plain; charset=us-ascii
On 14 janv. 2010, at 15:35, Steve Ebersole wrote:
Ah, backrefs!
Something you want to confess Steve? ;)
------------------------------
Message: 11
Date: Thu, 14 Jan 2010 16:26:55 +0100
From: Emmanuel Bernard <emmanuel(a)hibernate.org>
Subject: Re: [hibernate-dev] 3.5.0-Beta-3 has different behaviour on
commit as 3.5.0-Beta-2, is this intended?
To: Guenther Demetz <guenther.demetz(a)wuerth-phoenix.com>
Cc: "hibernate-dev(a)lists.jboss.org" <hibernate-dev(a)lists.jboss.org>
Message-ID: <1BA17F7B-A55E-4440-A831-BE326263D01F(a)hibernate.org>
Content-Type: text/plain; charset=us-ascii
Hello,
I cannot reproduce what you are describing.
Here are the two tests I have on the subject.
http://fisheye.jboss.org/browse/Hibernate/core/trunk/entitymanager/src/te...
How is your configuration different?
On 14 janv. 2010, at 15:51, Guenther Demetz wrote:
-until 3.5.0-Beta-2 a ConstraintViolationException during commit caused
an implicite rollback and the exception was wrapped into a
javax.persistence.RollbackException
-now with 3.5.0-Beta-3 the same ConstraintViolationException during
commit is wrapped into a javax.persistence.PersistenceException without
implicite rollback
Is this a wanted behavior change?
If yes, where it is documented?
best regards
G.D.
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
------------------------------
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
End of hibernate-dev Digest, Vol 43, Issue 11
*********************************************