May 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6823) Short-name config values

by Steve Ebersole (JIRA)

Short-name config values ------------------------ Key: HHH-6823 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6823 Project: Hibernate Core Issue Type: Improvement Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.1.0 The idea is to provide easier config as well as to isolate configurations from package moves as part of refactoring. * {{hibernate.transaction.jta.platform}} : Names the {{org.hibernate.service.jta.platform.spi.JtaPlatform}} to use. See {{org.hibernate.service.jta.platform.internal.JtaPlatformInitiator}}. For example, {{hibernate.transaction.jta.platform=JBossAS}} to name {{org.hibernate.service.jta.platform.internal.JBossAppServerJtaPlatform}}; etc * {{hibernate.dialect}} : Names the {{org.hibernate.dialect.Dialect}} * TBC... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5689) Updated data remains in 2L Cache after rollback

by Nikita Koksharov (JIRA)

Updated data remains in 2L Cache after rollback ----------------------------------------------- Key: HHH-5689 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5689 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.6.0, 3.5.6 Reporter: Nikita Koksharov Attachments: UpdatedDataTest.java, UpdatedItem.java For entities with Transactional caching strategy, updated data remains in 2L cache after transaction rollback. Please look at testcase. -- 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

11 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6315) Remove slf4j dependecy from gradle build

by Hardy Ferentschik (JIRA)

Remove slf4j dependecy from gradle build ---------------------------------------- Key: HHH-6315 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6315 Project: Hibernate Core Issue Type: Task Components: build Affects Versions: 4.0.0.Beta1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.0.0.next Slf4j is actually not used anymore, but needed by hibernate-commons-annotations. Once hibernate-commons-annotations is made obsolete we can remove the slf4j dependency. -- 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

11 years, 11 months

3
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3441) Null pointer exception on org.hibernate.type.AbstractType.getHashCode(AbstractType.java:112)

by DEROUET (JIRA)

Null pointer exception on org.hibernate.type.AbstractType.getHashCode(AbstractType.java:112) -------------------------------------------------------------------------------------------- Key: HHH-3441 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3441 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.25., Oracle 10g, Spring 2.5.5 Reporter: DEROUET Priority: Blocker The issue concerns a problem already signaled in different forums, and I decided to report it in JIRA, because many people have this same problem and after days and days of work around, the solutions possibles are heavy or dangerous for a database integrity (for example remove a non-nullability constraint...). Here it is the problem a previous forum participant had perfectly summarized (see http://opensource.atlassian.com/projects/hibernate/browse/HHH-2326): A null pointer exception is thrown when: a) we have a composite key with one of the attributes of the key being an FK to another persistent class. b) The other persistent class has an ID field whose value is being generated. c) The instance of the other persistent class is transient (does not yet have an ID) We do not get the null pointer if we explicitly set the ID (generator=assigned) Here it is the failure trace: --> --> java.lang.NullPointerException at org.hibernate.type.AbstractType.getHashCode(AbstractType.java:112) at org.hibernate.type.AbstractType.getHashCode(AbstractType.java:120) at org.hibernate.type.EntityType.getHashCode(EntityType.java:279) at org.hibernate.type.ComponentType.getHashCode(ComponentType.java:189) at org.hibernate.engine.EntityKey.generateHashCode(EntityKey.java:104) at org.hibernate.engine.EntityKey.<init>(EntityKey.java:48) at org.hibernate.engine.StatefulPersistenceContext.getDatabaseSnapshot(StatefulPersistenceContext.java:240) at org.hibernate.engine.ForeignKeys.isTransient(ForeignKeys.java:189) at org.hibernate.event.def.AbstractSaveEventListener.getEntityState(AbstractSaveEventListener.java:512) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:80) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSaveOrUpdate(SessionImpl.java:507) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:499) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:495) at org.springframework.orm.hibernate3.HibernateTemplate$16.doInHibernate(HibernateTemplate.java:747) at org.springframework.orm.hibernate3.HibernateTemplate.doExecute(HibernateTemplate.java:419) at org.springframework.orm.hibernate3.HibernateTemplate.executeWithNativeSession(HibernateTemplate.java:374) at org.springframework.orm.hibernate3.HibernateTemplate.saveOrUpdate(HibernateTemplate.java:744) at eu.cec.argus.bcm.dao.businessContinuityEvent.BusinessContinuityEventDAOImpl.createBCEvent(BusinessContinuityEventDAOImpl.java:39) at eu.cec.argus.bcm.dao.businessContinuityEvent.BusinessContinuityEventDAOTest.testSaveBcEventAndRelatedMessagesAndMeetings(BusinessContinuityEventDAOTest.java:127) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.springframework.test.context.junit4.SpringTestMethod.invoke(SpringTestMethod.java:198) at org.springframework.test.context.junit4.SpringMethodRoadie.runTestMethod(SpringMethodRoadie.java:274) at org.springframework.test.context.junit4.SpringMethodRoadie$2.run(SpringMethodRoadie.java:207) at org.springframework.test.context.junit4.SpringMethodRoadie.runBeforesThenTestThenAfters(SpringMethodRoadie.java:254) at org.springframework.test.context.junit4.SpringMethodRoadie.runWithRepetitions(SpringMethodRoadie.java:234) at org.springframework.test.context.junit4.SpringMethodRoadie.runTest(SpringMethodRoadie.java:204) at org.springframework.test.context.junit4.SpringMethodRoadie.run(SpringMethodRoadie.java:146) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.invokeTestMethod(SpringJUnit4ClassRunner.java:151) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:26) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:36) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Here they are my classes: @Entity @Table(name = "BCM_BC_EVENT") @IdClass(BusinessContinuityEvent.BusinessContinuityEventId.class) @SequenceGenerator(name = "Generator.BusinessContinuityEvent", sequenceName = "SEQ_BCM_BC_EVENT") public class BusinessContinuityEvent implements Serializable { @Embeddable public static class BusinessContinuityEventId implements Serializable { private static final long serialVersionUID = 3513299649110908676L; @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "Generator.BusinessContinuityEvent") @Column(name = "BCE_ID", insertable = false, updatable = false, nullable = false) private Long id; @ManyToOne(fetch = FetchType.LAZY, cascade = {CascadeType.PERSIST, CascadeType.REFRESH, CascadeType.MERGE}) @Cascade(org.hibernate.annotations.CascadeType.SAVE_UPDATE) @JoinColumn(name = "EVE_ID", referencedColumnName = "EVE_ID", nullable = false) private Event event; public BusinessContinuityEventId(){ } public BusinessContinuityEventId(Long id, Event event) { this.id = id; this.event = event; } public Long getId() { return id; } public void setId(Long id) { this.id = id; } public Event getEvent() { return event; } public void setEvent(Event event) { this.event = event; } @Override public boolean equals(Object obj) { if (obj instanceof BusinessContinuityEventId) { BusinessContinuityEventId other = (BusinessContinuityEventId) obj; return this.event.getId().equals(other.event.getId()) && this.id.equals(other.id); } return false; } @Override public int hashCode() { return this.event.getId().hashCode() ^ this.id.hashCode(); } } private static final long serialVersionUID = 5385009048448590115L; @Id private Long id; @Id private Event event; @OneToMany(fetch = FetchType.LAZY, cascade = {CascadeType.PERSIST, CascadeType.REFRESH, CascadeType.MERGE}) @Cascade(org.hibernate.annotations.CascadeType.SAVE_UPDATE) @JoinColumns({ @JoinColumn(name = "BCE_ID", referencedColumnName = "BCE_ID"), @JoinColumn(name = "EVE_ID", referencedColumnName = "EVE_ID")}) private List<Message> messages; public Long getId() { return id; } public void setId(Long id) { this.id = id; } public Event getEvent() { return event; } public void setEvent(Event event) { this.event = event; } public List<Message> getMessages() { return messages; } public void setMessages(List<Message> messages) { this.messages = messages; } } -- 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

11 years, 11 months

5
5
0 / 0

[Hibernate-JIRA] Created: (HHH-6549) ID and discrminator are nullable if a column attribute is supplied using HBM XML

by Gail Badner (JIRA)

ID and discrminator are nullable if a column attribute is supplied using HBM XML -------------------------------------------------------------------------------- Key: HHH-6549 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6549 Project: Hibernate Core Issue Type: Bug Components: metamodel Reporter: Gail Badner Assignee: Steve Ebersole Fix For: 4.0.0.next -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-6049) Improve error message about incompatible JDBC driver

by Sanne Grinovero (JIRA)

Improve error message about incompatible JDBC driver ---------------------------------------------------- Key: HHH-6049 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6049 Project: Hibernate Core Issue Type: Task Components: core Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.6.3 We should revert the workaround committed as part of (HHH-5642) Error configuring Hibernate with PostgreSQL JDBC3 8.2.511 driver and fail fast instead, with a good errormessage like "this jdbc driver compiled against jdk 1.3 or earlier..." -- 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

11 years, 11 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HSHARDS-57) For a better "virtual shards" support!

by Colbert Philippe (JIRA)

For a better "virtual shards" support! -------------------------------------- Key: HSHARDS-57 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-57 Project: Hibernate Shards Issue Type: Improvement Affects Versions: 3.0.0.Beta2 Environment: Windows XP Reporter: Colbert Philippe Assignee: Max Ross The current implementation of virtual shards leaves a lot to be desired when used in big corporate applications. A better way to model shards, is to identify a virtual shard by a pairing of "some name" + "an index" (example: Clients, 11). The name plays a role similar to namespaces. The index is always zero based and valid only within the namespace. There can be many shard namespaces with unique names. A configuration file (possibly XML) will map each virtual shard to a single physical shard. It's a simple mapping strategy. The mapping can allow overlaps of virtual shards into a single physical shard. This type of naming can make things more clear and easier to manage on the long-run. The big advantage to virtual shards over physical shards is that virtual shards can be easily persisted to file or database and retrieved again and still remain valid. Any change to the shard structure is fully controlled by the shard configuration file, without modifications to the persisted representation of the shard. This way the code can evolve separately from the physical shard architecture. With this kind of virtual shard, top-of-tree classes will map to a single shard namespace. The object will reside in any of the virtual shard indexes associated with the shard namespace. The resolution strategy becomes very simple because the set of shard indexes will be returned. -- 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

11 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3464) SimpleExpression.ignoreCase uses SQL server lowercase function for left part and JAVA lowercase function for right part of expression

by Vitaliy Tymchyshyn (JIRA)

SimpleExpression.ignoreCase uses SQL server lowercase function for left part and JAVA lowercase function for right part of expression ------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3464 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3464 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.6 Environment: tried with PostgreSQL Reporter: Vitaliy Tymchyshyn Priority: Minor When using SimpleExpression.ignoreCase (e.g. Restrictions.eq().ignoreCase, hibernate makes 'lower(field)=?' SQL expression, passing lowercased strings to '?' parameter. This may produce unpredictable results depending on Database server lower implementation and current JAVA locale (see JDK javadoc). For example, I've tried with '\u0130' character as in JDK JavaDoc. Postgresql produces: unhappy=> select lower('İ'); lower ------- i̇ (1 row) unhappy=> select char_length(lower('İ')); char_length ------------- 2 (1 row) While Java with default locale produces single-character 'i̇'. Of course the restriction will not work - it can not find 'İ' in database. I'd recommend to use 'lower(field)=lower(?)' to use same lower casing function for both parts of expression. -- 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

11 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (OGM-22) Support Session#list and JP-QL queries

by Emmanuel Bernard (JIRA)

Support Session#list and JP-QL queries -------------------------------------- Key: OGM-22 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-22 Project: Hibernate OGM Issue Type: New Feature Components: query Reporter: Emmanuel Bernard -- 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

11 years, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (JPA-15) Criteria API based on MapKeyColumn is not working

by Edwin Dalorzo (JIRA)

Criteria API based on MapKeyColumn is not working ------------------------------------------------- Key: JPA-15 URL: http://opensource.atlassian.com/projects/hibernate/browse/JPA-15 Project: Java Persistence API Issue Type: Bug Environment: Hibernate 3.6.1 MySQL 5.0 Reporter: Edwin Dalorzo Attachments: log.txt, src.zip I defined an Employee entity having a map of phone numbers, where the key is the type of phone (home, office, mobile) and the value is the phone number as a String. @ElementCollection(fetch=FetchType.LAZY) @CollectionTable(name="emp_phone") @MapKeyColumn(name="phone_type") @Column(name="phone_num") private Map<String, String> phoneNumbers; Then I tried to write a Criteria API query using a map join, like this: CriteriaBuilder builder = entityManager.getCriteriaBuilder(); CriteriaQuery<Employee> criteria = builder.createQuery(Employee.class); Root<Employee> employeeRoot = criteria.from(Employee.class); criteria.select(employeeRoot); MapJoin<Employee, String, String> phoneRoot = employeeRoot.joinMap("phoneNumbers"); criteria.where(builder.equal(phoneRoot.key(), "HOME")); System.out.println(entityManager.createQuery(criteria).getResultList()); You get an NullPointerException java.lang.NullPointerException at org.hibernate.ejb.criteria.path.AbstractPathImpl.prepareAlias(AbstractPathImpl.java:246) at org.hibernate.ejb.criteria.path.AbstractPathImpl.render(AbstractPathImpl.java:253) at org.hibernate.ejb.criteria.predicate.ComparisonPredicate.render(ComparisonPredicate.java:173) at org.hibernate.ejb.criteria.QueryStructure.render(QueryStructure.java:258) at org.hibernate.ejb.criteria.CriteriaQueryImpl.render(CriteriaQueryImpl.java:340) at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:223) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:441) at com.dalorzo.Main.main(Main.java:57) Exception in thread "main" java.lang.RuntimeException: java.lang.NullPointerException at com.dalorzo.Main.main(Main.java:64) Caused by: java.lang.NullPointerException at org.hibernate.ejb.criteria.path.AbstractPathImpl.prepareAlias(AbstractPathImpl.java:246) at org.hibernate.ejb.criteria.path.AbstractPathImpl.render(AbstractPathImpl.java:253) at org.hibernate.ejb.criteria.predicate.ComparisonPredicate.render(ComparisonPredicate.java:173) at org.hibernate.ejb.criteria.QueryStructure.render(QueryStructure.java:258) at org.hibernate.ejb.criteria.CriteriaQueryImpl.render(CriteriaQueryImpl.java:340) at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:223) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:441) at com.dalorzo.Main.main(Main.java:57) If you change the query to filter on value instead of key, it works just fine criteria.where(builder.equal(phoneRoot.value(), "88750372")); I have attached a log with exceptions as well as the Employee entity and the Main class containing a main method. Also, the code in question runs perfectly fine in EclipseLink. -- 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

11 years, 11 months

6
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2012