September 2011 - hibernate-issues

[Hibernate-JIRA] Created: (HCANN-10) JPA OneToOne(optional=true) not supported, supported alternative NotFound() is hibernate-proprietary!

by Bruno Melloni (JIRA)

JPA OneToOne(optional=true) not supported, supported alternative NotFound() is hibernate-proprietary! ----------------------------------------------------------------------------------------------------- Key: HCANN-10 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-10 Project: Hibernate Commons Annotations Issue Type: Bug Environment: Hibernate 3.3.1, annotations 3.4.0, MsSQL DB. Reporter: Bruno Melloni Rejected issue ANN-725 covers this partially. I might have misunderstood, but it seems the reason for rejecting is that @NotFound provides the same capability. All information I could find for JPA and other ORM tools indicates that this capability is supplied by @OneToOne(optional=true). Hibernate seems to be the lone ORM tool that requires the use of a proprietary annotation: @NotFound. @NotFound works, but the problem is that it makes the application no longer be pure-JPA. Not supporting pure-JPA outer joins would seem to be a major bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

6
16
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-931) CollectionUpdateEventTest fails from the commans line when run after a unit test which extends JPATestcase

by Hardy Ferentschik (JIRA)

CollectionUpdateEventTest fails from the commans line when run after a unit test which extends JPATestcase ---------------------------------------------------------------------------------------------------------- Key: HSEARCH-931 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-931 Project: Hibernate Search Issue Type: Bug Components: tests Affects Versions: 4.0.0.Beta2 Reporter: Hardy Ferentschik Fix For: 4.0.0.CR1 The first problem was that we could not reproduce the problem and that was due to the fact that the execution order of tests varies depending on the OS. The surefire plugin has the _runOrder_ property to define the order. The default is _filesystem_ which has different results on Mac vs Linux. On Mac the tests are run in alphabetical order on Linux in "random" order. If the tests are ordered alphabetically JPA tests are run after _CollectionUpdateEventTest_ and all works fine. If the order is random and a JPA test runs first we get the following error: {noformat} ------------------------------------------------------------------------------- Test set: org.hibernate.search.test.engine.optimizations.CollectionUpdateEventTest ------------------------------------------------------------------------------- Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.574 sec <<< FAILURE! testWithClassBridge(org.hibernate.search.test.engine.optimizations.CollectionUpdateEventTest) Time elapsed: 0.242 sec <<< FAILURE! org.junit.ComparisonFailure: [catalogItems should have been initialized] expected:<[tru]e> but was:<[fals]e> 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:513) at org.fest.assertions.ConstructorInvoker.newInstance(ConstructorInvoker.java:36) at org.fest.assertions.ComparisonFailureFactory.newComparisonFailure(ComparisonFailureFactory.java:60) at org.fest.assertions.ComparisonFailureFactory.comparisonFailure(ComparisonFailureFactory.java:46) at org.fest.assertions.Fail.comparisonFailed(Fail.java:83) at org.fest.assertions.Fail.failIfNotEqual(Fail.java:71) at org.fest.assertions.GenericAssert.isEqualTo(GenericAssert.java:217) at org.fest.assertions.BooleanAssert.isEqualTo(BooleanAssert.java:73) at org.fest.assertions.BooleanAssert.isTrue(BooleanAssert.java:55) at org.hibernate.search.test.engine.optimizations.CollectionUpdateEventTest.testScenario(CollectionUpdateEventTest.java:98) at org.hibernate.search.test.engine.optimizations.CollectionUpdateEventTest.testWithClassBridge(CollectionUpdateEventTest.java:52) 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) {noformat} At the moment we explicitly set the _runOrder_ option in the surefire plugin to _alphabetical_ which will make the tests pass. To trigger the failure you can change _runOrder_ to _reversealphabetical_ and run: {code} mvn test -Dtest=org.hibernate.search.test.engine.optimizations.CollectionUpdateEventTest,EntityManagerTest {code} Also important for this issue is that the surefire plugin is configured to only fork _once_ for all tests, so the same JVM is shared between tests. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4854) Make constraint violation name extraction language neutral

by Jonas Olsson (JIRA)

Make constraint violation name extraction language neutral ---------------------------------------------------------- Key: HHH-4854 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4854 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.2.6 Environment: Oracle 8 or later Reporter: Jonas Olsson The ViolatedConstraintNameExtracter of Oracle8iDialect uses the following pattern for extracting the contraint violated: return extractUsingTemplate( "constraint (", ") violated", sqle.getMessage() ); and is highly error message language dependent. Changing to: return extractUsingTemplate( "(", ")", sqle.getMessage() ); would eliminate this while still getting the constraint name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-887) Version conflict of dependency jackson-mapper-asl with the one included in JBoss AS7

by Sanne Grinovero (JIRA)

Version conflict of dependency jackson-mapper-asl with the one included in JBoss AS7 ------------------------------------------------------------------------------------ Key: HSEARCH-887 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-887 Project: Hibernate Search Issue Type: Bug Components: build Reporter: Sanne Grinovero Priority: Blocker Fix For: 4.0 It seems the version of Apache Avro we introduced as a new dependency is depending on jackson-mapper-asl, which is included in AS7 as well, but using a different version. We should see if we can use the same as AS7, if the dependency can be removed, or if we should verify if we can take advantage of AS7's new super isolation features. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-930) Follow up Jenkins feedback on Hibernate Search build on Windows

by Emmanuel Bernard (JIRA)

Follow up Jenkins feedback on Hibernate Search build on Windows --------------------------------------------------------------- Key: HSEARCH-930 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-930 Project: Hibernate Search Issue Type: Task Affects Versions: 4.0.0.Beta2 Reporter: Emmanuel Bernard Fix For: 4.0.0.CR1 Build on Windows are not stable but for weird reasons. http://hudson.qa.jboss.com/hudson/job/hibernate-search-master-windows/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3239) MarkerObject should be serializable when using with swf

by Goran Blankendal (JIRA)

MarkerObject should be serializable when using with swf ------------------------------------------------------- Key: HHH-3239 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3239 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6 and Spring Webflow 2.0 Reporter: Goran Blankendal You get a java.io.NotSerializableException: org.hibernate.util.MarkerObject when using hibernate in a persistence context in SWF 2 See http://forum.springframework.org/showthread.php?t=51738 and http://forum.hibernate.org/viewtopic.php?t=985226 The MarkerObject should be serializable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6705) SQL datatypes for booleans not being handled correctly

by Steve Ebersole (JIRA)

SQL datatypes for booleans not being handled correctly ------------------------------------------------------ Key: HHH-6705 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6705 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.CR4 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.next Perhaps due to changes for metamodel... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2774) Call ResultTransformer.transformList() even if the list argument is an empty list

by Christian Bauer (JIRA)

Call ResultTransformer.transformList() even if the list argument is an empty list --------------------------------------------------------------------------------- Key: HHH-2774 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2774 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: Christian Bauer Priority: Trivial I have a case where a ResultTransformer is doing all the work in transformTuple() and always returns null from that method. The transformed target state is held internally in the ResultTransformer instance (I basically turn many tuples into one). Now I can't get this state out of the ResultTransformer because transformList() is not called after transformTuple(). It would be better if transformList() is called even if the list of tuples returned by transformTuple() is empty. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6680) 2L caching appears to ignore collections

by Ben Hood (JIRA)

2L caching appears to ignore collections ---------------------------------------- Key: HHH-6680 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6680 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.6.7 Environment: 3.6.7 on Derby 10.8.1.2 and Oracle 11g Reporter: Ben Hood I have a scenario where a (read-mostly) mapped collection is eagerly loaded with the parent object, but when I retrieve the graph, the 2L cache appears to get ignored and the data is hydrated from the DB. I have created a test case to reproduce this issue as a runnable Maven project on Github : https://github.com/0x6e6562/hibernate_2L -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6609) Provide a way to supply prebuild ConnectionProvider to Hibernate

by Christoph Läubrich (JIRA)

Provide a way to supply prebuild ConnectionProvider to Hibernate ---------------------------------------------------------------- Key: HHH-6609 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6609 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.6.7 Reporter: Christoph Läubrich Currently it is only possible to provide a ConnectionProvider via the property Environment.CONNECTION_PROVIDER which only accepts a class-name which later is instantiated via ConnectionProviderFactory: private static ConnectionProvider initializeConnectionProviderFromConfig(String providerClass) { ConnectionProvider connections; try { log.info( "Initializing connection provider: " + providerClass ); connections = (ConnectionProvider) ReflectHelper.classForName( providerClass ).newInstance(); } catch ( Exception e ) { log.error( "Could not instantiate connection provider", e ); throw new HibernateException( "Could not instantiate connection provider: " + providerClass ); } return connections; } This aproch is okay for connectionprovider which are very generic and can build up completely by the configuration, but under some circumstances the creation and setup is out of scope of the Provider implementation class. For this case it would be helpfull to have a configuration property like Environment.CONNECTION_PROVIDER_REFERENCE and a static public Method in the ConnectionProviderFactory like ConnectionProviderFactory.addConnectionProviderReference(ConnectionProvider provider, String reference) So it would be possible to make something like this: ConnectionProvider provider = new MySpecialProvider(x, y, z); provider.doSpecialSetup(d); ConnectionProviderFactory.addConnectionProviderReference(provider, "MySpecialProvider"); . . . Configuration configuration = new Configuration(); configuration.setProperty(Environment.CONNECTION_PROVIDER_REFERENCE, "MySpecialProvider"); SessionFactory factory = configuration.buildSessionFactory(); The only alternative to this in current days is to create a ConnectionProvider class which completely relies on static setup methods, making the code relativly complicated and error prone, as well as introducing class not found problems if the provider is not in the same class loader context as hibernate or the module which creates the configuration (for example in OSGi applications). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2011