February 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5688) Migrate BytecodeProvider to be a Service

by Steve Ebersole (JIRA)

Migrate BytecodeProvider to be a Service ---------------------------------------- Key: HHH-5688 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5688 Project: Hibernate Core Issue Type: Task Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha1 This is deeply dependent upon the metamodel redesign completion. -- 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

12 years, 9 months

2
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-638) Limit graph traversal by @ContainedIn to the minimum required path

by Sanne Grinovero (JIRA)

Limit graph traversal by @ContainedIn to the minimum required path ------------------------------------------------------------------ Key: HSEARCH-638 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-638 Project: Hibernate Search Issue Type: Improvement Components: engine Affects Versions: 3.2.1, 3.2.0.Final, 3.1.1.GA, 3.1.0.GA, 3.3.0 Reporter: Sanne Grinovero Unit test available in the source tree since HSEARCH-513 org.hibernate.search.test.embedded.depth.RecursiveGraphTest, see the "FIXME" referring to this issue. It seems that @ContainedIn is now traversing the graph "upwards" towards any related entity it might find, without any limit; this happens to work pretty well in most simple use cases but becomes a performance problem in the more complex scenarios. -- 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

12 years, 9 months

2
10
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

12 years, 9 months

4
8
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

12 years, 9 months

5
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2907) ability to apply 'generation strategy' to generated properties

by Steve Ebersole (JIRA)

ability to apply 'generation strategy' to generated properties -------------------------------------------------------------- Key: HHH-2907 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2907 Project: Hibernate3 Issue Type: New Feature Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Priority: Minor Fix For: 3.3 Currently, the support for generated properties allows only for db-generated values (ala triggers etc). Would be great to allow the user to provide a seperate (optional) strategy for generating the generated values. It would be nice to have a generic solution, which we can build on top of for the more common use cases. Also, we may need to use a name other than 'generated' in the annotations to avoid conflicts with the current @Generated annotation; for now lets use the term @Dynamic. Consider mapping a 'created timestamp' column. Currently, provided we are using a trigger, that would look like: @Generated(INSERT) Date created; The strategy here (^^) is implicitly 'db', as the db is taking care of the generation. In the most generic form, that could be written as: @Dynamic(time=INSERT,strategy=DB) Date created; Additionally, since this is such a common case, also allow this: @CreationTimestamp Date created; The final form would also allow the definition of strategies. As an example, consider: @CreationTimestamp(strategy=NOW) Date created; Here we are not relying on the db to generate the value, but are explicitly telling Hibernate to do it (basically 'use the current timestamp to generate a value here whenever we do an insert'). -- 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

12 years, 9 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HHH-4521) Hibernate/Infinispan integration doesn't property handle Entity/CollectionRegionAccessStrategy evict(Object)

by Galder Zamarreno (JIRA)

Hibernate/Infinispan integration doesn't property handle Entity/CollectionRegionAccessStrategy evict(Object) ------------------------------------------------------------------------------------------------------------ Key: HHH-4521 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4521 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 3.5 Port HHH-4517 to Infinispan second level cache integration. -- 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

12 years, 9 months

3
12
0 / 0

[Hibernate-JIRA] Created: (HHH-4048) Phase 2 - implement rest of strategies

by Steve Ebersole (JIRA)

Phase 2 - implement rest of strategies -------------------------------------- Key: HHH-4048 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4048 Project: Hibernate Core Issue Type: Sub-task Reporter: Steve Ebersole Assignee: Steve Ebersole -- 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

12 years, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3800) Allow chopping of class names in various logging scenarios

by Steve Ebersole (JIRA)

Allow chopping of class names in various logging scenarios ---------------------------------------------------------- Key: HHH-3800 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3800 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Priority: Minor When logging enti ty class names, it would be nice to allow "collapsing" or "stripping" the entity name in various ways. Or when referencing Hibernate classes... -- 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

12 years, 9 months

1
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5223) Allow 2-phase load of components

by Steve Ebersole (JIRA)

Allow 2-phase load of components -------------------------------- Key: HHH-5223 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5223 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6 -- 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

12 years, 9 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5037) Improve documentation for immutable/read-only entity and immutable collection functionality

by Gail Badner (JIRA)

Improve documentation for immutable/read-only entity and immutable collection functionality ------------------------------------------------------------------------------------------- Key: HHH-5037 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5037 Project: Hibernate Core Issue Type: Improvement Components: documentation Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.0.Next -- 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

12 years, 9 months

3
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2011