September 2010 - hibernate-issues

[Hibernate-JIRA] Created: (HHH-2606) CharArrayType allways leads to dirty objects

by Aymeric Levaux (JIRA)

CharArrayType allways leads to dirty objects -------------------------------------------- Key: HHH-2606 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2606 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4 Environment: Hibernate 3.2.4 Postgresql 8.2 or Hsqldb Reporter: Aymeric Levaux Attachments: typechararray.zip When you map a property of type char[], the owning object is always considered as dirty even if untouched. I attached a unit test that reproduce the 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

15 years, 6 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5578) Support for Specj JPA1 ManyToOne Key

by Ståle W. Pedersen (JIRA)

Support for Specj JPA1 ManyToOne Key ------------------------------------ Key: HHH-5578 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5578 Project: Hibernate Core Issue Type: New Feature Components: core Affects Versions: 3.6.0.CR1 Reporter: Ståle W. Pedersen Attachments: specj_manytoonekey.diff Last piece to get support for SpecJ JPA1 ManyToOne syntax. Note that this will only be enabled if the property "hibernate.enable_specj_proprietary_syntax" is set. -- 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

15 years, 6 months

2
3
0 / 0

[Hibernate-JIRA] Created: (METAGEN-32) Update the documentation regarding the usage of the maven-processor-plugin

by Hardy Ferentschik (JIRA)

Update the documentation regarding the usage of the maven-processor-plugin -------------------------------------------------------------------------- Key: METAGEN-32 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-32 Project: Hibernate Metamodel Generator Issue Type: Task Components: build, documentation Affects Versions: 1.0.0.Final Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 1.1.0 The plugin allows now to configure the ap dependency as a plugin dependency instead of a project dependency - http://code.google.com/p/maven-annotation-plugin/issues/detail?id=20 For example: {code} <plugin> <groupId>org.bsc.maven</groupId> <artifactId>maven-processor-plugin</artifactId> <version>1.3.4</version> <executions> <execution> <id>process</id> <goals> <goal>process</goal> </goals> <phase>process-sources</phase> </execution> </executions> <dependencies> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-validator-annotation-processor</artifactId> <version>4.1.0.GA</version> <scope>compile</scope> </dependency> </dependencies> </plugin> {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

15 years, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HBX-1068) Hibernate Configurations on Eclipse Ganymede 3.4

by Ricardo M Augusto (JIRA)

Hibernate Configurations on Eclipse Ganymede 3.4 ------------------------------------------------ Key: HBX-1068 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1068 Project: Hibernate Tools Issue Type: Bug Components: eclipse Affects Versions: 3.2.1 Environment: Windows Vista 32bits, hibernate 2.6, eclipse 3.4 (Ganymede) Reporter: Ricardo M Augusto When created hibernate configuration eclipse shows: java.lang.NoClassDefFoundError: org/eclipse/ui/internal/util/SWTResourceUtil at org.hibernate.eclipse.console.workbench.xpl.AnyAdaptableLabelProvider.getImage(AnyAdaptableLabelProvider.java:166) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.getImage(WrappedViewerLabelProvider.java:117) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:165) at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:145) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:932) at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:102) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1012) at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:466) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2041) at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:827) at org.eclipse.jface.viewers.AbstractTreeViewer.createAddedElements(AbstractTreeViewer.java:340) at org.eclipse.jface.viewers.AbstractTreeViewer.internalAdd(AbstractTreeViewer.java:270) at org.eclipse.jface.viewers.TreeViewer.internalAdd(TreeViewer.java:652) at org.hibernate.eclipse.console.viewers.xpl.MTreeViewer.add(MTreeViewer.java:106) at org.eclipse.ui.progress.DeferredTreeContentManager$3.runInUIThread(DeferredTreeContentManager.java:353) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) -- 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

15 years, 6 months

7
6
0 / 0

[Hibernate-JIRA] Created: (METAGEN-33) Metamodel is not generated with @Generated annotation

by Paulo Silveira (JIRA)

Metamodel is not generated with @Generated annotation ----------------------------------------------------- Key: METAGEN-33 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-33 Project: Hibernate Metamodel Generator Issue Type: Task Components: processor Affects Versions: 1.0.0.Final Environment: hibernate 3.5.4 and final metamodel version Reporter: Paulo Silveira Assignee: Hardy Ferentschik The static meta model does not have a @Generated. This is probably the reason that avoids Eclipse compiling of the derived classes (we must clean the project, or alter the generated class and save it). The eclipselink metamodel generator works fine, and the only difference between EclipseLink generator and hibernate generator is this annotation You can see that many users are being affected by this issue in the comments here: http://relation.to/Bloggers/HibernateStaticMetamodelGeneratorAnnotationPr... -- 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

15 years, 6 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HV-380) Validator fails when a non-Hibernate persistence layer is in the classpath

by Archie Cobbs (JIRA)

Validator fails when a non-Hibernate persistence layer is in the classpath -------------------------------------------------------------------------- Key: HV-380 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-380 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.1.0.Final Reporter: Archie Cobbs Assignee: Hardy Ferentschik Attachments: HIBVALIDBUG.tar.bz2 The documentation for the Hibernate Validator states: {quote} The API is not tied to a specific application tier or programming model. It is specifically not tied to either the web tier or the persistence tier, and is available for both server-side application programming, as well as rich client Swing application developer. {quote} However, this doesn't seem to be the case. It is true that validation can be performed without any persistence layer being present. However, simply by having a non-Hibernate persistence layer such as EclipseLink in the classpath, validation fails as follows: {noformat} javax.validation.ValidationException: Call to TraversableResolver.isReachable() threw an exception at org.hibernate.validator.engine.ValidatorImpl.isValidationRequired(ValidatorImpl.java:766) at org.hibernate.validator.engine.ValidatorImpl.validateConstraint(ValidatorImpl.java:324) at org.hibernate.validator.engine.ValidatorImpl.validateConstraintsForRedefinedDefaultGroup(ValidatorImpl.java:273) at org.hibernate.validator.engine.ValidatorImpl.validateConstraintsForCurrentGroup(ValidatorImpl.java:256) at org.hibernate.validator.engine.ValidatorImpl.validateInContext(ValidatorImpl.java:210) at org.hibernate.validator.engine.ValidatorImpl.validate(ValidatorImpl.java:119) at Foo.main(Foo.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:217) at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:152) at org.apache.tools.ant.taskdefs.Java.run(Java.java:764) at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:218) at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:132) at org.apache.tools.ant.taskdefs.Java.execute(Java.java:105) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1189) at org.apache.tools.ant.Main.runBuild(Main.java:758) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) Caused by: java.lang.NullPointerException at javax.persistence.Persistence$1.isLoaded(Persistence.java:78) at org.hibernate.validator.engine.resolver.JPATraversableResolver.isReachable(JPATraversableResolver.java:62) at org.hibernate.validator.engine.resolver.DefaultTraversableResolver.isReachable(DefaultTraversableResolver.java:94) at org.hibernate.validator.engine.resolver.SingleThreadCachedTraversableResolver.isReachable(SingleThreadCachedTraversableResolver.java:47) at org.hibernate.validator.engine.ValidatorImpl.isValidationRequired(ValidatorImpl.java:757) ... 33 more {noformat} I've attached a test case. Run "ant" to see the problem. Edit {{build.xml}} to remove {{eclipselink-1.2.0.jar}} from the runtime classpath, re-run "ant", and the problem goes away. -- 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

15 years, 6 months

2
4
0 / 0

[Hibernate-JIRA] Created: (METAGEN-7) Try to find a way to be able to use @SupportedAnnotationTypes("javax.persistence.Entity") in JPAMetaModelEntityProcessor

by Hardy Ferentschik (JIRA)

Try to find a way to be able to use @SupportedAnnotationTypes("javax.persistence.Entity") in JPAMetaModelEntityProcessor ------------------------------------------------------------------------------------------------------------------------ Key: METAGEN-7 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-7 Project: Hibernate StaticMetamodel Generator Issue Type: Task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik At the moment we use @SupportedAnnotationTypes("*"). Better would be to explicitly specify @SupportedAnnotationTypes("javax.persistence.Entity"). Then the processor would only be called if there are any entities annotated with @Entity. However, this also means that the processor is not getting called at all if there is no @Entity which could be the case if all configuration is done via xml. We would need a way to make sure that the processor is called at least once to ensure xml is parsed. Other than that only entities annotated with @Entity should be passed to the processor. At the moment I don't see how we can make this happen :( -- 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

15 years, 6 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-591) Programmitic mapping not working in Seam application

by Jeff Faath (JIRA)

Programmitic mapping not working in Seam application ---------------------------------------------------- Key: HSEARCH-591 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-591 Project: Hibernate Search Issue Type: Bug Components: mapping Affects Versions: 3.2.1 Reporter: Jeff Faath Attachments: searchmapping-test.rar See this forum post: https://forum.hibernate.org/viewtopic.php?f=9&t=1006616 The progammatic mapping doesn't seem to work when used inside a Seam application with the bootstrapped EntityManagerFactory. Attached is a simple Seam application (can be built with Maven) that demonstrates the error. -- 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

15 years, 6 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HHH-5343) Issue with lazy loading of composite key for 1:1 entity relationships

by Jim O'Callaghan (JIRA)

Issue with lazy loading of composite key for 1:1 entity relationships --------------------------------------------------------------------- Key: HHH-5343 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5343 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.1 Environment: hibernate-envers 3.5.1-Final, MySQL Reporter: Jim O'Callaghan This issue was originally raised against envers 1.2.2.GA-hibernate-3.3, hibernate-core 3.3.1.GA, under the previous Envers JIRA at https://jira.jboss.org/browse/ENVERS-77 - a test case is attached to that Issue. The problem is related to lazily loaded 1:1 entity relations using a composite key, where the Envers proxy for a key does not appear to load the key before persisting the containing entity, resulting in a problem when loading the contained entity back from the audit table. The issue appears to still be present in hibernate-envers 3.5.1-Final. Is there a known-workaround aprat from setting the contained entity to be eager loaded? -- 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

15 years, 6 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5610) Replace new Integer() by Integer.valueOf()

by Ondrej Medek (JIRA)

Replace new Integer() by Integer.valueOf() ------------------------------------------ Key: HHH-5610 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5610 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.5.1 Reporter: Ondrej Medek Priority: Minor Hi, I have seen in org.hibernate.impl.CriteriaImpl and other parts of Hibernate constructions like: this.maxResults = new Integer(maxResults); AFAIK it better to use this.maxResults = Integer.valueOf(maxResults); e.g. see * [http://download.oracle.com/javase/6/docs/api/java/lang/Integer.html#value...] * [http://tech.puredanger.com/2007/02/01/valueof/] Or leave this to the compiler and write: this.maxResults = maxResults; Pleas, grep all your code to find such cunstructs or use FindBugs [http://findbugs.sourceforge.net/] to find it for you. -- 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

15 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2010