Hi hibernate developers,
testing Hibernate ORM 4.1.1 I discovered a behavior change regarding Optimistic
Lock Versioning
in detail on bidirectional OneToMany relations with inverse-owner (mappedBy
attribute specified):
- until Hiberante version 4.1.0 by default on changes both involved sides go
Steve,
Just built it and I see no such folders in my env:
https://gist.github.com/2005857
Maybe these are old folders that were lying around?
They look to be JBoss Transactions related.
Cheers,
On Mar 8, 2012, at 1:53 AM, Steve Ebersole wrote:
> Running the hibernate-infinispan tests I am see
My build, including running tests, took:
Total time: 2 mins 53.136 secs
So, I'd say it's some env issue, maybe UDP traffic generated by the cluster
tests getting stuck somewhere?
Btw, I did improve the speed of these tests hugely a few months ago by
switching to an in-memory discovery protocol
My bad, I'll do that right away. CR1 was released just 3 days before FINAL, so
it's pretty stable already.
On Mar 8, 2012, at 2:56 AM, Steve Ebersole wrote:
> Hmm, I did not have problems resolving artifacts, but I just noticed
> this CR... we really need to not be upgrading to CR releases of
Not Infinispan, but JBoss Transactions.
On Mar 8, 2012, at 9:15 AM, Hardy Ferentschik wrote:
> This used to happen in Search as well, but is gone now (I think). Must be in
> Infinispan config thing.
> Sanne probably knows :-)
>
> --Hardy
>
>
> On Mar 8, 2012, at 2:53 AM, Steve Ebersole wrote
On Mar 8, 2012, at 10:48 AM, Sanne Grinovero wrote:
> Hi,
> I found the same files in my workspace as left over from and older
> build, but deleted them and tried new builds several times, they don't
> seem to be re-created anymore?
> Could anyone confirm (after cleaning them up) that it's still
On Mar 8, 2012, at 4:46 PM, Strong Liu wrote:
>
> On Mar 8, 2012, at 6:48 PM, Sanne Grinovero wrote:
>
>> Hi,
>> I found the same files in my workspace as left over from and older
>> build, but deleted them and tried new builds several times, they don't
>> seem to be re-created anymore?
>> Coul
No idea why, the JAR is there - maybe a Gradle/Ivy issue?
https://repository.jboss.org/nexus/content/groups/public/org/infinispan/infinispan-core/5.1.2.CR1/infinispan-core-5.1.2.CR1-tests.jar
I don't get this issue in my own env btw.
On Mar 8, 2012, at 2:19 AM, Strong Liu wrote:
> btw ci fails d
Immutable entities should still be deletable. Unless Gail changed that
during the consolidation with making a particular entity instance "read
only" as part of a session. There was a lot of discussion at that time
wrt consistency between these two things. I forget all the outcomes.
But imm
The old behavior violated JPA spec. The issue is HHH-7138
On Fri 09 Mar 2012 03:04:54 AM CST, Demetz, Guenther wrote:
> Hi hibernate developers,
>
> testing Hibernate ORM 4.1.1 I discovered a behavior change regarding
> Optimistic Lock Versioning
> in detail on bidirectional OneToMany relations
Luckily you get to decide to follow the company line and use inferior
tools as part of your project.
Considering that part works everywhere I find it funny that you can
chalk my issue up to env but this has to be a "gradle/ivy bug" lol.
There is also a far easier syntax for how you are trying t
Thank you Steve,
anyway in this context
I strongly recommend all Hibernate-Users to force version increment explicitly
on such OneToMany relations when the mapped collection is a map!
Otherwise, unless implementing some pessimistick locking, 2 concurrent
transactions will be able to insert an o
Hi,
I've just found the task and was wondering if I can be assigned on this
task. I would like to finish the task based on the comments that I got and
will get for my pull request if it's possible.
--
Thank you
Seiya
___
hibernate-dev mailing list
hibe
Hi Nicolas,
I've improved that test to be less time-sensitive, could you checkout
latest master and give it another try please?
The warnings you see in the log are nothing to worry about, they are
related to the fact that the test is using an in-memory channel to
avoid trouble with your potentiall
But you are already :)
If you mean physically on JIRA, send me your JIRA login.
Emmanuel
On 9 mars 2012, at 15:02, Seiya Kawashima wrote:
> Hi,
>
> I've just found the task and was wondering if I can be assigned on this
> task. I would like to finish the task based on the comments that I got an
Indexed collections (maps and lists) should always be the owning side
of bi-directional associations for the exact reason you mention. Not
sure if annotations actually enforces that or whether JPA even allows
us to enforce that.
On Fri 09 Mar 2012 07:53:20 AM CST, Demetz, Guenther wrote:
> Tha
>>Indexed collections (maps and lists) should always be the owning side of
>>bi-directional associations for the exact reason you mention.
OK, I suppose this is already mentioned somewhere in the documentation, or not
?
regards & nice weekend
G.D.
_
http://docs.jboss.org/hibernate/orm/3.5/reference/en-US/html_single/#collections-indexedbidirectional
Though:
1) Reading back through that section its not really clearly stated.
2) Later work to "fold in" the annotation mappings seems to have
completely dropped this unclearly stated point.
Essen
You roxx =)
I did build twice and it is working just nice.
Thanks a lot.
Niko
P.S : Ok ok I'll buy a MacBookPro with a SSD ... or not !
2012/3/9 Sanne Grinovero
> Hi Nicolas,
> I've improved that test to be less time-sensitive, could you checkout
> latest master and give it another try pleas
Yaay! It ony took slightly over 5 minutes today. But of course:
> Building > :hibernate-infinispan:test > Resolving dependencies
> ':hibernate-infinispan:test:hibernate-infinispan:test
Test
org.hibernate.test.cache.infinispan.entity.InvalidatedTransactionalTestCase
FAILED
Test org.hibernate.t
The documentation in 12.1.1 is correct. Read-only entities can be created and
deleted.
Sounds like you can't delete a single entity from the 2nd-level cache though.
That sounds like a bug.
- Original Message -
> From: "Steve Ebersole"
> To: "Strong Liu"
> Cc: "Hibernate hibernate-dev"
21 matches
Mail list logo
