September 2009 - hibernate-issues

[Hibernate-JIRA] Created: (HHH-4465) Document @Entity.name != Hibernate entity name

by Paul Benedict (JIRA)

Document @Entity.name != Hibernate entity name ---------------------------------------------- Key: HHH-4465 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4465 Project: Hibernate Core Issue Type: Improvement Components: documentation Affects Versions: 3.5.0.Beta-1, 3.3.2 Reporter: Paul Benedict Priority: Minor Only through stack tracing and Internet searching did I realize that JPA's @Entity.name does not equal Hibernate's entity name. The reference documentation does not make that knowledge explicit -- it's pretty important to know! Issues like HHH-2597 and HHH-4375 might indicate frequent head banging. Please add a line or two to highlight this difference and where it applies (e..g, queries). -- 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

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-236) Spring/Hibernate integration, and maven suggestions

by Ken Egervari (JIRA)

Spring/Hibernate integration, and maven suggestions --------------------------------------------------- Key: HV-236 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-236 Project: Hibernate Validator Issue Type: Improvement Components: documentation Affects Versions: 4.0.0.CR1 Environment: spring 3.0, hibernate 3.3.2, hibernate validator 4.0cr1 Reporter: Ken Egervari HI, I think it would a good idea to include an integration section on the documentation - a subsection on hibernate, an another subsection with spring. I'm sure jpa would be another. To set up a validation in spring, all one needs to do is this: <bean id="validationFactory" class="javax.validation.Validation" factory-method="buildDefaultValidatorFactory" /> <bean id="beanValidationEventListener" class="org.hibernate.cfg.beanvalidation.BeanValidationEventListener"> <constructor-arg index="0" ref="validationFactory" /> <constructor-arg index="1"> <props/> </constructor-arg> </bean> Now, I don't know what the second properties argument is for... sending it an empty properties seems to work. I guess if that is the ValidationMessages.properties file... then it already gets picked up in the person's resources directory. Since Spring is finicky if you specify the actual types, I think sharing this bean configuration would help people get moving on their projects faster. Let's face it, someone new to the library who can't find this info on google will spend hours. Let's give them a hand. I spent time doing it - let's now not make that time in vain and share with easily with people in the main documentation. To wire these beans into the sessionfactory in hibernate, this is all that needs to be done given the other bean definitions: <bean id="sessionFactory" class="org.springframework.orm.hibernate3.LocalSessionFactoryBean"> <property name="dataSource" ref="dataSource"/> <property name="eventListeners"> <map> <entry key="pre-insert" value-ref="beanValidationEventListener" /> <entry key="pre-update" value-ref="beanValidationEventListener" /> </map> </property> .... And then they can keep adding more properties for configuration properties, mappings and whatever else. This works. I hope sections like this appear in the documentation because really I want to do is help people, and make sure they don't have to go through what I went through to figure this out. I'm in huge favour of keeping things in 1 spot and spoon-feeding people. -- 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

2
4
0 / 0

[Hibernate-JIRA] Created: (HV-180) Failure when compiling Hibernate Validator

by Emmanuel Bernard (JIRA)

Failure when compiling Hibernate Validator ------------------------------------------ Key: HV-180 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-180 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.0.0.Beta1 Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik https://forum.hibernate.org/viewtopic.php?f=26&t=997514 Juergen, do you still have the issue? (check later tomorrow we are doing some API surgery today so it won't compile :) ) Yes, the issue still exists: 1) Using JDK 1.6_14 and implicitely JAXB 2.1.10 works fine 2) Using JDK 1.6_14 and JAXB 2.1.11 via the endorsed mechanism fails -- 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

2
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-4375) Consider implementing @Entity(name=) through entityName

by Paul Benedict (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4375?page=c... ] Paul Benedict commented on HHH-4375: ------------------------------------ Err. In my previous comment, I meant HHH-2597. > Consider implementing @Entity(name=) through entityName > ------------------------------------------------------- > > Key: HHH-4375 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4375 > Project: Hibernate Core > Issue Type: Improvement > Components: annotations > Reporter: Steve Ebersole > Priority: Minor > Attachments: ANN-303-patch.txt > > > I'm doubtful but this might be a solution > http://jroller.com/page/MikeSlattery?entry=workaround_for_entity_name_alias -- 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

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2597) Criteria API should handle entity aliases

by Emmanuel Bernard (JIRA)

Criteria API should handle entity aliases ----------------------------------------- Key: HHH-2597 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2597 Project: Hibernate3 Issue Type: Improvement Components: query-criteria Reporter: Emmanuel Bernard Priority: Minor HQL takes entity alias into account Criteria does not seem to do so "I'm trying to use @Entity(name="Test") to map a very simple pojo, but hibernate seems to ignore entity name, ie.: session.createCritirea("Test").list() throws "org.hibernate.MappingException: Unknown entity: Test" but session.createCritirea(myPojoClassName).list() works. " http://forum.hibernate.org/viewtopic.php?p=2350219 -- 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

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-391) Two-Level embedded objects don't get an index update

by Sven (JIRA)

Two-Level embedded objects don't get an index update ---------------------------------------------------- Key: HSEARCH-391 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-391 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.1.1.GA Reporter: Sven Priority: Minor refering to my post in the forum, i should write a jira issue: https://forum.hibernate.org/viewtopic.php?f=9&t=998709 -- 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

5
9
0 / 0

[Hibernate-JIRA] Created: (HHH-4464) PostgreSQLDialect does not support resultsets via stored procedures

by Hasitha Wijesekara (JIRA)

PostgreSQLDialect does not support resultsets via stored procedures ------------------------------------------------------------------- Key: HHH-4464 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4464 Project: Hibernate Core Issue Type: Improvement Components: query-sql Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga , PostgreSQL 8.3 Reporter: Hasitha Wijesekara Attachments: PostgreSQLDialect-Issue.bmp When executing PostgreSQL function following error occurred. org.hibernate.dialect.PostgreSQLDialect does not support resultsets via stored procedures. But when we execute same function using MySQL5Dialect, this error does not occur. We use following NamedQuery for that, <sql-query name="callFunction" callable="true"> {call visualdata.getEmpFullName(100) } </sql-query> -- 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

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-4375) Consider implementing @Entity(name=) through entityName

by Paul Benedict (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4375?page=c... ] Paul Benedict commented on HHH-4375: ------------------------------------ This is the Hibernate Annotations 3.4 code starting at line 154: 154 public void bindEntity() { 155 persistentClass.setAbstract( annotatedClass.isAbstract() ); 156 persistentClass.setClassName( annotatedClass.getName() ); 157 persistentClass.setNodeName( name ); 158 //persistentClass.setDynamic(false); //no longer needed with the Entity name refactoring? 159 persistentClass.setEntityName( annotatedClass.getName() ); The last line is where Hibernate could be enhanced to take the proposed @o.h.a.Entity name. Like HHH-4375, I am not a fan of automatically naming the Hibernate name through EJB annotations. I think it should be explicitly done. > Consider implementing @Entity(name=) through entityName > ------------------------------------------------------- > > Key: HHH-4375 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4375 > Project: Hibernate Core > Issue Type: Improvement > Components: annotations > Reporter: Steve Ebersole > Priority: Minor > Attachments: ANN-303-patch.txt > > > I'm doubtful but this might be a solution > http://jroller.com/page/MikeSlattery?entry=workaround_for_entity_name_alias -- 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

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-4375) Consider implementing @Entity(name=) through entityName

by Paul Benedict (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4375?page=c... ] Paul Benedict commented on HHH-4375: ------------------------------------ At least Hibernate's custom @Entity annotation should allow the Hibernate name to be specified. There doesn't seem to be any equivalent of the hbm's entity-name attribute when using annotation-only metadata. > Consider implementing @Entity(name=) through entityName > ------------------------------------------------------- > > Key: HHH-4375 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4375 > Project: Hibernate Core > Issue Type: Improvement > Components: annotations > Reporter: Steve Ebersole > Priority: Minor > Attachments: ANN-303-patch.txt > > > I'm doubtful but this might be a solution > http://jroller.com/page/MikeSlattery?entry=workaround_for_entity_name_alias -- 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

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4463) Native queries should not be automatically paginated in getSingleResult() as it fails for some DB and or queries

by Emmanuel Bernard (JIRA)

Native queries should not be automatically paginated in getSingleResult() as it fails for some DB and or queries ---------------------------------------------------------------------------------------------------------------- Key: HHH-4463 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4463 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0.Beta-1 Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 3.5 -- 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

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2009