November 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6847) HibernateSearch DSL - excludeLimit()

by S M (JIRA)

HibernateSearch DSL - excludeLimit() ------------------------------------ Key: HHH-6847 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6847 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.2 Reporter: S M Priority: Minor As in HibernateCore 3.6.2 (with HibernateSearch 3.3.1) I found the following error: The class ConnectedMultiFieldsRangeQueryBuilder has to implement the method excludeLimit(), in which the border to be excluded is checked. The upper border is excluded correctly, but the lower border needs to be excluded with: rangeContext.setExcludeFrom(true) instead of rangeContext.setExcludeTo(true) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-951) excludeLimit() has no effect on QueryBuilder.range().above() queries

by Marko Lukša (JIRA)

excludeLimit() has no effect on QueryBuilder.range().above() queries -------------------------------------------------------------------- Key: HSEARCH-951 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-951 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 4.0.0.CR1, 3.4.1.Final Reporter: Marko Lukša Priority: Trivial When executing the following code, the {{excludeLimit()}} call has no effect. {code} Query query = queryBuilder .range() .onField("letter") .ignoreFieldBridge() .ignoreAnalyzer() .above("b").excludeLimit() .createQuery(); {code} It's caused by a minor bug in {{ConnectedMultiFieldsRangeQueryBuilder.excludeLimit()}}: {code} public RangeTerminationExcludable excludeLimit() { if ( rangeContext.getFrom() != null && rangeContext.getTo() != null ) { rangeContext.setExcludeTo( true ); } else if ( rangeContext.getFrom() != null ) { rangeContext.setExcludeTo( true ); <---- should be From, not To } else if ( rangeContext.getTo() != null ) { rangeContext.setExcludeTo( true ); } else { throw new AssertionFailure( "Both from and to clause of a range query are null" ); } return this; } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-6541) ColumnValues.applyColumnValues tests presence of uniqueValue but reads nameValue

by Erik Bertelsen (JIRA)

ColumnValues.applyColumnValues tests presence of uniqueValue but reads nameValue -------------------------------------------------------------------------------- Key: HHH-6541 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6541 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 4.0.0.Beta4 Environment: 4.0.0.Beta4, postgresql 9 Reporter: Erik Bertelsen In https://github.com/hibernate/hibernate-core/blob/master/hibernate-core/sr... in the method applyColumnValues, the following lines are present: AnnotationValue nameValue = columnAnnotation.value( "name" ); if ( nameValue != null ) { this.name = nameValue.asString(); } AnnotationValue uniqueValue = columnAnnotation.value( "unique" ); if ( uniqueValue != null ) { this.unique = nameValue.asBoolean(); } Note that this.unique is set from nameValue.asBoolean instead of the intended uniqueValue.asBoolean. This causes an IlleArgumentException (unless nameValue happens to be a valid boolean value). Only uniqueValue seems to be affected, the remaining properties look ok. Suggested fix: replace 'this.unique = nameValue.asBoolean();' by 'this.unique = uniqueValue.asBoolean();' Consequence of this bug: It is not possible to annotate a property of an entity class by: @Column(name = "someName", unique = true) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6522) NPE in JBoss 7 when using JTA

by Mike Huniewicz (JIRA)

NPE in JBoss 7 when using JTA ----------------------------- Key: HHH-6522 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6522 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.Beta4 Environment: Hibernate 4.0.0.Beta1 and 4.0.0.Beta4. JBoss 7 Reporter: Mike Huniewicz A NullPointerException occurs when resolving JTA transaction manager. Please see here for the stack trace: http://community.jboss.org/message/618455#618455 Caused by: java.lang.NullPointerException at org.hibernate.engine.transaction.internal.jta.JtaStatusHelper.getStatus(JtaStatusHelper.java:72) [hibernate-core-4.0.0.Beta1.jar:4.0.0.Beta1] I'm using Arquillian to build my WAR file to deploy it to JBoss 7 for testing. Here's my source code: https://github.com/m1key/audiolicious/tree/WithJBossIntegrationTests persistence.xml: https://github.com/m1key/audiolicious/blob/WithJBossIntegrationTests/audi... Data source is not XA. It seems that it did manage to connect to the data source because it tries to create tables. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6727) serializing an EntityManager should include enough information to later be unserialized with re-association to existing EntityManagerFactory (even on a different machine/jvm process)

by Scott Marlow (JIRA)

serializing an EntityManager should include enough information to later be unserialized with re-association to existing EntityManagerFactory (even on a different machine/jvm process) -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-6727 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6727 Project: Hibernate Core Issue Type: New Feature Components: entity-manager Reporter: Scott Marlow The re-association (of EM to EMF) is important, as applications expect that closing the EntityManagerFactory, will close the EntityManager's that have been opened from the EMF. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
14
0 / 0

[Hibernate-JIRA] Created: (HHH-6822) Split notions of (1) "naming" a SessionFactory and (2) specifying a JNDI name to which to bind it

by Steve Ebersole (JIRA)

Split notions of (1) "naming" a SessionFactory and (2) specifying a JNDI name to which to bind it ------------------------------------------------------------------------------------------------- Key: HHH-6822 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6822 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.1.0 Currently naming a {{SessionFactory}} and specifying the JNDI namespace into which Hibernate should bind it after creation are one-in-the-same. Ideally this should be split. The concept of a named {{SessionFactory}} is useful in quite a few situations internally (the JNDI binding is more end user focused). See {{org.hibernate.internal.SessionFactoryRegistry}}. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5882) JPA lazy Load problem on many-to-one property getter

by Leo Deng (JIRA)

JPA lazy Load problem on many-to-one property getter ---------------------------------------------------- Key: HHH-5882 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5882 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0 Environment: Windows 7, JDK 1.6 ,MySQL 5.5 Reporter: Leo Deng Priority: Critical Attachments: TestJPA.zip Hibernate could not work properly when I use lazy load in many-to-one situation.you can run the test case in attachment. I try to get primary-key property of parent object which get from child object property.Hibernate query the parent object from database by foreign key successfully. But when I try to use org.hibernate.property.Getter Interface to read some property, hibernate return null to me. My code in attachment can be described as follow: <1>Test function "TestEagerLoadManyToOne" using Eager load can pass the test. Code logic are: 1)Load Child object from database 2)Get "parentObj" property and test whether "parent_id" field in parent is NULL; 2)Use org.hibernate.property.Getter to get "parent_id" field and test the result. <2>Test function "TestLazyLoadManyToOne" do exactly same thing just like "TestEagerLoadManyToOne", but the "Child" class change "parentObj" property to lazy load mode. this test function could not pass. Please fix this issue. It's crucial to my project. -- 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

14 years, 3 months

4
8
0 / 0

[Hibernate-JIRA] Created: (HHH-6678) Update base jDocBook styles

by Steve Ebersole (JIRA)

Update base jDocBook styles --------------------------- Key: HHH-6678 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6678 Project: Hibernate Core Issue Type: Task Components: documentation Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.next {quote} For those projects still using the jbossorg-jdocbook-style dependency, you should consider upgrading your pom.xml files to reference the new pressgang-xslt style bundle. The jbossorg-jdocbook-style dependencies are no longer maintained. PressGang has taken over maintenance of these assets, with a big thanks to Geoffrey for improving the base styles considerably. At the moment, Geoffrey is doing the lion's share of this work and PressGang needs more shipmates to assist with this important work. If you have CSS skills, and a small amount of time to donate, I'd love to hear from you. You can get the required dependencies for your pom by investigating the pom.xml for the PressGang JBoss Documentation Guide. The new styles are used to give the JBoss Documentation Guide the look and feel. You can learn more about the styles here: http://www.jboss.org/pressgang/basestyles.html You can learn more about the JBoss Documentation Guide here: http://www.jboss.org/pressgang/jdg.html The direct link to the pom.xml config PressGang uses for the guide is here: http://svn.jboss.org/repos/pressgang/pressgang-documentation-guide/trunk/... Any questions? Please get in touch using the methods described on the PressGang pages listed above. PressGang is on IRC (freenode.org #PressGang) and Twitter (@PressGang). {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-6861) Test failures on OpenJDK 7

by Sanne Grinovero (JIRA)

Test failures on OpenJDK 7 -------------------------- Key: HHH-6861 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6861 Project: Hibernate Core Issue Type: Bug Reporter: Sanne Grinovero Fix For: 4.0.0.next Running the testsuite with {code} java version "1.7.0_b147-icedtea" OpenJDK Runtime Environment (fedora-2.0.3.fc16-x86_64) OpenJDK 64-Bit Server VM (build 21.0-b17, mixed mode){code} I'm having some failures: 2880 tests completed, 13 failures -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HCANN-9) Unable to reference JPA entity beans in a different package

by Krashan Brahmanjara (JIRA)

Unable to reference JPA entity beans in a different package ----------------------------------------------------------- Key: HCANN-9 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-9 Project: Hibernate Commons Annotations Issue Type: Bug Environment: Hibernate Annotations 3.4.0.GA in Jboss 5.1.0.GA Reporter: Krashan Brahmanjara Problem described in https://forum.hibernate.org/viewtopic.php?f=1&t=998404 Example Two classes test.jpa.db1.Card ant test.jpa.db2.Cards are in different packages in the same jar and @ManyToOne fails if deployed on Jboss server ... but it work if these clases are together in the same package. ... it not fails on Weblogic with OpenJpa Stack trace 09:53:37,609 ERROR [AbstractKernelController] Error installing to Start: name=persistence.unit:unitName=test-services-ear .ear/test-services-ejb-3.0.alfa-SNAPSHOT.jar#test-services-jpa state=Create org.hibernate.AnnotationException: @OneToOne or @ManyToOne on test.jpa.db1.Card.podm references an unknown ent ity: test.jpa.db2.Cards at org.hibernate.cfg.ToOneFkSecondPass.doSecondPass(ToOneFkSecondPass.java:81) at org.hibernate.cfg.AnnotationConfiguration.processEndOfQueue(AnnotationConfiguration.java:456) at org.hibernate.cfg.AnnotationConfiguration.processFkSecondPassInOrder(AnnotationConfiguration.java:438) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:309) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1148) at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1226) at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:173) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:854) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:425) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:131) at org.jbtest.jpa.deployment.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:301) 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:597) at org.jbtest.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59) at org.jbtest.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150) Tested workarounds, both doesn't work: - adding an orm.xml file with entries like: <entity>test.jpa.db1.Card</entity> <entity>test.jpa.db2.Cards</entity> - adding an hibernate extensions to class definition like: @Entity @org.hibernate.annotations.Entity @Table(name = "card") public class Card implements Serializable { -- 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

14 years, 3 months

5
9
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 2011