November 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4575) When Infinispan is configured for INVALIDATION don't send cluster message on entity insert

by Galder Zamarreno (JIRA)

When Infinispan is configured for INVALIDATION don't send cluster message on entity insert ------------------------------------------------------------------------------------------ Key: HHH-4575 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4575 Project: Hibernate Core Issue Type: Improvement Components: caching (L2) Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 3.5 Port HHH-4484 over to Infinispan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3935) Bad Certificate on bug website

by Patrick Moore (JIRA)

Bad Certificate on bug website ------------------------------ Key: HHH-3935 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3935 Project: Hibernate Core Issue Type: Bug Reporter: Patrick Moore When going to :http://opensource.atlassian.com/projects/hibernate/secure/CreateIssue.jspa I am getting this browser message (FF) : hibernate.bluemars.net:443 uses an invalid security certificate. The certificate is only valid for <a id="cert_domain_link" title="*.hibernate.org">*.hibernate.org</a> (Error code: ssl_error_bad_cert_domain) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

3
3
0 / 0

[Hibernate-JIRA] Created: (EJB-272) PostRemove being called before entity is actually deleted

by Paul (JIRA)

PostRemove being called before entity is actually deleted --------------------------------------------------------- Key: EJB-272 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-272 Project: Hibernate Entity Manager Type: Bug Versions: 3.2.1 Environment: Hibernate 3.2.1GA Entity Manager Hibernate core 3.2.2 GA Oracle 9i Windows XP professional service pack 2 No application server is being used. Reporter: Paul I have an EntityListener with a method annotated with postremove. It seems that the method is being called before the actual entity is deleted from the database. When configuring log4j with "debug" logging it appears that the method is being called after the PreparedStatement is created and configured but before executeUpdate() is called. I see the following statements in my log file before my listener is called 14:06:27,024 DEBUG AbstractBatcher:476 - preparing statement 14:06:27,024 DEBUG IntegerType:133 - binding '59532' to parameter: 1 My listener is called next. Then, the prepared statement is executed. This violates the EJB3 spec. The EJB3 spec states "The PostPersist and PostRemove methods will be invoked after the database insert and delete operations respectively." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4499) Account for modules needing JDK 1.6

by Steve Ebersole (JIRA)

Account for modules needing JDK 1.6 ----------------------------------- Key: HHH-4499 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4499 Project: Hibernate Core Issue Type: Task Components: build Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5 Currently both the hibernate-infinispan and hibernate-jdb4-testing modules need JDK 1.6, whereas the rest of Hibernate needs to be built using JDK 1.5. The solution is to fork both javac and surefire to pass in the JDK: </plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <executable>${jdk16_home}/bin/javac</executable> <fork>true</fork> <verbose>true</verbose> <compilerVersion>1.6</compilerVersion> <source>1.6</source> <target>1.6</target> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <configuration> <jvm>${jdk16_home}/bin/java</jvm> ... </configuration> </plugin> Notice the use of the jdk16_home property to allow this to be customized to each developers machine... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4622) Hibernate still refuses to build on JDK6

by Chris Wilson (JIRA)

Hibernate still refuses to build on JDK6 ---------------------------------------- Key: HHH-4622 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4622 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5 Environment: Ubuntu 8.04, Maven 2.0.8, JDK 1.6.0-16 Reporter: Chris Wilson Despite fixing the issue that stopped Hibernate building on JDK6 (HHH-2412), the Maven config still insists that jdk 1.5 is used, in parent/pom.xml:  <version>[1.5,1.6)</version> This seems not to be necessary any more, and it would be nice to enable building ootb on a modern JVM. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-426) Update archetype sources

by Hardy Ferentschik (JIRA)

Update archetype sources ------------------------- Key: HSEARCH-426 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-426 Project: Hibernate Search Issue Type: Task Components: build Affects Versions: 3.1.1.GA Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.2.0.Beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4620) Inject Hibernate's transaction manager into Infinispan cache instances

by Galder Zamarreno (JIRA)

Inject Hibernate's transaction manager into Infinispan cache instances ---------------------------------------------------------------------- Key: HHH-4620 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4620 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.5.0-Beta-2 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 3.5 Inject Hibernate's transaction manager into Infinispan cache instances -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4619) It's not possible to access insertability/updatability/etc of an embedded object's properties.

by Mikhail Vorozhtsov (JIRA)

It's not possible to access insertability/updatability/etc of an embedded object's properties. ---------------------------------------------------------------------------------------------- Key: HHH-4619 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4619 Project: Hibernate Core Issue Type: Bug Components: metamodel Affects Versions: 3.3.2 Reporter: Mikhail Vorozhtsov Priority: Minor Currently there is no way to access insertability/updatability/etc of an embedded object's properties via EntityMetamodel. StandardProperty seems like a right place for the reference to the corresponding ComponentMetamodel, i.e. entityMetamodel.getProperties()[EMBED_IDX].getComponentMetamodel().getProperty("subproperty").isUpdateable() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2609) Delete with multiple nested sub-queries generates invalid SQL (on Postgresql)

by Michael Barker (JIRA)

Delete with multiple nested sub-queries generates invalid SQL (on Postgresql) ----------------------------------------------------------------------------- Key: HHH-2609 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2609 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.4 Environment: Linux, JDK 1.5. Reporter: Michael Barker Attachments: delete-ejbql-problem.zip When a delete uses multiple nest subqueries the resulting SQL query generated is invalid. E.g. the EJB-QL: DELETE Foo f WHERE f.fooId NOT IN (SELECT bar.fooId FROM Bar bar) AND f.fooId NOT IN (SELECT baz.fooId FROM Baz baz) or DELETE Foo WHERE fooId NOT IN (SELECT fooId FROM Bar) AND fooId NOT IN (SELECT fooId FROM Baz) Generates the following: delete from Foo where (fooId not in (select bar1_.fooId from Bar bar1_)) and (foo0_.fooId not in (select baz2_.fooId from Baz baz2_)) Will fail because the field "foo0_.fooId" should be "fooId", "foo0_" is not declared. At test case is attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

3
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1829) Allow join on any property using property-ref

by Mathieu Gervais (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829?page=c... ] Mathieu Gervais commented on HHH-1829: -------------------------------------- We looked at the patch and we don't see how it can be easily done without updating all operations. Can you let us know what timeframe you expect the metadata API to be available? thanks, > Allow join on any property using property-ref > --------------------------------------------- > > Key: HHH-1829 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829 > Project: Hibernate Core > Issue Type: New Feature > Components: metamodel > Affects Versions: 3.2.0 cr1, 3.2.0.cr2 > Reporter: Maarten Winkels > Assignee: Anthony Patricio > Attachments: AbstractJoinTest.java, HHH-1829-3.2.8-SNAPSHOT.patch, HHH-1829-mwinkels.patch, hhh-1829.patch, JoinNoPropertyRefTest.java, JoinPropertyRefTest.java, Person.hbm.xml, Person.java, PersonNoPropertyRef.hbm.xml > > > Currently joining tables for one class (uing the <join...> tag) is only supported for the id property. The property-ref is allowed on the <key..> tag inside the <join..> tag, but this is ignored. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2009