May 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Commented: (HHH-1851) relax special handling of 'id' property

by Sanne Grinovero (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1851?page=c... ] Sanne Grinovero commented on HHH-1851: -------------------------------------- please have Projections.id() return the identifier, whatever it is called. > relax special handling of 'id' property > --------------------------------------- > > Key: HHH-1851 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1851 > Project: Hibernate Core > Issue Type: Improvement > Components: query-hql > Environment: independent, all versions all databases. > Reporter: Gunther Schadow > Assignee: Steve Ebersole > Fix For: 3.5 > > Attachments: IdClassAndAnotherPropertyNamedId.zip > > > Hibernate has long treated 'id' in a special manner in HQL and Criteria queries. The drawback to this has always been that it effectively means users cannot define non-identifier properties named id and refer to those properties in HQL/Criteria queries. > Thus, I will change this such that: > (1) 'id' can still be used to refer to the identifier property, whatever the property's actual name, as long as the entity does not define a non-identitifer property named id. > (2) if the entity defines a non-identifier property named 'id', using 'id' in HQL or Criteria queries will refer to this non-identifier property; users would need to refer to the identifier property by its actual name. > FYI, the original reason for this feature was to support entity's which did not define an identifier property at all (users were responsible for managing the ids seperately. That feature was never really recommended and has been deprecated since early in the 3.x development. -- 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

15 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-159) NullPointerException in ValidatorFactoryImpl, if XML config file doesn't contain at least one constraint and one cascade configuration

by Gunnar Morling (JIRA)

NullPointerException in ValidatorFactoryImpl, if XML config file doesn't contain at least one constraint and one cascade configuration -------------------------------------------------------------------------------------------------------------------------------------- Key: HV-159 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-159 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.0.0.Beta1 Reporter: Gunnar Morling Attachments: hv-bugscenario.zip When using the XML based approach for constraint configuration, I get - a NullPointerException in ValidatorFactoryImpl, line 98, if I don't have at least one constraint configuration declared such as <field name="orderDate"> <constraint annotation="javax.validation.constraints.Past"> <message>Some overridden message.</message> </constraint> </field> - a NullPointerException in ValidatorFactoryImpl, line 100, if I don't have at least one cascade configuration declared such as <field name="orderLines"> <valid/> </field> The attached project demonstrates the problem. By uncommenting the two field elements in src/main/resources/META-INF/validation/order-constraints.xml the test will run successfully. -- 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

15 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HV-133) Create test baseclass to allow test to run w and w/o xml configuration

by Hardy Ferentschik (JIRA)

Create test baseclass to allow test to run w and w/o xml configuration ---------------------------------------------------------------------- Key: HV-133 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-133 Project: Hibernate Validator Issue Type: Task Components: engine Affects Versions: 4.0.0.Alpha3 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.0.0.Beta1 We need some sort of framework to run tests with and without xml configuration. Maybe just extend TestUtil? -- 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

15 years, 10 months

1
4
0 / 0

[Hibernate-JIRA] Created: (ANN-836) Availability of @CollectionId in Maps

by Vlasov Igor (JIRA)

Availability of @CollectionId in Maps ---------------------------------------- Key: ANN-836 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-836 Project: Hibernate Annotations Issue Type: Improvement Affects Versions: 3.4.0.GA Reporter: Vlasov Igor Hello, I have table user( id number(10) name varchar(50) ) and table user_right( id number(10) name varchar(50) key varchar(50) ) then i want to tie together "user" and "user_right" in table: rl_user_right( rl_id number(10) usr_id number(10) ur_id number(10) ) I can do this in such manner @OneToMany(fetch = FetchType.LAZY) @JoinTable(name = "rl_user_right", joinColumns = @JoinColumn(name = "usr_id"), inverseJoinColumns = @JoinColumn(name = "ur_id")) @CollectionId(columns = @Column(name = "rl_id"), type = @org.hibernate.annotations.Type(type = "long"), generator = "identity") @org.hibernate.annotations.Fetch(org.hibernate.annotations.FetchMode.SUBSELECT) private List<UserRight> rights; BUT i want to have property of Map type : private Map<String,UserRight> rights; with "key" value =user_right.key I try to do : @OneToMany(fetch = FetchType.LAZY) @JoinTable(name = "rl_user_right", joinColumns = @JoinColumn(name = "usr_id"), inverseJoinColumns = @JoinColumn(name = "ur_id")) @javax.persistence.MapKey(name="ur_key") @CollectionId(columns = @Column(name = "rl_id"), type = @org.hibernate.annotations.Type(type = "long"), generator = "identity") @org.hibernate.annotations.Fetch(org.hibernate.annotations.FetchMode.SUBSELECT) private Map<String,UserRight> rights; Then i catch an exception Map do not support @CollectionId: com.entity.User.rights; org.hibernate.cfg.annotations.CollectionBinder.getCollectionBinder ..... if ( java.util.Map.class.equals( returnedClass ) ) { if ( property.isAnnotationPresent( CollectionId.class ) ) { throw new AnnotationException( "Map do not support @CollectionId: " + StringHelper.qualify( entityName, property.getName() ) ); } return new MapBinder(); } How can I achieve my desire with another way? May be allow @CollectionId in Maps? -- 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

15 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-162) XML based configuration should be tolerant to line breaks and white spaces where appropriate

by Gunnar Morling (JIRA)

XML based configuration should be tolerant to line breaks and white spaces where appropriate -------------------------------------------------------------------------------------------- Key: HV-162 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-162 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.0.0.Beta1 Reporter: Gunnar Morling Priority: Minor When using the XML based configuration approach, unnecessary line breaks can cause some trouble. Eclipse formatted a config file of mine as follows: ... <default-package>org.hibernate.validation.bugscenario </default-package> <bean class="Order" ignore-annotations="false"> ... which leads to a ClassNotFoundException: java.lang.ClassNotFoundException: org.hibernate.validation.bugscenario .Order (note the line break after the package name), that is caught in XmlMappingParser, line 558 and rethrown as ValidationException. The problem goes away, if I format the package name as follows: <default-package>org.hibernate.validation.bugscenario</default-package> To make the XML based configuration more robust, trimming Strings such as the package name could be considered. This could be achieved by leveraging JAXB's CollapsedStringAdapter (https://jaxb.dev.java.net/nonav/2.1.11/docs/api/javax/xml/bind/annotation...). -- 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

15 years, 10 months

2
4
0 / 0

[Hibernate-JIRA] Created: (EJB-439) Query.getSingleResult fails if a sored proc is used

by Lloyd Fernandes (JIRA)

Query.getSingleResult fails if a sored proc is used --------------------------------------------------- Key: EJB-439 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-439 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.4.0.GA Environment: Hibernate core 3.3.1 Reporter: Lloyd Fernandes If you use Query.getSingleResult() on a named query that results in a stored proce call, the query is changed from {call usp_RequestState_Get (:requestID ) } to {call usp_RequestState_Get (? ) } to {call usp_Requ top 2estState_Get (? ) } in (org.hibernate.loader.Loader.prepareQueryStatement() line 1557) Code was working for 3.3.2 Looks like this was broken/incorrectly implemented earlier (than 3.3.2) but exasperated by the recent change to org.hibernate.ejb.QueryImpl.getSingleResult() that forces a maxResult to 2. I think the correct fix will be to not insert the limit statement (Loader.java line 15557) if the sql query does not start with a select call or if it is marked callable -- 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

15 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-354) Add indexAll method to FullTextSession

by Marcel Overdijk (JIRA)

Add indexAll method to FullTextSession -------------------------------------- Key: HSEARCH-354 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-354 Project: Hibernate Search Issue Type: Improvement Reporter: Marcel Overdijk To index all entities by a manual loop it would be more consistent to add an indexAll(Class<T> entityType) method. Just like there is a purgeAll method already. {code} FullTextSession fullTextSession = Search.getFullTextSession(session); Transaction tx = fullTextSession.beginTransaction(); List books = session.createQuery("from Book as book").list(); for (Book book : books) { fullTextSession.index(book); } tx.commit(); //index is written at commit time {code} -- 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

15 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-835) ManyToMany from and to the same object by using a non primary key column

by Frank Pfleger (JIRA)

ManyToMany from and to the same object by using a non primary key column ------------------------------------------------------------------------ Key: ANN-835 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-835 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Core 3.3.1.GA, Annotations 3.4.0, Postgres 8.3, JBoss 4.2.3 JDK6, Seam 2.1.1.GA Reporter: Frank Pfleger A ManyToMany relationship to the same table and the same property produces a MappingException on JBoss startup. Caused by: org.hibernate.MappingException: Duplicate property mapping of _org_weazel_security_entity_impl_Group_groups found in org.weazel.security.entity.impl.Group at org.hibernate.mapping.PersistentClass.checkPropertyDuplication(PersistentClass.java:477) at org.hibernate.mapping.PersistentClass.validate(PersistentClass.java:467) at org.hibernate.mapping.RootClass.validate(RootClass.java:215) at org.hibernate.cfg.Configuration.validate(Configuration.java:1135) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1320) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669) ... 145 more An Example Annotation that works fine between different tables and objects (NUMBER is a non primary key column/property) @ManyToMany @JoinTable(joinColumns=@JoinColumn(name="NUMBER1", referencedColumnName="NUMBER")), inverseJoinColumns=@JoinColumn(name="NUMBER2", referencedColumnName="NUMBER")) Using this Annotation between different classes works fine as said before. The Problem is the syntheticPropertyName (_org_weazel_security_entity_impl_Group_groups) generated in BinderHelper.createSyntheticPropertyReference which is the same for both parts/ends of the ManyToMany relationship. -- 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

15 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-575) Able to add meta information on the reveng.xml file (common configuration for all renerated classes)

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-575?page=co... ] Max Rydahl Andersen commented on HBX-575: ----------------------------------------- create a patch, create a jira and attach the patch to the jira. Then we can look. > Able to add meta information on the reveng.xml file (common configuration for all renerated classes) > ---------------------------------------------------------------------------------------------------- > > Key: HBX-575 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-575 > Project: Hibernate Tools > Issue Type: Improvement > Components: reverse-engineer > Affects Versions: 3.1beta4 > Reporter: David Leal > Fix For: 3.2beta9 > > Attachments: svn-patch2.txt > > > Just to add the posibility to set some meta information common to all possible generated *.hbm files, for example to set that ALL generated file will implement toString method or equal/hash code. > A good solution whoud be to add some filter options in order to speficy the set of Tables it would apply, using regular expresion, like include nestede target from ant. Something like this: > <meta attribute name="theAttributeName" value="theValue"> > <include name="theListOfTableToInclude"/> > <exlude name="theListOfTablesToExclude"> > </meta> > If it is more complicated just to add the possibility to add meta information for all possible generated files. -- 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

15 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-369) typos in documentation

by Sanne Grinovero (JIRA)

typos in documentation ---------------------- Key: HSEARCH-369 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-369 Project: Hibernate Search Issue Type: Improvement Components: documentation Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Trivial Fix For: 3.1.1, 3.2.0 Running a spellchecker on documentation reveals some flaws.. -- 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

15 years, 10 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2009