[Hibernate-JIRA] Created: (HSEARCH-233) Only one @IndexedEmbedded collection working in my entity.
by sam doyle (JIRA)
Only one @IndexedEmbedded collection working in my entity.
----------------------------------------------------------
Key: HSEARCH-233
URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-233
Project: Hibernate Search
Issue Type: Bug
Affects Versions: 3.0.1.GA
Environment: JBoss AS 4.2.2 Windows
Reporter: sam doyle
Attachments: jiraFiles.tar.gz
This is supposedly pretty basic functionality so perhaps it is my particular case that it is causing it.
In the attachment files the EmtVenue class is the root of the indexing.
It contains two @IndexedEmbedded
@OneToMany( cascade = CascadeType.ALL, fetch = FetchType.LAZY, mappedBy = "emtVenue" )
@IndexedEmbedded
public Set<ClientGroupVenue> getClientGroupVenues()
@Embedded
@ManyToOne( fetch = FetchType.LAZY )
@JoinColumns( { @JoinColumn( nullable = false, name = "HOST", referencedColumnName = "HOST" ),
@JoinColumn( nullable = false, name = "zone", referencedColumnName = "ZONE" ) } )
@NotNull
@IndexedEmbedded
public Zones getZones()
In this case when I index EmtVenue the resulting index contains only values that correspond to Zones and no ClientGroupVenues.
When I comment out the @IndexedEmbedded on the Zones the resulting index does show the categories.
One side note that might be of interest is indexing of Zones results in referencing some entities which don't exist that I'm catching due to the data not being in sync.
--
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
17 years, 5 months
[Hibernate-JIRA] Created: (HHH-2354) Schema validation too rigid for MySql enums
by Zeljko Trogrlic (JIRA)
Schema validation too rigid for MySql enums
-------------------------------------------
Key: HHH-2354
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2354
Project: Hibernate3
Type: Bug
Components: metamodel
Environment: jboss-seam-1.1.0.GA, MySQL 5
Reporter: Zeljko Trogrlic
Enum column type in MySQL is handled as CHAR in their JDBC driver and should be mapped to String Java type.
However, Hibernate expects varchar(n) and fails to do the validation.
This is how DatabaseMetaData.getColumns describes it:
DATA_TYPE=1
TYPE_NAME=enum
Note that although TYPE_NAME is enum, DATA_TYPE represents CHAR.
Hibernate reports following exception:
13:49:31,397 INFO [TableMetadata] table found: configuration.userdb_domain_acl
13:49:31,397 INFO [TableMetadata] columns: [id, enabled, tablename, domain]
13:49:31,397 WARN [ServiceController] Problem starting service persistence.units:ear=msmgui.ear,unitName=msmgui
javax.persistence.PersistenceException: org.hibernate.HibernateException: Wrong column type: enabled, expected: varchar(
2)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:698)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:127)
at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:264)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Validation should be fixed/relaxed to avoid this problem.
--
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
17 years, 5 months
[Hibernate-JIRA] Created: (HHH-3481) JTATransactionFactory bug when Transaction cannot be found in JNDI
by Steve Ebersole (JIRA)
JTATransactionFactory bug when Transaction cannot be found in JNDI
------------------------------------------------------------------
Key: HHH-3481
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3481
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.3.0.CR2
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.2.x, 3.3.x, 3.4
This is the code after linked patch:
protected UserTransaction getUserTransaction() {
log.trace( "Attempting to locate UserTransaction via JNDI [{}]", getUserTransactionName() );
try {
UserTransaction ut = ( UserTransaction ) getInitialContext().lookup( getUserTransactionName() );
if ( ut == null ) {
throw new TransactionException( "Naming service lookup for UserTransaction returned null [" + getUserTransactionName() +"]" );
}
log.trace( "Obtained UserTransaction" );
return ut;
}
catch ( NamingException ne ) {
throw new TransactionException( "Could not find UserTransaction in JNDI [" + getUserTransaction() + "]", ne );
}
}
Notice that in catch of NamingException we try to build a TransactionException. It is supposed to embed the JNDI namespace where we attempted to resolve the Transaction; but rather than getUserTransactionName() we are instead calling back into this same exact method getUserTransaction().
--
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
17 years, 6 months
[Hibernate-JIRA] Created: (ANN-791) Variation on 509, can't find join columns in key
by harry clark (JIRA)
Variation on 509, can't find join columns in key
------------------------------------------------
Key: ANN-791
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-791
Project: Hibernate Annotations
Issue Type: Bug
Components: binder
Affects Versions: 3.4.0.GA
Environment: Windows XP, DB2 (AS400), Hib 3.3.1
Reporter: harry clark
Attachments: hibfiles.rtf
I have what appears to be a reprise of issue 509, about finding join columns in keys. This occurs with one to many, not many to one. It occurs on the second pass over the configuration, and varies with order, as the earlier issue. When I move the class where the issue first occurs to be the first class in the config, the error occurs in another class, also in the second pass. That is, the file which raised the exception in the first example is processed successfully in the second, apparently.
I cannot reproduce this in a simple example; there is no simple example with this database, or on this server for admin reasons. I did try on MSSQL. There are ~1360 persistent classes in the ORM, and ~1100 compound key classes. This is a legacy database, obviously, but the ORM is generated from a data modeling tool which has enforced correct key relations, not a hand-written, hand-modified, buggy schema. The join columns are correct. I would very much like to eat humble pie and get on with this project, but doesn't the order variation suggest a Hibernate problem? Has Hib processed this many compound keys? Here is the stack trace. The persistent classes are in an attached file. Thanks.
Initial SessionFactory creation failed.Unable to find column with logical name: THAZCD in org.hibernate.mapping.Table(DBAFREP) and its related supertables and secondary tables
Exception in thread "main" java.lang.ExceptionInInitializerError
at com.kve.util.HibernateUtil.<clinit>(HibernateUtil.java:1360)
at com.kve.main.Main.main(Main.java:22)
Caused by: org.hibernate.MappingException: Unable to find column with logical name: THAZCD in org.hibernate.mapping.Table(DBAFREP) and its related supertables and secondary tables
at org.hibernate.cfg.Ejb3JoinColumn.checkReferencedColumnsType(Ejb3JoinColumn.java:396)
at org.hibernate.cfg.BinderHelper.createSyntheticPropertyReference(BinderHelper.java:102)
at org.hibernate.cfg.annotations.CollectionBinder.bindCollectionSecondPass(CollectionBinder.java:1321)
at org.hibernate.cfg.annotations.CollectionBinder.bindOneToManySecondPass(CollectionBinder.java:654)
at org.hibernate.cfg.annotations.CollectionBinder.bindStarToManySecondPass(CollectionBinder.java:589)
at org.hibernate.cfg.annotations.CollectionBinder$1.secondPass(CollectionBinder.java:543)
at org.hibernate.cfg.CollectionSecondPass.doSecondPass(CollectionSecondPass.java:66)
at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1163)
at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:329)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1319)
at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867)
at com.kve.util.HibernateUtil.<clinit>(HibernateUtil.java:1356)
... 1 more
--
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
17 years, 6 months
[Hibernate-JIRA] Created: (EJB-277) allow string values for query hints
by Norman Richards (JIRA)
allow string values for query hints
-----------------------------------
Key: EJB-277
URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-277
Project: Hibernate Entity Manager
Type: Improvement
Reporter: Norman Richards
It seems that some string values are not accepted as query hint values in hibernate. In specific, I was trying to convert a simple query that uses setHint("org.hibernate.cacheable", true) to use an XML-defined EntityQuery that uses
<framework:entity-query name="allCategories"
ejbql="select c from Category c"
order="c.name">
<framework:hints>
<key>org.hibernate.cacheable</key>
<value>true</value>
</framework:hints>
</framework:entity-query>
Unfortunately, this fails with an IllegalArgumentException:
Caused by: java.lang.IllegalArgumentException: Value for hint
at org.hibernate.ejb.QueryImpl.setHint(QueryImpl.java:160)
at org.jboss.seam.framework.EntityQuery.createQuery(EntityQuery.java:114)
at org.jboss.seam.framework.EntityQuery.getResultList(EntityQuery.java:41)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
...
Although I didn't try it, I would assume this would also fail from a @QueryHint in on a named query since that annotation only accepts a string
value.
I don't think this is technically a bug, but it would be very convenient if all the hints could accept string values.
--
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
17 years, 6 months
[Hibernate-JIRA] Created: (HHH-3078) Problem with multiple classloaders and cglib proxy enhancement, e.g. in the usual tomcat configuration
by Pietu Pohjalainen (JIRA)
Problem with multiple classloaders and cglib proxy enhancement, e.g. in the usual tomcat configuration
------------------------------------------------------------------------------------------------------
Key: HHH-3078
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3078
Project: Hibernate3
Issue Type: Bug
Components: build
Affects Versions: 3.2.5, 3.1.3
Environment: Verified against Hibernate 3.1.3 and Hibernate 3.2.5ga.
Reporter: Pietu Pohjalainen
Attachments: hibernate-3.2.patch, LoadOrderTest.tar.gz
In an usual tomcat classloader configuration, with hibernate3.jar residing in the Tomcat's common class loader and webapplications staying in their own classloaders, the cglib's proxy enhancement fails sometimes, as it tries to load the web application's classes via the Tomcat's common class loader.
The main culprit is the interaction between Hibernate's PojoEntityTuplizer and cglib's AbstractClassGenerator.
PojoEntityTuplizer passes a Set of interfaces to cglib for proxy enhancement. The set is constructed in method buildProxyFactory(PersistentClass, Getter, Setter). Now, depending on the interface classes hash codes, the order of included interfaces varies: sometimes Hibernate's HibernateProxy.class is the first one, sometimes it is the enhanced interface's class.
Problems rise when the Set's iterator gives the interfaces in order of {HibernateProxy.class, InterfaceToBeEnhanced.class}. When performing the enhancing, the cglib chooses the first interface class's classloader to find all the other classes as well. Because HibernateProxy.class was loaded by Tomcat's common class loader, it cannot find the application's class InterfaceToBeEnhanced. Thus a ClassDefNotFoundError is thrown.
There's a JUnit test demonstrating the case. Because the hashCodes of loaded classes is quite undeterministic (read: beyond my skills to make deterministic), I've included ten interface classes that should be cglib-enhanced. Most often, one of these enhancements fails, due to this bug.
A fix would be to change hibernate to prioritize the application's interface classes over Hibernate's HibernateProxy.class in the set. This could be implemented by using LinkedHashSet instead of HashSet, and adding the HibernateProxy.class as the last one. This change does not introduce any faults to existing unit test sets, but allows the attaches JUnit test to run without failures. The attached patch is for Hibernate 3.2.5ga.
--
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
17 years, 6 months
[Hibernate-JIRA] Created: (HHH-3511) Sybase - Column alias in subselect doesn't works
by Juraci Paixao Krohling (JIRA)
Sybase - Column alias in subselect doesn't works
------------------------------------------------
Key: HHH-3511
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3511
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.2.4.sp1
Environment: Branch_3_2_4_SP1_CP with Sybase 15
Reporter: Juraci Paixao Krohling
I could not find any reference in documentation to support it, but it seems that column aliasing in sub-selects isn't supported. I could not find any information in the docs which confirms or denies this, but running the test CriteriaQueryTest#testDetachedCriteriaAsSubQuery can confirm this.
Hibernate generates a query which ends in:
where ? in (select this_.courseCode as y0_ from Course this_ where this_.description like ?)
This fails in Sybase, with this message:
15:29:38,063 WARN JDBCExceptionReporter:77 - SQL Error: 156, SQLState: ZZZZZ
15:29:38,074 ERROR JDBCExceptionReporter:78 - Incorrect syntax near the keyword 'AS'.
Removing all "as" keywords returns the same message, even though the query itself doesn't have it. [1]
Removing the "as $alias" solves the problem.
The working line is:
where courseCode in (select this_.courseCode from Course this_ where this_.description like 'test%')
--
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
17 years, 6 months
[Hibernate-JIRA] Commented: (HHH-1528) GenericJDBCException when querying on one-to-one association
by Arne Limburg (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1528?page=c... ]
Arne Limburg commented on HHH-1528:
-----------------------------------
I guess the empty implementation of nullSaveSet(...) has to do with insertion of (in your example) Persons. On insertion no id for the name has to be set because of the primary key join-column. However I get thi9s error, too, when using another join-column than the primary key. I guess on the OneToOneType should be used on insertion and the ManyToOneType on selection.
> GenericJDBCException when querying on one-to-one association
> ------------------------------------------------------------
>
> Key: HHH-1528
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1528
> Project: Hibernate Core
> Issue Type: Bug
> Affects Versions: 3.1.2
> Environment: Hibernate 3.1.2, MySQL 4.1, Java 5
> Reporter: Alexander Dvorkovyy
> Attachments: src.zip
>
>
> I am getting following stack trace:
> Exception in thread "main" org.hibernate.exception.GenericJDBCException: could not execute query
> at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:91)
> at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:79)
> at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
> at org.hibernate.loader.Loader.doList(Loader.java:2148)
> at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2029)
> at org.hibernate.loader.Loader.list(Loader.java:2024)
> at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:375)
> at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:308)
> at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:153)
> at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1129)
> at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
> at BugDemo.main(BugDemo.java:28)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:86)
> Caused by: java.sql.SQLException: Statement parameter 1 not set.
> at com.mysql.jdbc.ServerPreparedStatement.serverExecute(ServerPreparedStatement.java:1031)
> at com.mysql.jdbc.ServerPreparedStatement.executeInternal(ServerPreparedStatement.java:676)
> at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1030)
> at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:139)
> at org.hibernate.loader.Loader.getResultSet(Loader.java:1669)
> at org.hibernate.loader.Loader.doQuery(Loader.java:662)
> at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224)
> at org.hibernate.loader.Loader.doList(Loader.java:2145)
> ... 13 more
> while executing this code:
> OneClass one = (OneClass) session.load(OneClass.class, 1L);
> Query query = session.createQuery("FROM OneToOneClass oto WHERE oto.whatever=:whatever");
> query.setParameter("whatever", one);
> query.list(); // < - - Exception is thrown here
> on this domain model (I used annotations here, same thing with hbm.xml):
> @Entity public class OneClass {
> @Id private Long id;
> }
> @Entity public class OneToOneClass {
> @Id private Long id;
> @OneToOne
> @PrimaryKeyJoinColumn
> private OneClass whatever;
> }
> Problem first appeared in 3.1 (also when using xml mapping files), in 3.0 no problem. Full source code attached.
> Would be nice if the problem can be fixed in upcoming 3.1.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
17 years, 6 months
[Hibernate-JIRA] Created: (HHH-2077) Providing an escape sequence for Criteria queries
by Tobias Dietl (JIRA)
Providing an escape sequence for Criteria queries
-------------------------------------------------
Key: HHH-2077
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2077
Project: Hibernate3
Type: Improvement
Components: query-criteria
Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2, 3.2.0.cr3, 3.2.0.cr4
Environment: Hibernate 3.1.3, MySQL, HSQLDB, Oracle
Reporter: Tobias Dietl
Up to now, there is no way of setting the escape sequence to use for string comparisions with like for Criteria queries.
This is necessary as MySQL on the one hand and HSQLDB / Oracle on the other behave differently...
If you want to search for '_abc' in MySQL, you have to use:
value like '\\_abc'
In Oracle or HsqlDB, you have to use:
value like '\_abc'
If you want to switch to another escape sequence like '|' , you can set it in HQL with value like '|_abc' escape '|'. Unfortunately, there is no way of setting it for Criteria queries, which would force me to rewrite all my Criteria queries in HQL. It would really be nice if the feature/improvement would be added...
--
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
17 years, 6 months
[Hibernate-JIRA] Created: (HHH-3647) instance not of expected entity type: java.util.HashMap is not a: smx3.schema3.Party_AUD
by Mark Derricutt (JIRA)
instance not of expected entity type: java.util.HashMap is not a: smx3.schema3.Party_AUD
----------------------------------------------------------------------------------------
Key: HHH-3647
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3647
Project: Hibernate Core
Issue Type: Bug
Components: envers
Affects Versions: 3.4
Reporter: Mark Derricutt
After resolving all my other issues regarding using envers from trunk, I now find this stacktrace thrown when saving records into the database:
org.hibernate.HibernateException: instance not of expected entity type: java.util.HashMap is not a: smx3.schema3.Party_AUD
at org.hibernate.persister.entity.AbstractEntityPersister.getSubclassEntityPersister(AbstractEntityPersister.java:3663)
at org.hibernate.impl.SessionImpl.getEntityPersister(SessionImpl.java:1374)
at org.hibernate.id.Assigned.generate(Assigned.java:51)
at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:122)
at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:210)
at org.hibernate.event.def.DefaultSaveEventListener.saveWithGeneratedOrRequestedId(DefaultSaveEventListener.java:56)
at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:195)
at org.hibernate.event.def.DefaultSaveEventListener.performSaveOrUpdate(DefaultSaveEventListener.java:50)
at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:93)
at org.hibernate.impl.SessionImpl.fireSave(SessionImpl.java:562)
at org.hibernate.impl.SessionImpl.save(SessionImpl.java:550)
at org.hibernate.envers.synchronization.work.ModWorkUnit.perform(ModWorkUnit.java:59)
at org.hibernate.envers.synchronization.AuditSync.executeInSession(AuditSync.java:126)
at org.hibernate.envers.synchronization.AuditSync.beforeCompletion(AuditSync.java:150)
at com.atomikos.icatch.jta.Sync2Sync.beforeCompletion(Sync2Sync.java:73)
at com.atomikos.icatch.imp.TransactionStateHandler.commit(TransactionStateHandler.java:253)
at com.atomikos.icatch.imp.CompositeTransactionImp.doCommit(CompositeTransactionImp.java:509)
at com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:138)
at com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:297)
at com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:608)
at com.atomikos.icatch.jta.UserTransactionManager.commit(UserTransactionManager.java:148)
at nz.co.smx.rest.TransactionFilter.afterHandle(TransactionFilter.java:224)
at org.restlet.Filter.handle(Filter.java:197)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Filter.doHandle(Filter.java:150)
at com.noelios.restlet.StatusFilter.doHandle(StatusFilter.java:130)
at org.restlet.Filter.handle(Filter.java:195)
at org.restlet.Filter.doHandle(Filter.java:150)
at org.restlet.Filter.handle(Filter.java:195)
at com.noelios.restlet.ChainHelper.handle(ChainHelper.java:124)
at com.noelios.restlet.application.ApplicationHelper.handle(ApplicationHelper.java:112)
at org.restlet.Application.handle(Application.java:341)
at org.restlet.ext.wadl.WadlApplication.handle(WadlApplication.java:705)
at org.restlet.Filter.doHandle(Filter.java:150)
My Party entity is a single table inheritance based entity with three subclasses.
--
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
17 years, 6 months
[Hibernate-JIRA] Created: (HHH-3679) Sybase conversion of Java byte to tinyint fails with 8-bit values causing unit test failures
by Gail Badner (JIRA)
Sybase conversion of Java byte to tinyint fails with 8-bit values causing unit test failures
--------------------------------------------------------------------------------------------
Key: HHH-3679
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3679
Project: Hibernate Core
Issue Type: Bug
Environment: Sybase
Reporter: Gail Badner
Assignee: Gail Badner
Fix For: 3.2.x, 3.3.x, 3.4
If an 8-bit byte value is inserted into a Sybase TINYINT column, GenericJDBCException is thrown because of an arithmetic overflow during implicit conversion of a SMALLINT value to a TINYINT field.
This is happening for MixedTest.testMixedInheritance() and InterfaceProxyTest.testInterfaceProxies().
The full stacktrace is:
could not insert: [org.hibernate.test.interfaceproxy.SecureDocumentImpl]" type="org.hibernate.exception.
GenericJDBCException">org.hibernate.exception.GenericJDBCException: could not insert: [org.hibernate.test.interfaceproxy.Sec
ureDocumentImpl]
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:2640)
at org.hibernate.action.EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:48)
at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:250)
at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:298)
at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:181)
at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:107)
at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventL
istener.java:187)
at org.hibernate.event.def.DefaultSaveEventListener.saveWithGeneratedOrRequestedId(DefaultSaveEventListener.java:33)
at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:
172)
at org.hibernate.event.def.DefaultSaveEventListener.performSaveOrUpdate(DefaultSaveEventListener.java:27)
at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70)
at org.hibernate.impl.SessionImpl.fireSave(SessionImpl.java:535)
at org.hibernate.impl.SessionImpl.save(SessionImpl.java:523)
at org.hibernate.impl.SessionImpl.save(SessionImpl.java:519)
at org.hibernate.test.interfaceproxy.InterfaceProxyTest.testInterfaceProxies(InterfaceProxyTest.java:52)
at org.hibernate.junit.functional.FunctionalTestCase.runTest(FunctionalTestCase.java:102)
at org.hibernate.junit.UnitTestCase.runBare(UnitTestCase.java:34)
at org.hibernate.junit.functional.FunctionalTestClassTestSuite.runTest(FunctionalTestClassTestSuite.java:100)
at org.hibernate.junit.functional.FunctionalTestClassTestSuite.run(FunctionalTestClassTestSuite.java:69)
Caused by: com.sybase.jdbc3.jdbc.SybSQLException: Arithmetic overflow during implicit conversion of SMALLINT value '-10
4' to a TINYINT field .
at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.updateLoop(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.executeUpdate(Unknown Source)
at com.sybase.jdbc3.jdbc.SybPreparedStatement.executeUpdate(Unknown Source)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2250)
... 34 more
--
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
17 years, 6 months
[Hibernate-JIRA] Created: (HHH-3675) Limitiations on Sybase ResultSet implementation causes unit tets failures
by Gail Badner (JIRA)
Limitiations on Sybase ResultSet implementation causes unit tets failures
-------------------------------------------------------------------------
Key: HHH-3675
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3675
Project: Hibernate Core
Issue Type: Bug
Components: core
Reporter: Gail Badner
Assignee: Gail Badner
Fix For: 3.2.x, 3.3.x, 3.4
CMTTest.testCurrentSessionWithScroll() fails using Sybase because it calls ResultSet.isLast() and the Sybase implentation throws com.sybase.jdbc2.utils.UnimplementedOperationException. The exception message is, "The method com.sybase.jdbc2.jdbc.SybResultSet.isLast() has not been completed and should not be called.".
AggressiveReleaseTest,testSerializationFailsOnAfterStatementAggressiveReleaseWithOpenResources() throws NullPointerException when a ResultSet is closed before reading any rows.
The exception is:
java.lang.NullPointerException at com.sybase.jdbc2.tds.TdsResultSet.next(TdsResultSet.java:313) at com.sybase.jdbc2.tds.TdsResultSet.close(TdsResultSet.java:452) at com.sybase.jdbc2.jdbc.SybResultSet.markDead(SybResultSet.java:1540) at com.sybase.jdbc2.jdbc.SybResultSet.close(SybResultSet.java:1608) at com.sybase.jdbc2.jdbc.SybResultSet.close(SybResultSet.java:193) at org.hibernate.jdbc.AbstractBatcher.closeQueryStatement(AbstractBatcher.java:207) at org.hibernate.impl.AbstractScrollableResults.close(AbstractScrollableResults.java:99) at org.hibernate.test.connections.AggressiveReleaseTest.testSerializationFailsOnAfterStatementAggressiveReleaseWithOpenResources(AggressiveReleaseTest.java:112) at org.hibernate.junit.functional.FunctionalTestCase.runTest(FunctionalTestCase.java:102) at org.hibernate.junit.UnitTestCase.runBare(UnitTestCase.java:34) at org.hibernate.junit.functional.FunctionalTestClassTestSuite.runTest(FunctionalTestClassTestSuite.java:100) at org.hibernate.junit.functional.FunctionalTestClassTestSuite.run(FunctionalTestClassTestSuite.java:69)
CurrentSessionConnectionTest extends AggressiveReleaseTest, so NullPointerException is thrown for the same reason.
--
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
17 years, 6 months
[Hibernate-JIRA] Created: (HHH-3678) Fields marked as @Transient on components that are mapped on @CollecionOfElements are still persistent
by Leandro Feres Ribeiro (JIRA)
Fields marked as @Transient on components that are mapped on @CollecionOfElements are still persistent
------------------------------------------------------------------------------------------------------
Key: HHH-3678
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3678
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.2.6
Environment: Hibernate 3.2.6.GA, hibernate-commons-annotations 3.3.0.GA, hibernate-annotations 3.3.0.GA.
Reporter: Leandro Feres Ribeiro
Attachments: testCase.zip
The test cases show the bug. I have a Component class, that is an attribute of the CollectionElement class, that is mapped as a @CollectionOfElements on TestEntity. Component has 4 transient attributes (name, description, middleName and lastName), however only middleName and lastName behave as transient. This means that when the @Transient annotation appears on the getter methods, on the Component class, it is not working.
See the classes below:
public class Component implements Serializable {
private Integer id;
private String name;
private String description;
@Transient
private String middleName;
private transient String lastName;
public Integer getId() {
return id;
}
public void setId(Integer id) {
this.id = id;
}
@Transient
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
@Transient
public String getDescription() {
return description;
}
public void setDescription(String description) {
this.description = description;
}
public String getMiddleName() {
return middleName;
}
public void setMiddleName(String middleName) {
this.middleName = middleName;
}
public String getLastName() {
return lastName;
}
public void setLastName(String lastName) {
this.lastName = lastName;
}
}
public class CollectionElement implements Serializable {
private Component component;
private Integer number;
private String property;
public Component getComponent() {
return component;
}
public void setComponent(Component component) {
this.component = component;
}
public Integer getNumber() {
return number;
}
public void setNumber(Integer number) {
this.number = number;
}
public String getProperty() {
return property;
}
public void setProperty(String property) {
this.property = property;
}
}
@Entity
@Table
public class TestEntity {
private Integer id;
private List<CollectionElement> elements = new ArrayList<CollectionElement>();
@Id
public Integer getId() {
return id;
}
public void setId(Integer id) {
this.id = id;
}
@CollectionOfElements
public List<CollectionElement> getElements() {
return elements;
}
public void setElements(List<CollectionElement> elements) {
this.elements = elements;
}
}
--
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
17 years, 6 months
[Hibernate-JIRA] Created: (HHH-3676) Unable to Load JTA Transaction
by pioneer (JIRA)
Unable to Load JTA Transaction
------------------------------
Key: HHH-3676
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3676
Project: Hibernate Core
Issue Type: Bug
Components: core
Environment: Hibernate3, Weblogic 9.0
Reporter: pioneer
This is my hibernat.cfg.xml file which i have been using for my app. me trying out an J2ee Application within an weblogic 9.0 . As my config denotes its exactly true.When WeblogicTransactionManagerLookup tries to look out for tranaction within JTASessionContext within currentSession() method , it returns due to the following line.
if(txn == null)
{
throw new HibernateException("Unable to load JTA Transaction);
}
this line didn't allow to proceed within the method to create an new session. Its an bug with JTASessionContext. Correct me if iam wrong.
<property name="connection.datasource">jdbc/connectionPool</property>
<property name="hibernate.transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property>
<property name="hibernate.transaction.manager_lookup_class">org.hibernate.transaction.WeblogicTransactionManagerLookup</property>
<property name="hibernate.dialect">org.hibernate.dialect.OracleDialect</property>
<property name="hibernate.current_session_context_class">jta</property>
<property name="hibernate.cache.provider_class">org.hibernate.cache.EhCacheProvider</property>
<property name="hibernate.cache.use_query_cache">true</property>
<property name="hibernate.query.factory_class">org.hibernate.hql.ast.ASTQueryTranslatorFactory</property>
<property name="show_sql">true</property>
--
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
17 years, 6 months
[Hibernate-JIRA] Created: (HHH-3303) Parameters bound in wrong order for IN-clauses on dynamic components
by Holger Engels (JIRA)
Parameters bound in wrong order for IN-clauses on dynamic components
--------------------------------------------------------------------
Key: HHH-3303
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3303
Project: Hibernate3
Issue Type: Bug
Components: query-criteria
Affects Versions: 3.2.6
Reporter: Holger Engels
When issuing the following query, the parameters are bound in wrong order:
List<Map> keys = Arrays.asList(CollectionUtil.map("mandator", "M", "key", "test"), CollectionUtil.map("mandator", "M", "key", "user"));
list = session.createCriteria(Profile.class).add(Restrictions.in("key", keys)).list();
// list.size() = 0, should be 2
[DEBUG] 15:24:45 [org.hibernate.SQL ]: select this_.id as id7_0_, this_.version as version7_0_, this_.key_mandator as key3_7_0_, this_.key_key as key4_7_0_, this_.created as created7_0_, this_.createdBy as createdBy7_0_, this_.modified as modified7_0_, this_.name as name7_0_ from auth_profile this_ where (this_.key_mandator, this_.key_key) in ((?, ?), (?, ?))
Hibernate: select this_.id as id7_0_, this_.version as version7_0_, this_.key_mandator as key3_7_0_, this_.key_key as key4_7_0_, this_.created as created7_0_, this_.createdBy as createdBy7_0_, this_.modified as modified7_0_, this_.name as name7_0_ from auth_profile this_ where (this_.key_mandator, this_.key_key) in ((?, ?), (?, ?))
[DEBUG] 15:24:45 [nate.jdbc.AbstractBatcher]: preparing statement
[DEBUG] 15:24:45 [hibernate.type.StringType]: binding 'M' to parameter: 1
[DEBUG] 15:24:45 [hibernate.type.StringType]: binding 'M' to parameter: 2
[DEBUG] 15:24:45 [hibernate.type.StringType]: binding 'test' to parameter: 3
[DEBUG] 15:24:45 [hibernate.type.StringType]: binding 'user' to parameter: 4
It should be:
binding 'M' to parameter: 1
binding 'test' to parameter: 2
binding 'M' to parameter: 3
binding 'user' to parameter: 4
The mapping for key is:
<dynamic-component name="key" unique="true">
<property name="mandator" column="key_mandator" type="string" length="4"/>
<property name="key" column="key_key" type="string" length="16"/>
</dynamic-component>
Interestingly, the same query works in HQL:
Query query = session.createQuery("from Profile where key in (:keys)");
query.setParameterList("keys", keys);
list = query.list();
// list.size() = 2
--
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
17 years, 6 months
[Hibernate-JIRA] Commented: (HHH-759) problem for mixxing setmaxresults and setlockmode
by areis (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-759?page=co... ]
areis commented on HHH-759:
---------------------------
I am facing the same problem as reported by Frederic Leitenberger (I also need to use ORDER BY, MAXROWS and FOR UPDATE in one query. ) .
Is there an estimate of when there will be a solution?
Thanks!
> problem for mixxing setmaxresults and setlockmode
> -------------------------------------------------
>
> Key: HHH-759
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-759
> Project: Hibernate Core
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: Client:windows2000 professional,jre1.4.2, oracle8client,eclipse3.1-RC3,hibernate-tools 3.0 alpha4a,JBossIDE1.5M1
> Server:Solaris 2.8, oracle 8.1.7
> Reporter: johnhua
> Priority: Minor
>
> there is a problem for mixxing setmaxresults and setlockmode.
> the problem is that "ORA-00904: invalid column name".
> The error info is as the below:
> Hibernate: select * from ( select idmapp0_.RI as col_0_0_ from PCTMNGT.IDMAP_P idmapp0_ where idmapp0_.STATUS=? ) where rownum <= ? for update of idmapp0_.RI
> 14:21:54,076 DEBUG AbstractBatcher:AbstractBatcher.java:365 - preparing statement
> 14:21:54,082 DEBUG AbstractBatcher:AbstractBatcher.java:285 - about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
> 14:21:54,083 DEBUG AbstractBatcher:AbstractBatcher.java:403 - closing statement
> 14:21:54,090 WARN JDBCExceptionReporter:JDBCExceptionReporter.java:71 - SQL Error: 904, SQLState: 42000
> 14:21:54,091 ERROR JDBCExceptionReporter:JDBCExceptionReporter.java:72 - ORA-00904: invalid column name
> The source code is as the below:
> //query an unused emid for new tone
> query = av_session.createQuery("select v_idmap from IdmapP as v_idmap where v_idmap.status=:v_status");
> query.setCharacter("v_status",EMID_STATUS.UNUSED.charValue());
> query.setMaxResults(1);
> query.setLockMode("v_idmap",LockMode.UPGRADE);
> it = query.iterate();
> if( !it.hasNext() )
> {
> tx.rollback();
> lv_err = "addRing::doAddRingFile: no unused EMID for new tone in idmap. toneid="+av_tone;
> throw new InterfaceErrException(lv_err,INTERFACE_RETCODE.SYSTEM_ERR);
> }
--
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
17 years, 6 months
[Hibernate-JIRA] Created: (HHH-3667) Problem in class Dialect
by Jorge Miguel da Silva e Sá (JIRA)
Problem in class Dialect
------------------------
Key: HHH-3667
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3667
Project: Hibernate Core
Issue Type: Bug
Components: core
Reporter: Jorge Miguel da Silva e Sá
I have a problem with Hibernate. When I add one foreignKey Constraint in one table my application hang.
When i debug the problem, I think I found a bug in this feature ( getAddForeignKeyConstraintString).
When it does
if ( !referencesPrimaryKey )
Not should not be
if ( referencesPrimaryKey ) ?
public String getAddForeignKeyConstraintString(
String constraintName,
String[] foreignKey,
String referencedTable,
String[] primaryKey,
boolean referencesPrimaryKey) {
StringBuffer res = new StringBuffer( 30 );
res.append( " add constraint " )
.append( constraintName )
.append( " foreign key (" )
.append( StringHelper.join( ", ", foreignKey ) )
.append( ") references " )
.append( referencedTable );
if ( !referencesPrimaryKey ) {
res.append( " (" )
.append( StringHelper.join( ", ", primaryKey ) )
.append( ')' );
}
return res.toString();
}
--
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
17 years, 7 months
[Hibernate-JIRA] Created: (HHH-2629) Enable ordering by association paths
by Jörg Heinicke (JIRA)
Enable ordering by association paths
------------------------------------
Key: HHH-2629
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2629
Project: Hibernate3
Issue Type: Patch
Components: query-criteria
Affects Versions: 3.2.4.sp1
Reporter: Jörg Heinicke
In Hibernate's criteria API ordering is not possible on association properties without explicitly creating aliases.
This also only works on one level, not recursively as it would be needed in the following example.
Criteria criteria = session.createCriteria(Account.class);
Criteria pCriteria = criteria.createCriteria("person");
pCriteria.add(Example.create(person));
pCriteria.createCriteria("company");
criteria.addOrder(Order.asc("person.company.name"));
return criteria.list();
I have changed CriteriaQueryTranslator in a way that it first searches the aliasCriteriaMap, second the associationPathCriteriaMap. And the key used for the search is no longer
StringHelper.root( propertyName );
but
StringHelper.qualifier( propertyName );
>From what I understand this can't break anything since it has always only worked with one '.' in the path. For those cases the key stays the same.
This implementation is still not perfect since
1. you need to create criteria in advance
2. you can't switch between alias and actual association path. The best would probably be to walk the path recursively.
--
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
17 years, 7 months
[Hibernate-JIRA] Created: (HHH-3666) mapping of varchar primary key from database as assigned but while try to get data data automatically deleted.
by Prashant k Patil. (JIRA)
mapping of varchar primary key from database as assigned but while try to get data data automatically deleted.
--------------------------------------------------------------------------------------------------------------
Key: HHH-3666
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3666
Project: Hibernate Core
Issue Type: Bug
Environment: hibernate 3
Database MySql
Reporter: Prashant k Patil.
I am trying to get data from database. It is successfully receives data if it is add by hibernate.
If that data is manually added in database it is automatically deleted by hibernate.
my mapping to table like this.
<?xml version="1.0"?>
<!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd">
<!-- Generated Dec 17, 2008 1:38:05 PM by Hibernate Tools 3.1.0.beta5 -->
<hibernate-mapping>
<class name="com..entity.User" table="user" dynamic-update="true" catalog="database">
<comment></comment>
<id name="userId" type="string" length="30">
<column name="USER_ID" />
</id>
<property name="password" type="string" length="30">
<column name="PASSWORD">
<comment></comment>
</column>
</property>
</class>
</hibernate-mapping>
and code using like this .
Transaction tx = null;
try {
Session currentSession = InitializeSessionFactory.getInstance().getCurrentSession();
tx = currentSession.beginTransaction();
//User temp = new User("doctor","doctor","DOCTOR",new Integer(1));
//currentSession.save(temp);
User user = (User)currentSession.get(User.class, userId);
tx.commit();
return user;
}catch(Exception e) {
tx.rollback();
logger.error(e.getMessage());
}
please help me so that data not to be deleted.
--
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
17 years, 7 months
[Hibernate-JIRA] Created: (HBX-1038) NullPointerException trying to open "hibernate.reveng.xml" in Hibernate Reverse Engineering Editor
by Alex K (JIRA)
NullPointerException trying to open "hibernate.reveng.xml" in Hibernate Reverse Engineering Editor
--------------------------------------------------------------------------------------------------
Key: HBX-1038
URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1038
Project: Hibernate Tools
Issue Type: Bug
Components: reverse-engineer
Affects Versions: 3.2.0.GA
Environment: Windows XP, Eclipse 3.3.1.1.
Reporter: Alex K
I am getting an excepting trying to open "hibernate.reveng.xml" in Hibernate Reverse Engineering Editor.
Tools are 3.2.0 GA. Eclipse is 3.3.1.1.
Stack trace:
java.lang.NullPointerException
at org.eclipse.wst.sse.ui.StructuredTextEditor.update(StructuredTextEditor.java:3096)
at org.hibernate.eclipse.mapper.editors.xpl.XMLFormEditorPart.addSourcePage(XMLFormEditorPart.java:185)
at org.hibernate.eclipse.mapper.editors.xpl.XMLFormEditorPart.addPages(XMLFormEditorPart.java:50)
at org.hibernate.eclipse.mapper.editors.ReverseEngineeringEditor.addPages(ReverseEngineeringEditor.java:84)
at org.eclipse.ui.forms.editor.FormEditor.createPages(FormEditor.java:146)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:263)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2739)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2651)
at org.eclipse.ui.internal.WorkbenchPage.access$13(WorkbenchPage.java:2643)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2595)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2590)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2574)
at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:340)
at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.java:328)
at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:190)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
hibernate.reveng.xml has been generated by the Reverse Engineering Wizard. Contents are (about 9 tables are referenced):
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE hibernate-reverse-engineering PUBLIC "-//Hibernate/Hibernate Reverse Engineering DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-reverse-engineering-3.0.dtd" >
<hibernate-reverse-engineering>
<table-filter match-catalog="mysql" match-name="table1"/>
<table-filter match-catalog="mysql" match-name="table2"/>
...
</hibernate-reverse-engineering>
--
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
17 years, 7 months
[Hibernate-JIRA] Updated: (HHH-1015) Incorrect SQL generated when one-to-many foreign key is in a discriminated subclass table
by Krasimir Chobantonov (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1015?page=c... ]
Krasimir Chobantonov updated HHH-1015:
--------------------------------------
Attachment: hhh-1015-version2.patch
Attaching patch hhh-1015-version2.patch that will fix the HQL to SQL generation and it will include also the fixes from hhh-1015.patch
> Incorrect SQL generated when one-to-many foreign key is in a discriminated subclass table
> -----------------------------------------------------------------------------------------
>
> Key: HHH-1015
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1015
> Project: Hibernate Core
> Issue Type: Bug
> Components: core
> Affects Versions: 3.1 beta 2
> Environment: Hibernate versions 3.1 beta 3 and 3.0.5
> Reporter: Steven Grimm
> Priority: Minor
> Attachments: hhh-1015-version2.patch, hhh-1015.patch
>
>
> I have the following mappings describing a hierarchy of events and a class that the events refer to:
> <hibernate-mapping package="com.xyz">
> <class name="Event" table="event" discriminator-value="-1">
> <id name="Id" type="long" column="event_id"/>
> <discriminator column="event_type_id" type="integer" />
> <subclass name="EventPayer" discriminator-value="-3">
> <join table="event_payer">
> <key column="event_id" />
> <many-to-one name="payer" column="payer_id" class="Payer" />
> </join>
> <subclass name="EventPayerCreated" discriminator-value="1" />
> </subclass>
> </class>
> <class name="Payer" table="payer">
> <id name="payerId" column="payer_id" type="java.lang.Long"/>
> <set name="eventPayers" inverse="true" cascade="save-update">
> <key column="payer_id"/>
> <one-to-many class="EventPayer"/>
> </set>
> </class>
> </hibernate-mapping>
> When I fetch the Payer.eventPayers collection, Hibernate generates this SQL:
> select eventpayer0_.payer_id as payer7_1_,
> eventpayer0_.event_id as event1_1_,
> eventpayer0_.event_id as event1_5_0_,
> eventpayer0_1_.payer_id as payer2_6_0_,
> eventpayer0_.event_type_id as event2_5_0_
> from event eventpayer0_
> inner join event_payer eventpayer0_1_
> on eventpayer0_.event_id=eventpayer0_1_.event_id
> where eventpayer0_.payer_id=?
> The problem is that there is no event.payer_id column; payer_id is in the child table, not the parent. It appears that specifying a discriminated subclass in <one-to-many> is the same as specifying the superclass, or that Hibernate is ignoring the subclass's <join> element. As far as I can tell, this leaves no way to resolve bidirectional associations where one end of the association is in a discriminated subclass, which seems like a perfectly reasonable thing to want to do.
> I also tried changing <key column="payer_id"/> to <key property-ref="payer"/> in the Payer class's <set> element, but got similar behavior in the form of a "property not found" error: Hibernate is either looking in the superclass's properties rather than the subclass's or is ignoring the list of properties in the <join> element.
--
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
17 years, 7 months
[Hibernate-JIRA] Created: (HHH-3663) Request to add Joined inheritance strategy supported for versioning
by louie (JIRA)
Request to add Joined inheritance strategy supported for versioning
-------------------------------------------------------------------
Key: HHH-3663
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3663
Project: Hibernate Core
Issue Type: New Feature
Components: envers
Affects Versions: 3.3.1
Environment: Windows XP, jdk1.6
Reporter: louie
We have versioned entities with Joined inheritance strategy. The Envers throws the following exception:
[hibernatetool] An exception occurred while running exporter #2:hbm2ddl (Generates database schema)
[hibernatetool] To get the full stack trace run ant with -verbose
[hibernatetool] org.hibernate.MappingException: Joined inheritance strategy not supported for versioning!
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error executing ant tasks
Embedded error: org.hibernate.MappingException: Joined inheritance strategy not supported for versioning!
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant tasks
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing ant tasks
at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:114)
at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 16 more
Caused by: org.hibernate.MappingException: Joined inheritance strategy not supported for versioning!
at org.hibernate.tool.ant.HibernateToolTask.reportException(HibernateToolTask.java:226)
at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:189)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:64)
at net.sf.antcontrib.logic.IfTask.execute(IfTask.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:123)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:108)
... 19 more
Caused by: org.hibernate.MappingException: Joined inheritance strategy not supported for versioning!
at org.jboss.envers.configuration.metadata.VersionsMetadataGenerator.generateFirstPass(VersionsMetadataGenerator.java:307)
at org.jboss.envers.configuration.EntitiesConfigurator.configure(EntitiesConfigurator.java:84)
at org.jboss.envers.configuration.VersionsConfiguration.<init>(VersionsConfiguration.java:80)
at org.jboss.envers.configuration.VersionsConfiguration.getFor(VersionsConfiguration.java:93)
at org.jboss.envers.ant.JPAConfigurationTaskWithEnvers.doConfiguration(JPAConfigurationTaskWithEnvers.java:33)
at org.hibernate.tool.ant.ConfigurationTask.getConfiguration(ConfigurationTask.java:55)
at org.hibernate.tool.ant.HibernateToolTask.getConfiguration(HibernateToolTask.java:302)
at org.hibernate.tool.ant.Hbm2DDLExporterTask.createExporter(Hbm2DDLExporterTask.java:51)
at org.hibernate.tool.ant.ExporterTask.execute(ExporterTask.java:39)
at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:186)
... 32 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6 seconds
[INFO] Finished at: Tue Dec 16 13:42:44 PST 2008
[INFO] Final Memory: 15M/29M
[INFO] ------------------------------------------------------------------------
We would like to request to add the Envers support for the Joined inheritance strategy entities.
Thanks.
Louie Liu
--
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
17 years, 7 months
[Hibernate-JIRA] Created: (HHH-3661) Optimistic's locking version number is incorrectly applied to the Entity in some cases
by Juan F Cervera (JIRA)
Optimistic's locking version number is incorrectly applied to the Entity in some cases
--------------------------------------------------------------------------------------
Key: HHH-3661
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3661
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.3.1
Environment: Hibernate 3.3.1.GA and Informix 10
Reporter: Juan F Cervera
Hi I have found an issue using optimistic locking and I think it's probably a bug.
The situation is the following:
a) I use optimistic locking
b) I have a legacy database where the optimistic locking field is controlled by triggers, so I use generated="always" in the mapping file for the version field (I don't think this is related to the problem, but wanted to clarify)
c) The Entity has a <bag> collection that can be empty (null)
d) At some point the collection is changed to something else than null, in my case this is happening within the same transaction, after creating the Entity, but this doesn't seem to be required for the problem to happen.
The above scenario produces a StaleStateException.
For what I see Hibernate first inserts the new record, then it does an update because we have added the collection but it uses the wrong version number, which produces the exception.
After some debugging I have traced down the problem, as follows:
a) As there has been a change to the Entity, Hibernate calculates a new version number (even when I have generated="always". This is not normally a problem though as it's not written to the DB.)
b) When an Entity has a collection that changes from null to something else, Hibernate substitutes the normal collection for the appropriate Hibernate collection type, in my case a PersistentBag. Unfortunately, the substitution process doesn't stop just at the collection, it applies to all the dirty fields, including the version number to the new calculated in a)!! This means that the version number is out of sync with the DB, which will produce problems down the line.
See the following for details:
+ Line 112 at org.hibernate.event.def.WrapVisitor.processArrayOrNewCollection forces the substitution by not returning new persistentCollection
+ This gets propagates several layers until it reaches the boolean "substitute" in line 148 at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity
+ This variable enforces the substitution in the line 156, where the version number gets updated to a new value which doesn't exist yet in the database, as the record has not been updated with it yet.
c) When the update happens, Hibernate queries the Entity for it's version number because it's using optimistic locking, and as this has been updated in b) with a new value that doesn't match the record in the database nothing gets updated
See following for details:
+ The "previous" version number is retrieved in the line 96 at org.hibernate.action.EntityUpdateAction.execute
d) Hibernate checks how many records have been updated, in this case 0 as the version number was wrong. Then it interprets this as a StaleStateException
Unfortunately I don't know enough about Hibernate to be able to propose a working solution. I think the fact that a full update of the Entity, including the new calculated version number, is forced in step b) is the issue and that the version number should have been left as it was.
How many other scenarios, apart from changing a null collection to one with data, would produce substitute to be "true" I don't know, but I expect all those cases to produce problems with optimistic locking in the same way.
I have work around for system that use the DB to control the version numbers instead of Hibernate (normally through triggers). In these systems it's possible to set optimistic-lock="false" in the collection, which would prevent the version number changing for updates on that field, so the update on b) would be fine. Unfortunately, if some other property changes along with the null collection, the version number will change because of those other properties. So in order to be sure I don't have issues I have had to set optimistic-lock="false" in all components/properties/collections.
One more thing, I think this issue is probably the cause to the problem reported in HHH-2796, as the symptoms look similar.
Let me know if you have any questions.
Thanks
--
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
17 years, 7 months
[Hibernate-JIRA] Deleted: (HHH-3658) using c3p0 connection Informix7.2
by Gail Badner (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3658?page=c... ]
Gail Badner deleted HHH-3658:
-----------------------------
> using c3p0 connection Informix7.2
> ---------------------------------
>
> Key: HHH-3658
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3658
> Project: Hibernate Core
> Issue Type: Bug
> Environment: Informix7.2, jdk1.5, Informix Dialect Version 2.21JC5, Hibernate3.3 ,c3p0-0.9.12
> Reporter: jean jj
>
> Hi I am using Hibernate 3 with JDK1.5 and Informix 7.2 and driver version 2.21JC5 and c3p0-0.9.12
> INFO - Initializing connection provider: org.hibernate.connection.C3P0ConnectionProvider
> INFO - C3P0 using driver: com.informix.jdbc.IfxDriver at URL: jdbc:informix-sqli://xxxxxx:xxxx/xx:INFORMIXSERVER=xxx
> INFO - Connection properties: {user=isuadmus, password=****}
> INFO - autocommit mode: false
> INFO - Initializing c3p0 pool... com.mchange.v2.c3p0.PoolBackedDataSource@df452eda [ connectionPoolDataSource -> com.mchange.v2.c3p0.WrapperConnectionPoolDataSource@2cdc0f6d [ acquireIncrement -> 3, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionCustomizerClassName -> null, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, debugUnreturnedConnectionStackTraces -> false, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, identityToken -> 1hd3ogc7yh0nhwh9oik8b|871e65, idleConnectionTestPeriod -> 0, initialPoolSize -> 5, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 0, maxIdleTimeExcessConnections -> 0, maxPoolSize -> 20, maxStatements -> 0, maxStatementsPerConnection -> 0, minPoolSize -> 5, nestedDataSource -> com.mchange.v2.c3p0.DriverManagerDataSource@e45de01f [ description -> null, driverClass -> null, factoryClassLocation -> null, identityToken -> 1hd3ogc7yh0nhwh9oik8b|ae1393, jdbcUrl -> jdbc:informix-sqli://140.127.191.1:8347/isuadmin:INFORMIXSERVER=sol8_tcp, properties -> {user=******, password=******} ], preferredTestQuery -> null, propertyCycle -> 0, testConnectionOnCheckin -> false, testConnectionOnCheckout -> false, unreturnedConnectionTimeout -> 0, usesTraditionalReflectiveProxies -> false; userOverrides: {} ], dataSourceName -> null, factoryClassLocation -> null, identityToken -> 1hd3ogc7yh0nhwh9oik8b|dcb6b4, numHelperThreads -> 3 ]
> INFO - Database has transactions
> INFO - Database has transactions
> java.sql.SQLWarning: Database has transactions
> at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:125)
> at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:149)
> at com.informix.jdbc.IfxSqliConnect.addWarning(IfxSqliConnect.java:1817)
> at com.informix.jdbc.IfxSqliConnect.setWarnings(IfxSqliConnect.java:3935)
> at com.informix.jdbc.IfxSqliConnect.OpenDbInit(IfxSqliConnect.java:2591)
> at com.informix.jdbc.IfxSqliConnect.setDatabaseOpen(IfxSqliConnect.java:2465)
> at com.informix.jdbc.IfxSqli.callsetDatabaseOpen(IfxSqli.java:2496)
> at com.informix.jdbc.IfxSqli.executeOpenDatabase(IfxSqli.java:1712)
> at com.informix.jdbc.IfxSqliConnect.<init>(IfxSqliConnect.java:1242)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at com.informix.jdbc.IfxDriver.connect(IfxDriver.java:243)
> at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)
> at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)
> at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)
> at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)
> at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)
> at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)
> at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810)
> at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
> INFO - Database selected
> java.sql.SQLWarning: Database selected
> at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:125)
> at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:149)
> at com.informix.jdbc.IfxSqliConnect.addWarning(IfxSqliConnect.java:1817)
> at com.informix.jdbc.IfxSqliConnect.setWarnings(IfxSqliConnect.java:3941)
> at com.informix.jdbc.IfxSqliConnect.OpenDbInit(IfxSqliConnect.java:2591)
> at com.informix.jdbc.IfxSqliConnect.setDatabaseOpen(IfxSqliConnect.java:2465)
> at com.informix.jdbc.IfxSqli.callsetDatabaseOpen(IfxSqli.java:2496)
> at com.informix.jdbc.IfxSqli.executeOpenDatabase(IfxSqli.java:1712)
> at com.informix.jdbc.IfxSqliConnect.<init>(IfxSqliConnect.java:1242)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at com.informix.jdbc.IfxDriver.connect(IfxDriver.java:243)
> at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)
> at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)
> at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)
> at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)
> at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)
> at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)
> at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810)
> at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
> INFO - Database server running in secondary mode.
> java.sql.SQLWarning: Database server running in secondary mode.
> at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:125)
> at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:149)
> at com.informix.jdbc.IfxSqliConnect.addWarning(IfxSqliConnect.java:1817)
> at com.informix.jdbc.IfxSqliConnect.setWarnings(IfxSqliConnect.java:3951)
> at com.informix.jdbc.IfxSqliConnect.OpenDbInit(IfxSqliConnect.java:2591)
> at com.informix.jdbc.IfxSqliConnect.setDatabaseOpen(IfxSqliConnect.java:2465)
> at com.informix.jdbc.IfxSqli.callsetDatabaseOpen(IfxSqli.java:2496)
> at com.informix.jdbc.IfxSqli.executeOpenDatabase(IfxSqli.java:1712)
> at com.informix.jdbc.IfxSqliConnect.<init>(IfxSqliConnect.java:1242)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at com.informix.jdbc.IfxDriver.connect(IfxDriver.java:243)
> at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)
> at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)
> at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)
> at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)
> at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)
> at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)
> at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810)
> at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
> INFO - Database has transactions
> java.sql.SQLWarning: Database has transactions
> at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:125)
> at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:149)
> at com.informix.jdbc.IfxSqliConnect.addWarning(IfxSqliConnect.java:1817)
> at com.informix.jdbc.IfxSqliConnect.setWarnings(IfxSqliConnect.java:3935)
> at com.informix.jdbc.IfxSqliConnect.OpenDbInit(IfxSqliConnect.java:2591)
> at com.informix.jdbc.IfxSqliConnect.setDatabaseOpen(IfxSqliConnect.java:2465)
> at com.informix.jdbc.IfxSqli.callsetDatabaseOpen(IfxSqli.java:2496)
> at com.informix.jdbc.IfxSqli.executeOpenDatabase(IfxSqli.java:1712)
> at com.informix.jdbc.IfxSqliConnect.<init>(IfxSqliConnect.java:1242)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at com.informix.jdbc.IfxDriver.connect(IfxDriver.java:243)
> at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)
> at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)
> at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)
> at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)
> at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)
> at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)
> at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810)
> at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
> hibernate.cfg.xml
> <hibernate-configuration>
> <session-factory>
> <property name="dialect">
> org.hibernate.dialect.InformixDialect
> </property>
> <property name="connection.driver_class">
> com.informix.jdbc.IfxDriver
> </property>
> <property name="connection.url">
> jdbc:informix-sqli://xxxx:xxxx/xxxx:INFORMIXSERVER=xxxx
> </property>
> <property name="connection.username">xxxx</property>
> <property name="connection.password">xxxx</property>
> <property name="show_sql">true</property>
> <property name="hibernate.connection.provider_class">org.hibernate.connection.C3P0ConnectionProvider</property>
> <property name="hibernate.c3p0.min_size">5</property>
> <property name="hibernate.c3p0.max_size">20</property>
> <property name="hibernate.c3p0.acquire_increment">0</property>
> <property name="hibernate.c3p0.timeout">300</property>
> <property name="hibernate.c3p0.max_statements">0</property>
> <property name="hibernate.c3p0.idle_test_period">100</property>
> <mapping resource="xxxx.hbm.xml" />
> </session-factory>
> </hibernate-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
17 years, 7 months
[Hibernate-JIRA] Created: (HHH-3660) Allow for "on-delete" attribute on "one-to-one" mapping
by Eric Sirianni (JIRA)
Allow for "on-delete" attribute on "one-to-one" mapping
-------------------------------------------------------
Key: HHH-3660
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3660
Project: Hibernate Core
Issue Type: Improvement
Components: core
Affects Versions: 3.3.1
Reporter: Eric Sirianni
Currently, specifying the attribute on-delete="cascade" in the <key> element within a collection mapping indicates to hibernate that the delete will be automatically cascaded within the database (as opposed to hibernate executing the delete itself). In other words, the foreign key for the collection table was created with ON CASCADE DELETE behavior.
There is currently no way to specify the on-delete attribute for <one-to-one> mappings. This means that hibernate will need to execute delete statements for the child end of a one-to-one association instead of letting the database do the work.
Please enhance <one-to-one> mappings to have "on-delete" awareness.
--
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
17 years, 7 months
[Hibernate-JIRA] Created: (HHH-3658) using c3p0 connection Informix7.2
by jean jj (JIRA)
using c3p0 connection Informix7.2
---------------------------------
Key: HHH-3658
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3658
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.3.0.GA
Environment: Informix7.2, jdk1.5, Informix Dialect Version 2.21JC5, Hibernate3.3 ,c3p0-0.9.12
Reporter: jean jj
Hi I am using Hibernate 3 with JDK1.5 and Informix 7.2 and driver version 2.21JC5 and c3p0-0.9.12
INFO - Initializing connection provider: org.hibernate.connection.C3P0ConnectionProvider
INFO - C3P0 using driver: com.informix.jdbc.IfxDriver at URL: jdbc:informix-sqli://xxxxxx:xxxx/xx:INFORMIXSERVER=xxx
INFO - Connection properties: {user=isuadmus, password=****}
INFO - autocommit mode: false
INFO - Initializing c3p0 pool... com.mchange.v2.c3p0.PoolBackedDataSource@df452eda [ connectionPoolDataSource -> com.mchange.v2.c3p0.WrapperConnectionPoolDataSource@2cdc0f6d [ acquireIncrement -> 3, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionCustomizerClassName -> null, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, debugUnreturnedConnectionStackTraces -> false, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, identityToken -> 1hd3ogc7yh0nhwh9oik8b|871e65, idleConnectionTestPeriod -> 0, initialPoolSize -> 5, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 0, maxIdleTimeExcessConnections -> 0, maxPoolSize -> 20, maxStatements -> 0, maxStatementsPerConnection -> 0, minPoolSize -> 5, nestedDataSource -> com.mchange.v2.c3p0.DriverManagerDataSource@e45de01f [ description -> null, driverClass -> null, factoryClassLocation -> null, identityToken -> 1hd3ogc7yh0nhwh9oik8b|ae1393, jdbcUrl -> jdbc:informix-sqli://140.127.191.1:8347/isuadmin:INFORMIXSERVER=sol8_tcp, properties -> {user=******, password=******} ], preferredTestQuery -> null, propertyCycle -> 0, testConnectionOnCheckin -> false, testConnectionOnCheckout -> false, unreturnedConnectionTimeout -> 0, usesTraditionalReflectiveProxies -> false; userOverrides: {} ], dataSourceName -> null, factoryClassLocation -> null, identityToken -> 1hd3ogc7yh0nhwh9oik8b|dcb6b4, numHelperThreads -> 3 ]
INFO - Database has transactions
INFO - Database has transactions
java.sql.SQLWarning: Database has transactions
at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:125)
at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:149)
at com.informix.jdbc.IfxSqliConnect.addWarning(IfxSqliConnect.java:1817)
at com.informix.jdbc.IfxSqliConnect.setWarnings(IfxSqliConnect.java:3935)
at com.informix.jdbc.IfxSqliConnect.OpenDbInit(IfxSqliConnect.java:2591)
at com.informix.jdbc.IfxSqliConnect.setDatabaseOpen(IfxSqliConnect.java:2465)
at com.informix.jdbc.IfxSqli.callsetDatabaseOpen(IfxSqli.java:2496)
at com.informix.jdbc.IfxSqli.executeOpenDatabase(IfxSqli.java:1712)
at com.informix.jdbc.IfxSqliConnect.<init>(IfxSqliConnect.java:1242)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at com.informix.jdbc.IfxDriver.connect(IfxDriver.java:243)
at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)
at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)
at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)
at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810)
at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
INFO - Database selected
java.sql.SQLWarning: Database selected
at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:125)
at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:149)
at com.informix.jdbc.IfxSqliConnect.addWarning(IfxSqliConnect.java:1817)
at com.informix.jdbc.IfxSqliConnect.setWarnings(IfxSqliConnect.java:3941)
at com.informix.jdbc.IfxSqliConnect.OpenDbInit(IfxSqliConnect.java:2591)
at com.informix.jdbc.IfxSqliConnect.setDatabaseOpen(IfxSqliConnect.java:2465)
at com.informix.jdbc.IfxSqli.callsetDatabaseOpen(IfxSqli.java:2496)
at com.informix.jdbc.IfxSqli.executeOpenDatabase(IfxSqli.java:1712)
at com.informix.jdbc.IfxSqliConnect.<init>(IfxSqliConnect.java:1242)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at com.informix.jdbc.IfxDriver.connect(IfxDriver.java:243)
at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)
at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)
at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)
at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810)
at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
INFO - Database server running in secondary mode.
java.sql.SQLWarning: Database server running in secondary mode.
at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:125)
at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:149)
at com.informix.jdbc.IfxSqliConnect.addWarning(IfxSqliConnect.java:1817)
at com.informix.jdbc.IfxSqliConnect.setWarnings(IfxSqliConnect.java:3951)
at com.informix.jdbc.IfxSqliConnect.OpenDbInit(IfxSqliConnect.java:2591)
at com.informix.jdbc.IfxSqliConnect.setDatabaseOpen(IfxSqliConnect.java:2465)
at com.informix.jdbc.IfxSqli.callsetDatabaseOpen(IfxSqli.java:2496)
at com.informix.jdbc.IfxSqli.executeOpenDatabase(IfxSqli.java:1712)
at com.informix.jdbc.IfxSqliConnect.<init>(IfxSqliConnect.java:1242)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at com.informix.jdbc.IfxDriver.connect(IfxDriver.java:243)
at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)
at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)
at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)
at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810)
at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
INFO - Database has transactions
java.sql.SQLWarning: Database has transactions
at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:125)
at com.informix.util.IfxWarnMsg.getSQLWarning(IfxWarnMsg.java:149)
at com.informix.jdbc.IfxSqliConnect.addWarning(IfxSqliConnect.java:1817)
at com.informix.jdbc.IfxSqliConnect.setWarnings(IfxSqliConnect.java:3935)
at com.informix.jdbc.IfxSqliConnect.OpenDbInit(IfxSqliConnect.java:2591)
at com.informix.jdbc.IfxSqliConnect.setDatabaseOpen(IfxSqliConnect.java:2465)
at com.informix.jdbc.IfxSqli.callsetDatabaseOpen(IfxSqli.java:2496)
at com.informix.jdbc.IfxSqli.executeOpenDatabase(IfxSqli.java:1712)
at com.informix.jdbc.IfxSqliConnect.<init>(IfxSqliConnect.java:1242)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at com.informix.jdbc.IfxDriver.connect(IfxDriver.java:243)
at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)
at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)
at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)
at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810)
at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
hibernate.cfg.xml
<hibernate-configuration>
<session-factory>
<property name="dialect">
org.hibernate.dialect.InformixDialect
</property>
<property name="connection.driver_class">
com.informix.jdbc.IfxDriver
</property>
<property name="connection.url">
jdbc:informix-sqli://xxxx:xxxx/xxxx:INFORMIXSERVER=xxxx
</property>
<property name="connection.username">xxxx</property>
<property name="connection.password">xxxx</property>
<property name="show_sql">true</property>
<property name="hibernate.connection.provider_class">org.hibernate.connection.C3P0ConnectionProvider</property>
<property name="hibernate.c3p0.min_size">5</property>
<property name="hibernate.c3p0.max_size">20</property>
<property name="hibernate.c3p0.acquire_increment">0</property>
<property name="hibernate.c3p0.timeout">300</property>
<property name="hibernate.c3p0.max_statements">0</property>
<property name="hibernate.c3p0.idle_test_period">100</property>
<mapping resource="xxxx.hbm.xml" />
</session-factory>
</hibernate-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
17 years, 7 months