July 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2579) scope bytecode provider selection to session factory

by Steve Ebersole (JIRA)

scope bytecode provider selection to session factory ---------------------------------------------------- Key: HHH-2579 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2579 Project: Hibernate3 Issue Type: Improvement Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: cfg-rework currently this is one of those "static" config params (classloader wide). -- 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, 8 months

1
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2484) Introduce NamingStrategy.getDefaultEntityName(String className)

by Emmanuel Bernard (JIRA)

Introduce NamingStrategy.getDefaultEntityName(String className) --------------------------------------------------------------- Key: HHH-2484 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2484 Project: Hibernate3 Type: Improvement Components: core Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Priority: Minor Fix For: 3.3 -- 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, 8 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-1976) NamingStrategy.classToTableName receives only class name, not a fully qualified name as stated in javadoc

by Lóránt Pintér (JIRA)

NamingStrategy.classToTableName receives only class name, not a fully qualified name as stated in javadoc --------------------------------------------------------------------------------------------------------- Key: HHH-1976 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1976 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3, 3.2.0.cr2 Reporter: Lóránt Pintér I have a custom NamingStrategy that overrides classToTableName in EJB3NamingStrategy. Prior to upgrading to Hibernate 3.1.3, my NamingStrategy implementation received the correct classnames as documented in the javadoc at http://www.hibernate.org/hib_docs/v3/api/org/hibernate/cfg/NamingStrategy... Since then, it only receives the name of the class without the package specification. I tried upgrading to 3.2.0.cr2, but it didn't help. -- 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, 8 months

9
15
0 / 0

[Hibernate-JIRA] Created: (HHH-2150) There are too many columns in the select statement with the Criteria API

by Slawek Trybus (JIRA)

There are too many columns in the select statement with the Criteria API ------------------------------------------------------------------------ Key: HHH-2150 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2150 Project: Hibernate3 Type: Improvement Components: query-criteria Versions: 3.2.0.ga Environment: Hibernate 3.2.0.cr2 PostgreSQL 8.1.3 Reporter: Slawek Trybus Using Criteria API brings on enclosing all columns from joined tables in generated select statement. It has big efficiency impact on DB especially if there are many joined tables (with many columns each) in a query. There is columns' limitation possible with the Projections API usage, but it makes received objects not fully fledged Hibernate entity objects. It would be good to have posibility to limit amount of columns in select statement to ones connected to entity we are interested in. There is available short discusion about this issue in the forum: http://forum.hibernate.org/viewtopic.php?t=965818 -- 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, 8 months

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-587) @Check doesn't work at property and collection level

by DEBOUTIN Loïc (JIRA)

@Check doesn't work at property and collection level ---------------------------------------------------- Key: ANN-587 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-587 Project: Hibernate Annotations Type: Bug Environment: Hibernate 3.2.2 Hibernate EntityManager:3.2.1.GA Hibernate Annotations :3.2.1.GA Name and version of the database you are using:Oracle XE Serveur d'application : JBoss 4.0.5.GA Reporter: DEBOUTIN Loïc Priority: Minor The @Check annotation doesn't work at property and collection level. it works only at class level. (L'annotation @Check ne fonctionne que lorsqu'elle est définie au niveau de la classe, impossible de définir plusieurs contraintes check pour différents champs d'un même bean). -- 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, 8 months

5
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2640) Clob management and deadlock

by Samuel Emangard (JIRA)

Clob management and deadlock ---------------------------- Key: HHH-2640 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2640 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.0.ga Environment: JDK 1.5, Oracle 10g v2 Reporter: Samuel Emangard Priority: Trivial Attachments: Samuel.rar Mapping documents: <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC '-//Hibernate/Hibernate Mapping DTD 3.0//EN' 'http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd'> <hibernate-mapping package="com.toluna.samuel.hibernate.emailtemplate"> <class name="EmailTemplate" table="EmailTemplate"> <id name="id" type="long"> <column name="template_id" not-null="true"/> <generator class="native"/> </id> <property name="name"> <column name="email_name" not-null="false"/> </property> <property name="htmlTextClob" type="clob"> <column name="html_Text" not-null="false"/> </property> <property name="plainTextClob" type="clob"> <column name="plain_Text" not-null="false"/> </property> </class> </hibernate-mapping> Extract also of my Java bean: ublic class EmailTemplate { private long id; private String name; private String plainText = " "; private String htmlText = " "; private Clob plainTextClob; private Clob htmlTextClob; ... Code of the test case: Session ss = HibernateUtil.getSessionFactory().getCurrentSession(); //S_LOGGER.debug("Number of current Hibernate sessions: "+ HibernateUtil.getSessionFactory().getStatistics().getSessionOpenCount()); ss.getTransaction().begin(); EmailTemplate et = (EmailTemplate) ss.load(EmailTemplate.class, new Long("299941536982302")); S_LOGGER.debug(et.getName()); Thread.sleep(5000); S_LOGGER.debug("BEFORE FLUSH"); ss.flush(); S_LOGGER.debug("AFTER FLUSH"); ss.getTransaction().commit(); The generated SQL : The load statement is always generated: /* load com.toluna.samuel.hibernate.emailtemplate.EmailTemplate */ select emailtempl0_.template_id as template1_0_0_, emailtempl0_.email_name as email2_0_0_, emailtempl0_.html_Text as html3_0_0_, emailtempl0_.plain_Text as plain4_0_0_ from EmailTemplate emailtempl0_ where emailtempl0_.template_id=? .... Depending on the implementation of the getter, the following update statement is generated: /* update com.toluna.samuel.hibernate.emailtemplate.EmailTemplate */ update EmailTemplate set email_name=?, html_Text=?, plain_Text=? where template_id=? Here is the getter: Clob getHtmlTextClob() { //1- //return Hibernate.createClob(htmlText != null ? htmlText : " "); //2- return htmlTextClob; } With 1- the update statement is generated With 2- the update statement is not generated Why? Extract of the setter: void setHtmlTextClob(Clob htmlTextClob) { this.htmlTextClob = htmlTextClob; try { if (htmlTextClob != null) { htmlText = HibernateUtil.getStringFromClob(htmlTextClob); //htmlText = "samuel"; } else htmlText = ""; } catch (SQLException e) { throw new RuntimeException(e); } catch (IOException e) { throw new RuntimeException(e); } } I have also another more critical issue which seems tied to the previous: If I write the following piece of test code instead of the one shown above: Session ss = HibernateUtil.getSessionFactory().openSession(); //S_LOGGER.debug("Number of current Hibernate sessions: "+ HibernateUtil.getSessionFactory().getStatistics().getSessionOpenCount()); EmailTemplate et = (EmailTemplate) ss.load(EmailTemplate.class, new Long("299941536982302")); S_LOGGER.debug(et.getName()); Thread.sleep(5000); S_LOGGER.debug("BEFORE FLUSH"); ss.flush(); S_LOGGER.debug("AFTER FLUSH"); As you can see in this piece of code i do not manage transactions explicitly and in that case my 2 java threads generated update statements which never ended: there was a deadlock on the DB. During the last test, If I still did not manage transactions explicitly but I modified the getter like that: Clob getHtmlTextClob() { return htmlTextClob; } Then neither update statements nor deadlock were generated. I wrote this piece of test code to reproduce deadlock I was facing on my Jonas server. Could you please help me to understand this behaviour? Here is anextract of my hibernate.cfg.xml: <property name="connection.url">jdbc:oracle:thin:@192.168.2.7:1521:tlorcl1</property> <property name="connection.username">samuel</property> <property name="connection.password">toluna</property> <property name="connection.driver_class">oracle.jdbc.driver.OracleDriver</property> <property name="dialect">org.hibernate.dialect.Oracle9Dialect</property> <property name="hibernate.show_sql">true</property> <property name="hibernate.format_sql">true</property> <property name="hibernate.use_sql_comments">true</property> <property name="myeclipse.connection.profile">QA</property> <property name="current_session_context_class">thread</property> Thanks in advance Regards Samuel -- 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, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2680) Blobs not updated on Session.merge() for detached instances

by Timo Thomas (JIRA)

Blobs not updated on Session.merge() for detached instances ----------------------------------------------------------- Key: HHH-2680 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2680 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1, 3.2.2 Environment: Windows XP Prof., Java 1.5_010, HSQLDB 1.8.0 Reporter: Timo Thomas Attachments: BlobTest.zip Blob columns are not updated when a detached instance is saved at the session with merge(). See attached TestCase. -- 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, 9 months

11
27
0 / 0

[Hibernate-JIRA] Created: (HHH-2710) Cannot specify on-delete="cascade" for a map or a set with just one element

by Gerald Klopp (JIRA)

Cannot specify on-delete="cascade" for a map or a set with just one element --------------------------------------------------------------------------- Key: HHH-2710 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2710 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.4 Reporter: Gerald Klopp Priority: Minor I'd like to specify the on-delete="cascade" attribute for a map or for a set with just one element. When I try to do this, I get the following exception : Initial SessionFactory creation failed.org.hibernate.MappingException: only inverse one-to-many associations may use on-delete="cascade" The on-delete="cascade" attribute can be specified for more complex relationships like one-to-many. But it seems that the case of a simple map or set is not covered. - Mapping document example: <hibernate-mapping> <class name="Document" table="DOCUMENT"> <id name="id" column="DOCUMENT_ID"> <generator class="native" /> </id> <map name="titles" table="DOCUMENT_TITLE" lazy="false"> <key column="DOCUMENT_ID" on-delete="cascade" /> <index column="LANGUAGE" type="string" /> <element column="TITLE" type="text" not-null="true" /> </map> <set name="references" table="DOCUMENT_REFERENCE" lazy="false"> <key column="DOCUMENT_ID" on-delete="cascade" /> <element type="string" column="REFERENCE" /> </set> </class> </hibernate-mapping> - Exception stack trace : Initial SessionFactory creation failed.org.hibernate.MappingException: only inverse one-to-many associations may use on-delete="cascade": Document.references Exception in thread "main" java.lang.ExceptionInInitializerError at fr.gklopp.test.hibernate3.util.HibernateUtil.<clinit>(HibernateUtil.java:17) at fr.gklopp.test.hibernate3.simple.DocumentManager.createAndStoreDocument(DocumentManager.java:23) at fr.gklopp.test.hibernate3.simple.DocumentManager.main(DocumentManager.java:68) Caused by: org.hibernate.MappingException: only inverse one-to-many associations may use on-delete="cascade": fr.gklopp.test.hibernate3.simple.Document.references at org.hibernate.mapping.Collection.validate(Collection.java:267) at org.hibernate.mapping.Set.validate(Set.java:19) at org.hibernate.cfg.Configuration.validate(Configuration.java:1106) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1287) at fr.gklopp.test.hibernate3.util.HibernateUtil.<clinit>(HibernateUtil.java:13) ... 2 more - Database : Oracle 10 -- 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, 9 months

8
11
0 / 0

[Hibernate-JIRA] Created: (HHH-2587) There is an attempt to set more parameters on a prepared statement than the latter can hold

by Zied Hamdi (JIRA)

There is an attempt to set more parameters on a prepared statement than the latter can hold ------------------------------------------------------------------------------------------- Key: HHH-2587 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2587 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.3 Environment: JPA through hibernate Reporter: Zied Hamdi Priority: Blocker Attachments: IntoCore.zip You can directly import the zip content into netBeans 5.5 the just launch: the test is executed at the home page servlet call. I have an index that doesn't exist : 11 (the total count of columns is 10) : Hibernate: insert into BasicPersonArchiveEntry (endDate, entryPerformer_revision, entryPerformer_id, lastOccurence, note, startDate, source_revision, source_id, revision, id) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?) could not bind value '0' to parameter: 11; Invalid argument: parameter index 11 is out of range. SQL Error: -99999, SQLState: null Invalid argument: parameter index 11 is out of range. Could not synchronize database state with session org.hibernate.exception.GenericJDBCException: could not insert: [com.homeservices.model.impl.BasicPersonArchiveEntry] at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2267) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2660) at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:52) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:139) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:516) at com.sun.enterprise.distributedtx.J2EETransaction.commit(J2EETransaction.java:395) at com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.commit(J2EETransactionManagerOpt.java:357) at com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:3653) at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:3431) at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:1247) at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:192) at com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate.invoke(EJBLocalObjectInvocationHandlerDelegate.java:118) at $Proxy49.create(Unknown Source) at tests.entities.TestArchiveServlet.processRequest(TestArchiveServlet.java:46) at tests.entities.TestArchiveServlet.doGet(TestArchiveServlet.java:61) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844) at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287) at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212) at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252) at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75) Caused by: org.apache.derby.client.am.SqlException: Invalid argument: parameter index 11 is out of range. at org.apache.derby.client.am.PreparedStatement.checkForValidParameterIndex(Unknown Source) at org.apache.derby.client.am.PreparedStatement.checkSetterPreconditions(Unknown Source) at org.apache.derby.client.am.PreparedStatement.setLong(Unknown Source) at org.hibernate.type.LongType.set(LongType.java:42) at org.hibernate.type.NullableType.nullSafeSet(NullableType.java:136) at org.hibernate.type.NullableType.nullSafeSet(NullableType.java:116) at org.hibernate.type.ComponentType.nullSafeSet(ComponentType.java:284) at org.hibernate.persister.entity.AbstractEntityPersister.dehydrate(AbstractEntityPersister.java:2008) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2243) ... 46 more EJB5018: An exception was thrown during an ejb invocation on [ArchivableFacadeStatelessBean] javax.ejb.EJBException: Transaction aborted; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback. -- 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, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2736) support for native/SQL query hints in HQL/Criteria (Oracle SELECT hints for example)

by Adam Wozniak (JIRA)

support for native/SQL query hints in HQL/Criteria (Oracle SELECT hints for example) ------------------------------------------------------------------------------------ Key: HHH-2736 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2736 Project: Hibernate3 Issue Type: New Feature Components: query-criteria, query-hql Affects Versions: 3.2.4.sp1 Reporter: Adam Wozniak Hello Everybody In 2004 Gavin said: "I think we plan to add a Query.setQueryHint() method" (hibernate forum: http://forum.hibernate.org/viewtopic.php?p=2193761&sid=5cf2ec711851f726c7... ). But I still cannot find it in Hibernate Core/Hib. Annotation/Hib. EntityManager. Can this enhancement request be opened / reopened? It would be great for us to have such possibility. Kind Regards, Adam Wozniak -- 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, 9 months

4
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2007