June 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HCANN-26) Possible NPE in MapBinder.bindKeyFromAssociationTable if @JoinColumn not present

by Sergey Vladimirov (JIRA)

Possible NPE in MapBinder.bindKeyFromAssociationTable if @JoinColumn not present -------------------------------------------------------------------------------- Key: HCANN-26 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-26 Project: Hibernate Commons Annotations Issue Type: Bug Affects Versions: 3.1.0.GA Reporter: Sergey Vladimirov Priority: Minor NPE can occur in MapBinder.bindKeyFromAssociationTable if @JoinColumn not present java.lang.NullPointerException org.hibernate.cfg.annotations.MapBinder.bindKeyFromAssociationTable(MapBinder.java:161) org.hibernate.cfg.annotations.MapBinder.access$000(MapBinder.java:77) org.hibernate.cfg.annotations.MapBinder$1.secondPass(MapBinder.java:111) org.hibernate.cfg.CollectionSecondPass.doSecondPass(CollectionSecondPass.java:66) org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1221) org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:383) org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1206) org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1449) org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:193) org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:1077) org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:868) mapKeyType = property.getMapKey().getName(); Hibernate should check if annotation/mapkey specified and throw human-friendly exception, not NPE. -- 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

13 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HCANN-25) Can't have an @Formula attribute in an @EmbeddedId

by Nicholas White (JIRA)

Can't have an @Formula attribute in an @EmbeddedId -------------------------------------------------- Key: HCANN-25 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-25 Project: Hibernate Commons Annotations Issue Type: Bug Affects Versions: 3.2.0 Reporter: Nicholas White If a class that will be used as an embedded id has a column that is defined by an @Formula attribute, hibernate throws a NPE. This is because the below method in org.hibernate.cfg.Ejb3Column doesn't check if the mappingColumn is null (which it is when the column is defined by a formula) before dereferencing it. public void forceNotNull() { mappingColumn.setNullable( false ); } To fix, change the method to: public void forceNotNull() { if (mappingColumn != null) { mappingColumn.setNullable( false ); } } -- 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

13 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-713) hbm2java task: meta support needed for class level annotations

by Anand Mahajan (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-713?page=co... ] Anand Mahajan commented on HBX-713: ----------------------------------- Is the solution to this problem released in any of the hiberante distributions? I want to place certain custom annotations in the hbm2java generated classes so that I can generate Flex Data Transfer object classes (Action Script classes) out of Hibernate entity classes using an DTO2fx Annotations processor. > hbm2java task: meta support needed for class level annotations > -------------------------------------------------------------- > > Key: HBX-713 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-713 > Project: Hibernate Tools > Issue Type: Bug > Components: hbm2java > Affects Versions: 3.2beta6 > Environment: hibernate tools 3.2 beta 6 > JBoss 4.0.4.GA with EJB3 > Reporter: Daniel Pocock > Attachments: class-annotations.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > We use hbm2java to create EJB3 entity beans from hbm files. It would be really useful to use the `meta' element to insert additional class level annotations. Is someone already working on such a feature, or should I submit a patch? > Here is an example of what I would like to do: > <meta attribute="extra-import">org.jboss.seam.annotations.Name</meta> > <meta attributre="class-annotation">@Name("myObject")</meta> > such that the following code would be generated: > import javax.ejb.Entity; > import org.jboss.seam.annotations.Name; > @Entity > @Name("myObject") > public class MyObject .... -- 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

13 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-330) Add a new constructor to ResourceBundleMessageInterpolator which enable/disables internal message caching

by Hardy Ferentschik (JIRA)

Add a new constructor to ResourceBundleMessageInterpolator which enable/disables internal message caching --------------------------------------------------------------------------------------------------------- Key: HV-330 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-330 Project: Hibernate Validator Issue Type: Task Components: engine Affects Versions: 4.1.0.Beta1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.1.0.Beta2 See also https://forum.hibernate.org/viewtopic.php?f=9&t=1004915 -- 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

13 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5285) Add support for CompositeUserType to implement org.hibernate.usertype.LoggableUserType

by Steve Ebersole (JIRA)

Add support for CompositeUserType to implement org.hibernate.usertype.LoggableUserType -------------------------------------------------------------------------------------- Key: HHH-5285 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5285 Project: Hibernate Core Issue Type: Improvement Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6 Add support for CompositeUserType to implement org.hibernate.usertype.LoggableUserType -- 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

13 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5262) Allow UserType and CompositeUserType to be registered with BasicTypeRegistry

by Steve Ebersole (JIRA)

Allow UserType and CompositeUserType to be registered with BasicTypeRegistry ---------------------------------------------------------------------------- Key: HHH-5262 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5262 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6 The implication here is that CustomType and CompositeCustomType need to (1) derive from the BasicType interface and (2) allow the user to configure the registration keys. 2 options for registration keys: # new (optional) interface, RegisterableUserType # allow passing the keys during registration via Configuration -- 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

13 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5268) Support for java.util.UUID properties/generators

by Steve Ebersole (JIRA)

Support for java.util.UUID properties/generators ------------------------------------------------ Key: HHH-5268 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5268 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.x See discussion on dev mailing list : http://lists.jboss.org/pipermail/hibernate-dev/2010-May/005209.html -- 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

13 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-329) Update quickstart section and remove reference to archetype catalog

by Hardy Ferentschik (JIRA)

Update quickstart section and remove reference to archetype catalog ------------------------------------------------------------------- Key: HV-329 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-329 Project: Hibernate Validator Issue Type: Bug Components: documentation Affects Versions: 4.1.0.Beta1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.1.0 Currently we don't have the archetype catalog deployed on the new JBoss nexus repository -- 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

13 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-328) Configuration.addMapping( null ) should throw IllegalArgumentException

by Hardy Ferentschik (JIRA)

Configuration.addMapping( null ) should throw IllegalArgumentException ---------------------------------------------------------------------- Key: HV-328 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-328 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.1.0.Beta1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.1.0 -- 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

13 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-1989) Deleted object remains referenced in 2nd level cache collections

by Justin Haddad (JIRA)

Deleted object remains referenced in 2nd level cache collections ---------------------------------------------------------------- Key: HHH-1989 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1989 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2 Environment: Spring 1.2.8, Hibernate 3.2, Postgres 8.0.3 Reporter: Justin Haddad This problem seems identical to issue NH-678. I have enabled caching for an one-to-many association. I use Ehcache. I have a test in which I load the parent object along with its collection. Both the parent and the collection wind up in the 2nd level cache. I then delete an object that is in the collection, not by removing it from the collection, but rather by doing a delete on the object itself. After deleting, I try to reload the parent and get the following exception (User#3102 is the deleted object): aused by: org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.bluenotenetworks.common.management.sm.User#3102] at org.hibernate.impl.SessionFactoryImpl$1.handleEntityNotFound(SessionFactoryImpl.java:372) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:128) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:178) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:86) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:871) at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:839) at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:266) at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:177) at org.hibernate.collection.PersistentSet.initializeFromCache(PersistentSet.java:101) at org.hibernate.cache.entry.CollectionCacheEntry.assemble(CollectionCacheEntry.java:35) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.initializeCollectionFromCache(DefaultInitializeCollectionEventListener.java:130) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:48) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1705) (continues on) I stepped through the code in the debugger and can see that the object's ID (3102 in this case) remains in the cached collection even after the deletion. -- 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

13 years, 11 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2010