August 2006 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-408) map a entity to integer map is not possible

by Armin Haaf (JIRA)

map a entity to integer map is not possible ------------------------------------------- Key: ANN-408 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-408 Project: Hibernate Annotations Type: Bug Versions: 3.2.0.cr1 Reporter: Armin Haaf It is not possible to map a entity to integer map: Map<MyClass, Integer> myMap; -- 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

18 years, 2 months

2
7
0 / 0

[Hibernate-JIRA] Created: (EJB-219) Add an EntityManagerFactory.getCurrentEntityManager() method.

by James Olsen (JIRA)

Add an EntityManagerFactory.getCurrentEntityManager() method. ------------------------------------------------------------- Key: EJB-219 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-219 Project: Hibernate Entity Manager Type: New Feature Components: EntityManager Environment: Hibernate 3.2. Any/All. Reporter: James Olsen BACKGROUND I'd like to code against the JPA standard, however my current EJB container vendor (like many others) is only providing JPA support as part of their EJB3 rollout which is at a very early stage. JPA doesn't need a full EJB3 environment. The only required apsect that appears to be missing in existing EJB containers is container management and injection of a correctly scoped EntityManager. I can deal with the injection problem by having a Singleton accessor for the EntityManagerFactory in much the same way as the well known HibernateUtil deals with the SessionFactory. All that is left then is providing something similar to the automatic JTA/CMT context scoping of Sessions for EntityManager instances. SUGGESTION I would propose that a new custom API be added to org.hibernate.ejb.EntityManagerFactoryImpl in the form of a method called getCurrentEntityManager(). Internally this would construct an EntityManagerImpl that was configured to do sessionFactory.getCurrentSession() rather than sessionFactory.openSession() (inside the getRawSession() method), thereby leveraging Hibernates pre-existing capability to return correctly scoped units of work in a JTA/CMT environment. Thats sounds easy, but maybe there's more to it!? JUSTIFICATION The advantage of having such an API is that we can write to the JPA API without waiting for full EJB3 support in the container. The little bit of application code to obtain the EntityManagerFactory, cast to the Hibernate impl and call this custom method can easily be removed in the future when EntityManager injection is available. I've looked at using Spring and Pitchfork but as great as they are, they are heavy handed when you already have a container and my customer demands a container and also has an aversion to non GA code (implies I'm confident the Hibernate 3.2 products will be GA soon - which I am!). -- 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

18 years, 3 months

3
5
0 / 0

[Hibernate-JIRA] Created: (EJB-212) excludeUnlistedClasses ignored in SE case

by Emmanuel Bernard (JIRA)

excludeUnlistedClasses ignored in SE case ----------------------------------------- Key: EJB-212 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-212 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.2.0.cr1 Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Fix For: 3.2.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

18 years, 3 months

2
6
0 / 0

[Hibernate-JIRA] Created: (ANN-428) Entity listener documentation contradicts EJB3 specification

by Koda Janh (JIRA)

Entity listener documentation contradicts EJB3 specification ------------------------------------------------------------ Key: ANN-428 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-428 Project: Hibernate Annotations Type: Bug Components: documentation Versions: 3.2.0.cr1 Reporter: Koda Janh Priority: Minor As discussed at http://forum.hibernate.org/viewtopic.php?p=2320577 the documentation contradicts the EJB3 specification with regards to method accessibility of entity listeners. Please fix the doc :) -- 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

18 years, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (EJB-215) EntityManager fails during transaction commit after it has been closed

by Barry Kaplan (JIRA)

EntityManager fails during transaction commit after it has been closed ---------------------------------------------------------------------- Key: EJB-215 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-215 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.2.0.cr1 Reporter: Barry Kaplan As per the JPA spec, an EntityManager should be closable prior to the end of the transaction. At least in the scenario where an exception is thrown during commit, AbstractEntityManagerImpl will attempt to mark the transaction rollback only, but in doing so it will access the Session. The session checks if it is closed, and if so throws an exception. There may be other scenarios where closing the EM prior to transaction end cause incorrect failures. For some background, there are two threads of discussion for this problem: - http://forum.hibernate.org/viewtopic.php?t=963262 - http://opensource.atlassian.com/projects/spring/browse/SPR-2412 -- 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

18 years, 3 months

2
10
0 / 0

[Hibernate-JIRA] Created: (HBX-728) Patch for hbm2dao "No signature of method getJavaTypeName matches (java.lang.Object,java.lang.Boolean) "

by Jacob Bergoo (JIRA)

Patch for hbm2dao "No signature of method getJavaTypeName matches (java.lang.Object,java.lang.Boolean) " -------------------------------------------------------------------------------------------------------- Key: HBX-728 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-728 Project: Hibernate Tools Type: Patch Components: reverse-engineer Versions: 3.2beta6 Environment: Hibernate tools beta6, Eclipse 3.2, Ant 1.6.5, Windows XP, Hibernate 3.1 Reporter: Jacob Bergoo This is the fix for this error message: [hibernatetool] Executing Hibernate Tool with a Standard Configuration [hibernatetool] 1. task: hbm2dao (Generates a set of DAOs) [hibernatetool] log4j:WARN No appenders could be found for logger (org.hibernate.cfg.Environment). [hibernatetool] log4j:WARN Please initialize the log4j system properly. [hibernatetool] An exception occurred while running exporter #2:hbm2dao (Generates a set of DAOs) [hibernatetool] To get the full stack trace run ant with -verbose [hibernatetool] org.hibernate.tool.hbm2x.ExporterException: Error while processing template daohome.ftl [hibernatetool] freemarker.template.TemplateModelException: No signature of method getJavaTypeName matches (java.lang.Object,java.lang.Boolean) to fix this you need to edit your dao templates you are using to generate the code. For the method findById() you have a if statement <#if clazz.identifierProperty> simply change this one to: <#if clazz.identifierProperty?has_content> and it should work. -- 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

18 years, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HBX-726) typo in Hibernate Tools reference manual

by Yuji Yamano (JIRA)

typo in Hibernate Tools reference manual ---------------------------------------- Key: HBX-726 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-726 Project: Hibernate Tools Type: Patch Components: doc Reporter: Yuji Yamano Priority: Trivial Attachments: diff I found some typos in Hibernate Tools reference manual. I attached the patch to fix them. -- 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

18 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-1986) javassist throws InvocationTargetException instead of original checked Exception

by Anthony Patricio (JIRA)

javassist throws InvocationTargetException instead of original checked Exception -------------------------------------------------------------------------------- Key: HHH-1986 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1986 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2 Reporter: Anthony Patricio Attachments: javassistTest.zip The javassist causes a problem if you have a hibernate persisted object which throws checked exceptions in some of his methods. In your code you have a try/catch for the checked exception around the method call. But if it is a proxy enhanced by javassist it won't throw the checked exception but an InvocationTargetException which is wrapped around the checked exception. So actually javassist should catch the InvocationTargetException and rethrown it's cause. The same bug was reported for cglib, see HHH-911 -- 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

18 years, 3 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2042) Typo in FlushMode.MANUAL Javadoc

by Koda Janh (JIRA)

Typo in FlushMode.MANUAL Javadoc -------------------------------- Key: HHH-2042 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2042 Project: Hibernate3 Type: Improvement Components: documentation Versions: 3.2.0.cr4 Reporter: Koda Janh Priority: Trivial The Javadoc for FlushMode.MANUAL reads "The Session is onyl eve flushed when flush()..." I believe you need to replace "onyl" by "only" and "eve" by "ever" -- 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

18 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (EJB-211) JavaDoc the EJB 3 API

by Emmanuel Bernard (JIRA)

JavaDoc the EJB 3 API --------------------- Key: EJB-211 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-211 Project: Hibernate Entity Manager Type: Improvement Components: Documentation Versions: 3.2.0.cr1 Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Priority: Minor Fix For: 3.2.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

18 years, 3 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2006