[Hibernate-JIRA] Created: (HSEARCH-646) Unable to run tests against non in memory db
by Hardy Ferentschik (JIRA)
Unable to run tests against non in memory db
--------------------------------------------
Key: HSEARCH-646
URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-646
Project: Hibernate Search
Issue Type: Bug
Components: build
Affects Versions: 3.3.0.CR2
Environment: Apache Maven 3.0.1 (r1038046; 2010-11-23 11:58:32+0100)
Java version: 1.6.0_22
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x" version: "10.6.5" arch: "x86_64" Family: "mac"
Reporter: Hardy Ferentschik
Fix For: 3.3.0.Final
Trying to run the build against a non in memory db fails. I tried against postgres and got 5 errors. One is in the infinispan module which seems to have a problem with finding the right drivers when running with the postgres profile:
* org.hibernate.search.infinispan.TwoNodesTest.testSomething
{noformat}
org.hibernate.HibernateException: JDBC Driver class not found: org.h2.Driver
at org.hibernate.connection.DriverManagerConnectionProvider.configure(DriverManagerConnectionProvider.java:89)
at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:143)
at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:84)
at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:459)
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:91)
at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2833)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2829)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1840)
at org.hibernate.search.test.util.FullTextSessionBuilder.build(FullTextSessionBuilder.java:150)
at org.hibernate.search.infinispan.TwoNodesTest.setUp(TwoNodesTest.java:91)
at junit.framework.TestCase.runBare(TestCase.java:125)
...
{noformat}
The other for errors are:
* org.hibernate.search.test.batchindexing.DoNotCloseOnLockTimeoutTest.testTimeoutException
* org.hibernate.search.test.bridge.BridgeTest.testIncorrectSetBridge
* org.hibernate.search.test.bridge.BridgeTest.testIncorrectGetBridge
* org.hibernate.search.test.bridge.BridgeTest.testIncorrectObjectToStringBridge
--
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, 5 months
[Hibernate-JIRA] Created: (HCANN-33) incompatable between hibernate core and annotations
by Ahmed Ali Elsayed Ali Soliman (JIRA)
incompatable between hibernate core and annotations
---------------------------------------------------
Key: HCANN-33
URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-33
Project: Hibernate Commons Annotations
Issue Type: Bug
Environment: Hibernate 3.6.0 Final release & hibernate-annotations-3.4.0.GA & hibernate-commons-annotations-3.1.0.GA
Reporter: Ahmed Ali Elsayed Ali Soliman
when i add annotations to my project i add the hibernate-annotations-3.4.0.GA & hibernate-commons-annotations-3.1.0.GA jars and start the project it report to me the following error
Caused by: java.lang.ClassCastException: org.hibernate.annotations.common.reflection.java.JavaReflectionManager cannot be cast to org.hibernate.annotations.common.reflection.MetadataProviderInjector
i saw that org.hibernate.annotations.common.reflection.java.JavaReflectionManager in hibernate core 3.6.jar and in hibernate-annotations-3.4.0.GA jar
please could you solve this issue as soon as possible because of my delivery deadlines
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
13 years, 5 months
[Hibernate-JIRA] Created: (HHH-5786) TypeSafeActivator.applyDDL doesn't process comprising constraints when @NotNull goes first
by Enrico Pizzorno (JIRA)
TypeSafeActivator.applyDDL doesn't process comprising constraints when @NotNull goes first
------------------------------------------------------------------------------------------
Key: HHH-5786
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5786
Project: Hibernate Core
Issue Type: Bug
Affects Versions: 3.6.0
Reporter: Enrico Pizzorno
Priority: Minor
We have a custom constraint defined as:
{quote}
@Size(max=60)
...
public @interface Name {
String message() default "";
Class<?>[] groups() default {};
Class<? extends Payload>[] payload() default {};
}
{quote}
Then we can annotate some entities like this:
{quote}
public class MyEntity {
...
@NotNull
@Name
private String name;
...
}
{quote}
If @NotNull goes before @Name then when contraints are applied to column definitions by calling TypeSafeActivator.applyDDL the constraint @Size(max=60) is ignored.
I think the problem is at line 200 from *org.hibernate.cfg.beanvalidation.TypeSafeActivator*, method *private static boolean applyConstraints(Set<ConstraintDescriptor<?>> constraintDescriptors, Property property, PropertyDescriptor propertyDesc, Set<Class<?>> groups, boolean canApplyNotNull)*:
{quote}
// pass an empty set as composing constraints inherit the main constraint and thus are matching already
hasNotNull = hasNotNull || applyConstraints(
descriptor.getComposingConstraints(),
property, propertyDesc, null,
canApplyNotNull );
{quote}
If @NotNull is processed first then hasNotNull is set to true so the call to applyConstraints at line 200 is never made.
Changing the order of the "or" operands will solve the problem:
{quote}
// pass an empty set as composing constraints inherit the main constraint and thus are matching already
hasNotNull = applyConstraints(
descriptor.getComposingConstraints(),
property, propertyDesc, null,
canApplyNotNull ) || hasNotNull;
{quote}
--
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, 5 months
[Hibernate-JIRA] Created: (HCANN-32) Discriminator for Single table per class hierarchy (2.2.4.2) should be optional
by Tobias Marx (JIRA)
Discriminator for Single table per class hierarchy (2.2.4.2) should be optional
--------------------------------------------------------------------------------
Key: HCANN-32
URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-32
Project: Hibernate Commons Annotations
Issue Type: Improvement
Affects Versions: 3.2.0
Reporter: Tobias Marx
If a Single table per class inheritance is used for cases as shown in the documentation, this makes perfect sense to need a Discriminator column.
However, in many scenarios, no Discriminator is needed as there will only different represenations of the same object.
Example:
One library defines a User entity.
In order to separate different Security implementations from each other, another library can extend this User Object, e.g.
as an ExtendedUser.
Some classes will query the table with less columns and call it "User" - some will query the same table in parallel as "ExtendendUser" - so no discriminator is needed - and adding an additional column makes now sense.
The colunns needed are already defined in the entities themselves.
--
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, 5 months
[Hibernate-JIRA] Created: (HHH-5787) Annotated Hibernate Entity can not have a Bean property as ID (literal id)
by yaodonghu (JIRA)
Annotated Hibernate Entity can not have a Bean property as ID (literal id)
--------------------------------------------------------------------------
Key: HHH-5787
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5787
Project: Hibernate Core
Issue Type: Bug
Components: annotations
Affects Versions: 3.5.6
Environment: Hibernate 3.5.3 final, with hsql as database
Reporter: yaodonghu
Priority: Minor
Attachments: FirstExample.java, SimpleAnnotation.java
the annotated entity has property name as "id", but it is not a identity property.
When using hibernate to create a simple query again the entity as
"Select MyEntity_Alias from MyEntity MyEntity_Alias"
Then the hibernate give out the following exception:
java.lang.NullPointerException
null
at org.hibernate.util.StringHelper.root(StringHelper.java:260)
at org.hibernate.persister.entity.AbstractEntityPersister.getSubclassPropertyTableNumber(AbstractEntityPersister.java:1467)
at org.hibernate.persister.entity.BasicEntityPropertyMapping.toColumns(BasicEntityPropertyMapping.java:62)
at org.hibernate.persister.entity.AbstractEntityPersister.toColumns(AbstractEntityPersister.java:1443)
at org.hibernate.hql.ast.tree.FromElement.getIdentityColumn(FromElement.java:345)
at org.hibernate.hql.ast.tree.IdentNode.resolveAsAlias(IdentNode.java:154)
at org.hibernate.hql.ast.tree.IdentNode.resolve(IdentNode.java:100)
at org.hibernate.hql.ast.tree.FromReferenceNode.resolve(FromReferenceNode.java:117)
at org.hibernate.hql.ast.tree.FromReferenceNode.resolve(FromReferenceNode.java:113)
at org.hibernate.hql.ast.HqlSqlWalker.resolve(HqlSqlWalker.java:867)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.propertyRef(HqlSqlBaseWalker.java:1199)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectExpr(HqlSqlBaseWalker.java:2047)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectExprList(HqlSqlBaseWalker.java:1983)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectClause(HqlSqlBaseWalker.java:1515)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:586)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:294)
at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:237)
at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:254)
at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:185)
at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:136)
at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:101)
at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80)
at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:98)
at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156)
at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135)
at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1760)
at roseindia.tutorial.hibernate.FirstExample.main(FirstExample.java:47)
Step to reproduce
Using the attach Annotated entity bean file SimpleAnnotation.java
and run the FirstExample.java (both file are attached)
--
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, 5 months
[Hibernate-JIRA] Created: (HHH-3007) Unchanged persistent set gets marked dirty on session.merge()
by Lars Koedderitzsch (JIRA)
Unchanged persistent set gets marked dirty on session.merge()
-------------------------------------------------------------
Key: HHH-3007
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3007
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.2.5
Reporter: Lars Koedderitzsch
Persistent sets are marked dirty on session.merge() even if there have been no changes to the collection.
This is especially painful when the collection is immutable and results in an "changed an immutable collection instance" exception on flush.
I tracked the behaviour down a bit and believe the problem to be in CollectionType.replace().
Here the passed in orginal PersistentSet is replaced by a plain HashSet in this line:
Object result = target == null || target == original ? instantiateResult( original ) : target;
The "result" object (HashSet) is then passed to the CollectionType.replaceElements() method (instead of the original PersistentSet).
In CollectionType.replaceElements() the code to clear the dirty state of the collection does not execute anymore, because the passed-in "original" collection is the described HashSet and *not* the original PersistentSet.
This way the PersistentSet remains marked dirty.
A workaround is to manually clear the dirty state of an immutable collection after merge but before flush.
--
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, 5 months
[Hibernate-JIRA] Created: (HV-362) Including Annotation Processor in Eclipse results in java.lang.OutOfMemoryError: Java heap space
by Marcel Tietze (JIRA)
Including Annotation Processor in Eclipse results in java.lang.OutOfMemoryError: Java heap space
------------------------------------------------------------------------------------------------
Key: HV-362
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-362
Project: Hibernate Validator
Issue Type: Bug
Components: annotation-processor
Affects Versions: 4.1.0.Final
Environment: eclipse.buildId=I20100608-0911
java.version=1.6.0_15
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
Reporter: Marcel Tietze
Assignee: Hardy Ferentschik
Priority: Minor
I added the annotation processor like in http://docs.jboss.org/hibernate/stable/validator/reference/en-US/html/ch0... chapter 8.4.2.1. Eclipse described. After a while the build process stops and the following exception occures:
{code}
An internal error occurred during: "Building Workspace".
java.lang.OutOfMemoryError: Java heap space
at org.eclipse.jdt.core.dom.ASTNode$NodeList.<init>(ASTNode.java:1112)
at org.eclipse.jdt.core.dom.Block.<init>(Block.java:70)
at org.eclipse.jdt.core.dom.ASTConverter.convert(ASTConverter.java:511)
at org.eclipse.jdt.core.dom.ASTConverter.buildBodyDeclarations(ASTConverter.java:180)
at org.eclipse.jdt.core.dom.ASTConverter.convert(ASTConverter.java:2709)
at org.eclipse.jdt.core.dom.ASTConverter.convert(ASTConverter.java:1266)
at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:876)
at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:577)
at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:888)
at org.eclipse.jdt.apt.core.internal.env.BaseProcessorEnv.createASTs(BaseProcessorEnv.java:859)
at org.eclipse.jdt.apt.core.internal.env.BuildEnv.createASTs(BuildEnv.java:356)
at org.eclipse.jdt.apt.core.internal.env.AbstractCompilationEnv.newBuildEnv(AbstractCompilationEnv.java:111)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.build(APTDispatchRunnable.java:271)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.run(APTDispatchRunnable.java:217)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.runAPTDuringBuild(APTDispatchRunnable.java:142)
at org.eclipse.jdt.apt.core.internal.AptCompilationParticipant.processAnnotations(AptCompilationParticipant.java:193)
at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.processAnnotations(AbstractImageBuilder.java:627)
at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:338)
at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:60)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:254)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:178)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:172)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:203)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:311)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)
at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:344)
{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
13 years, 5 months