June 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5478) Update Ehcache capabilities in the section [21.2. The Second Level Cache] of the documentation

by Pascal Thivent (JIRA)

Update Ehcache capabilities in the section [21.2. The Second Level Cache] of the documentation ---------------------------------------------------------------------------------------------- Key: HHH-5478 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5478 Project: Hibernate Core Issue Type: Improvement Components: documentation Reporter: Pascal Thivent Priority: Minor According to the [Hibernate Second Level Cache|http://ehcache.org/documentation/hibernate.html] documentation on the Ehcache website, Ehcache 2.0+ is cluster safe: {quote} h3. [Is Ehcache Cluster Safe?|http://ehcache.org/documentation/hibernate.html#Is_Ehcache_Cluster_...] hibernate.org maintains a table listing the providers. While ehcache works as a distributed cache for Hibernate, it is not listed as "Cluster Safe". What this means is that `Hibernate's lock and unlock methods are not implemented. Changes in one node will be applied without locking. This may or may not be a noticeable problem. In Ehcache 1.7 when using Terracotta, this cannot happen as access to the clustered cache itself is controlled with read locks and write locks. In Ehcache 2.0 when using Terracotta, the lock and unlock methods tie-in to the underlying clustered cache locks. We expect Ehcache 2.0 to be marked as cluster safe in new versions of the Hibernate documentation. {quote} And as of Ehcache 2.1.0, Ehcache now supports the transactional strategy. From the [JPA|http://ehcache.org/documentation/jta.html] page: {quote} h3. Hibernate Transactions Ehcache is a "transactional" cache for Hibernate purposes. The <<<net.sf.ehcache.hibernate.EhCacheRegionFactory>>> has support for Hibernate entities configured with <cache usage="transactional"/>. {quote} Shouldn't the cache provider table of the section [21.2. The Second Level Cache|http://docs.jboss.org/hibernate/core/3.6/reference/en-US/html/perfo...] and the cache compatibility matrix of the section [21.2.6. Cache-provider/concurrency-strategy compatibility|http://docs.jboss.org/hibernate/core/3.6/reference/en-US/ht...] be updated to reflect this (or at least make it clear that this is possible, be it through third party support)? -- 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

12 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2646) Informix 10 dialect with BLOB/CLOB support

by Thomas Much (JIRA)

Informix 10 dialect with BLOB/CLOB support ------------------------------------------ Key: HHH-2646 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2646 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.4.sp1 Environment: Informix 10 Reporter: Thomas Much Priority: Minor We discovered that Informix 10 works well with mapping types "blob" and "clob" if we use our own dialect that's simply derived from the existing Informix dialect by adding the two missing types: public class Informix10Dialect extends InformixDialect { public Informix10Dialect() { super(); registerColumnType( Types.BLOB, "blob" ); registerColumnType( Types.CLOB, "clob" ); } } We suggest adding this new dialect to Hibernate Core. (This is similar to issue HHH-2523, but here "clob" is mapped, too.) -- 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

12 years, 11 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5500) Extend AuditReader interface with findRevisions() method

by Erik-Berndt Scheper (JIRA)

Extend AuditReader interface with findRevisions() method -------------------------------------------------------- Key: HHH-5500 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5500 Project: Hibernate Core Issue Type: Sub-task Components: envers Reporter: Erik-Berndt Scheper To improve performance, it would be benificial to extend the Envers AuditReader interface, so that a list of audited entities can be retrieved in one query. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5663) Add read/write wrappers to org.hibernate.metamodel.relational.Column

by Steve Ebersole (JIRA)

Add read/write wrappers to org.hibernate.metamodel.relational.Column -------------------------------------------------------------------- Key: HHH-5663 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5663 Project: Hibernate Core Issue Type: Sub-task Reporter: Steve Ebersole -- 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

12 years, 11 months

2
9
0 / 0

[Hibernate-JIRA] Created: (HHH-6276) org.hibernate.test.cache.ehcache.EhCacheRegionFactoryImpl fails due to no slf4j in test configuration

by Strong Liu (JIRA)

org.hibernate.test.cache.ehcache.EhCacheRegionFactoryImpl fails due to no slf4j in test configuration ----------------------------------------------------------------------------------------------------- Key: HHH-6276 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6276 Project: Hibernate Core Issue Type: Bug Components: testsuite Affects Versions: 4.0.0.Alpha3 Reporter: Strong Liu Assignee: Strong Liu Fix For: 4.0.0.Beta1 org.hibernate.testing.junit4.CallbackException: org.hibernate.testing.junit4.BaseCoreFunctionalTestCase#buildSessionFactory at org.hibernate.testing.junit4.TestClassMetadata.invokeCallback(TestClassMetadata.java:199) at org.hibernate.testing.junit4.TestClassMetadata.performCallbacks(TestClassMetadata.java:190) at org.hibernate.testing.junit4.TestClassMetadata.performBeforeClassCallbacks(TestClassMetadata.java:181) at org.hibernate.testing.junit4.BeforeClassCallbackHandler.evaluate(BeforeClassCallbackHandler.java:42) at org.hibernate.testing.junit4.AfterClassCallbackHandler.evaluate(AfterClassCallbackHandler.java:42) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:51) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:63) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:49) 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.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:75) at $Proxy3.processTestClass(Unknown Source) at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:86) 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.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.messaging.remote.internal.MethodInvocationUnmarshallingDispatch.dispatch(MethodInvocationUnmarshallingDispatch.java:48) at org.gradle.messaging.dispatch.DiscardOnFailureDispatch.dispatch(DiscardOnFailureDispatch.java:31) at org.gradle.messaging.dispatch.AsyncDispatch.dispatchMessages(AsyncDispatch.java:129) at org.gradle.messaging.dispatch.AsyncDispatch.access$000(AsyncDispatch.java:33) at org.gradle.messaging.dispatch.AsyncDispatch$1.run(AsyncDispatch.java:69) at org.gradle.messaging.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:63) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.NoSuchMethodError: org.slf4j.helpers.MessageFormatter.format(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/String; at org.slf4j.impl.Log4jLoggerAdapter.info(Log4jLoggerAdapter.java:318) at org.hibernate.annotations.common.Version.<clinit>(Version.java:37) at org.hibernate.annotations.common.reflection.java.JavaReflectionManager.<clinit>(JavaReflectionManager.java:73) at org.hibernate.cfg.Configuration.createReflectionManager(Configuration.java:2356) at org.hibernate.cfg.Configuration.createReflectionManager(Configuration.java:2352) at org.hibernate.cfg.Configuration.reset(Configuration.java:267) at org.hibernate.cfg.Configuration.<init>(Configuration.java:258) at org.hibernate.cfg.Configuration.<init>(Configuration.java:262) at org.hibernate.testing.junit4.BaseCoreFunctionalTestCase.constructConfiguration(BaseCoreFunctionalTestCase.java:132) at org.hibernate.testing.junit4.BaseCoreFunctionalTestCase.buildConfiguration(BaseCoreFunctionalTestCase.java:122) at org.hibernate.testing.junit4.BaseCoreFunctionalTestCase.buildSessionFactory(BaseCoreFunctionalTestCase.java:115) 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.hibernate.testing.junit4.TestClassMetadata.invokeCallback(TestClassMetadata.java:196) ... 33 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

12 years, 11 months

1
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2059) Section 19.2 of the documentation does not show Ehcache as supporting clusters. It does.

by Greg Luck (JIRA)

Section 19.2 of the documentation does not show Ehcache as supporting clusters. It does. ----------------------------------------------------------------------------------------- Key: HHH-2059 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2059 Project: Hibernate3 Type: Bug Components: documentation Versions: 3.2.0 cr1, 3.2.0.cr2, 3.2.0.cr3, 3.2.0.cr4 Reporter: Greg Luck Priority: Minor Section 19.2 of the documentation does not show Ehcache as supporting clusters. It does. The only reason I am asking for this is that people are confused about it and are asking me questions over at the ehcache project. e.g. see the following email to the list. From: p.perrucci(a)gmail.com Subject: [ehcache-list] Using ehcache as a clustered cache in hibernate3 Date: 6 September 2006 6:29:21 PM GMT+10:00 To: ehcache-list(a)lists.sourceforge.net Hi all, current version of ehcache implements distributed caching but hibernate3 docs says that ehcache is not cluster safe. Anyone know the reason why it's not possible to use ehcache in such a scenario? Thanks Paolo ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642_... ehcache-list mailing list ehcache-list(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ehcache-list -- 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

12 years, 11 months

6
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3112) Upgrade EhCache dependancy to 1.2.4+

by Stevo Slavic (JIRA)

Upgrade EhCache dependancy to 1.2.4+ ------------------------------------ Key: HHH-3112 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3112 Project: Hibernate3 Issue Type: Improvement Components: caching (L2) Affects Versions: 3.2.5 Reporter: Stevo Slavic Priority: Trivial Hibernate is widely used in conjunction with Spring framework. Spring framework as of version 2.0 expects EhCache to be 1.2.4+. When using both EhCache 1.2.4+ and Hibernate 3.2.5.ga as dependency in same maven project but in different sub-projects, older EhCache 1.2.3 (current Hibernate 3.2.5.ga dependency) can overwrite dependency application has for newer EhCache ( http://forum.springframework.org/showthread.php?t=49956 ). If Hibernate would use 1.2.4+ EhCache there would be no need to specify separate EhCache dependency. -- 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

12 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-744) NullPointerException when using a range query on a numeric field and searching for values below a given boundary

by Nikita D (JIRA)

NullPointerException when using a range query on a numeric field and searching for values below a given boundary ----------------------------------------------------------------------------------------------------------------- Key: HSEARCH-744 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-744 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.4.0.Final Environment: Hibernate Core 3.6.3, MySQL 5.1.55 Reporter: Nikita D When using the query API to search for values below a boundary, a NullPointerException is thrown if the field is a numeric field (annotated with @NumericField). Example query: {code} Query luceneQuery = qb .range() .onField("myNumericField") .below(myMaxValue) .createQuery(); {code} The problem is in NumericFieldUtils.createNumericRangeQuery(), which always uses the "from" value to determine the class. For a "below" query, the "from" value is null. Stacktrace: {code} java.lang.NullPointerException at org.hibernate.search.bridge.util.NumericFieldUtils.createNumericRangeQuery(NumericFieldUtils.java:17) at org.hibernate.search.query.dsl.impl.ConnectedMultiFieldsRangeQueryBuilder.createQuery(ConnectedMultiFieldsRangeQueryBuilder.java:104) at org.hibernate.search.query.dsl.impl.ConnectedMultiFieldsRangeQueryBuilder.createQuery(ConnectedMultiFieldsRangeQueryBuilder.java:79) {code} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5306) Dialect resolution: Cannot set a custom dialect resolver programatically or using hibernate.cfg.xml

by Nikita D (JIRA)

Dialect resolution: Cannot set a custom dialect resolver programatically or using hibernate.cfg.xml --------------------------------------------------------------------------------------------------- Key: HHH-5306 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5306 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2, 3.5.1, 3.5.0-Final, 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1, 3.3.2 Reporter: Nikita D Priority: Minor Starting with version 3.3, Hibernate introduced an extremely useful dialect resolution feature (http://docs.jboss.org/hibernate/stable/core/reference/en/html_single/#por...). The problem is with the configuration of a custom dialect resolver: * Setting the property Environment.DIALECT_RESOLVERS in the Configuration of a SessionFactory doesn't work, because DialectFactory only reads from Environment.getProperties(), which is only the global properties (system properties plus the hibernate.properties file). * Setting a system property programatically is not safe, because the Environment class caches the system properties in a static constant, so if it's loaded before the code that sets the system property, the property will not be picked up. * The registerDialectResolver() method on DialectFactory is not public. Ideally, it should be possible to configure a custom dialect resolver by setting the property Environment.DIALECT_RESOLVERS on a Configuration object, just as one would configure an explicit dialect. Alternatively, I think an acceptable "quick fix" would be to expose the registerDialectResolver() method on DialectFactory. -- 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

12 years, 11 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-6371) Develop metamodel binding creation using a push approach

by Steve Ebersole (JIRA)

Develop metamodel binding creation using a push approach --------------------------------------------------------- Key: HHH-6371 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6371 Project: Hibernate Core Issue Type: Task Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.next However, for our normal use re-purpose the "state" stuff and act as a "normalized view of mapping information" and have binders consume that to create the bindings. -- 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

12 years, 11 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2011