December 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Créée: (HHH-2060) To be able to use <generator> with <composite-id>

by Xavier Brénuchon (JIRA)

To be able to use <generator> with <composite-id> ------------------------------------------------- Key: HHH-2060 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2060 Project: Hibernate3 Type: Improvement Versions: 3.2.0.cr4 Environment: Hibernate 3.x Reporter: Xavier Brénuchon Hello, This is the continuation of HB-389 We develop an application which has very strong need for performance with several tens of million recordings. Partitioning is a need. So for that, I use <composite-id>. But my primary key is not a natural key, but a real technical key : - column of partitioning for optimization of the data base - column of technical id So I need to have a generator, for exemple : <composite-id name="id" class="IdPartition"> <key-property name="org" type="string" column="ORG"/> <key-property name="id" type="long" column="ID"/> <generator class="fr.test.xavier.IdPartitionGenerator"> <param name="table">TAB_SEQ</param> <param name="column">LAST</param> </generator> </composite-id> The good news is that Hibernate can use that (HB-389). In fact, it is enough to modify the DTD to authorize <generator> in <composite-id> and it is all. The current code of Hibernate manages it very well. Is it possible that Hibernate is enriched by this functionality? -- 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, 1 month

7
17
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-301) Refactor JMSMasterTest and JMSSlaveTest

by Hardy Ferentschik (JIRA)

Refactor JMSMasterTest and JMSSlaveTest --------------------------------------- Key: HSEARCH-301 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-301 Project: Hibernate Search Issue Type: Improvement Components: build Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik The aim is to get rid of the embedded jboss server for the test. This environment is not supported and creates amongst others problems with CP builds. The embedded server is only used for testing the JMS clustering functionality. This functionality could be replaced with ActiveMQ - http://activemq.apache.org/how-to-unit-test-jms-code.html. -- 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, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-326) Drop support for IndexReader usage to update indexes.

by Sanne Grinovero (JIRA)

Drop support for IndexReader usage to update indexes. ----------------------------------------------------- Key: HSEARCH-326 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-326 Project: Hibernate Search Issue Type: Task Components: engine Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.1.1 in Workspace, remove "getIndexReader()" and all references to an IndexReader. In LuceneWorkDelegate and all implementations, remove "performWork(LuceneWork work, IndexReader reader)" Simplify PerDPQueueProcessor as no "best strategy choice" makes sense anymore. -- 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, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-284) Lucene locks left around in application restart/crash

by sam doyle (JIRA)

Lucene locks left around in application restart/crash ----------------------------------------------------- Key: HSEARCH-284 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-284 Project: Hibernate Search Issue Type: Improvement Affects Versions: 3.0.1.GA Reporter: sam doyle In a case where an application restarts, crashes, gets killed etc. if there is an existing Lucene lock it will not be removed on the application restart. As a result of this the application itself can be severely impacted. After encountering this particular issue and needing to manually remove the lock to resolve the problem I did some searching. It appears this situation is somewhat common and the use of NativeFSLockFactory was the suggested solution. Since I don't see where this particular option is configurable with Hibernate Search I have opened this request. -- 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, 1 month

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3531) Constraint violation Error

by suman (JIRA)

Constraint violation Error -------------------------- Key: HHH-3531 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3531 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Spring/Hibernate/Mysql/ Reporter: suman Hello All, I am Using Spring with Hibernate in my web application.I got Syncronize Exception in some Cases.Atually i am updating to table(sno[PK,Auto increment],acno,pan) In my HBM file i am mentioning sno as increment of generator class.Keen obeservation i am not getting this sort of problem always.In some Time i got this sort of proble, Log as follows: INFO | jvm 2 | 2008/10/15 16:06:25 | 16:06:25,353 WARN JDBCExceptionReporter:71 - SQL Error: 1062, SQLState: 23000 INFO | jvm 2 | 2008/10/15 16:06:25 | 16:06:25,354 ERROR JDBCExceptionReporter:72 - Duplicate key or integrity constraint violation, message from server: "Duplicate entry '984041' for key 1" INFO | jvm 2 | 2008/10/15 16:06:25 | 16:06:25,355 ERROR AbstractFlushingEventListener:277 - Could not synchronize database state with session INFO | jvm 2 | 2008/10/15 16:06:25 | org.hibernate.exception.ConstraintViolationException: could not insert: [com.xxx.model.map] -- 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, 2 months

3
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-36) Validation of method parameters and returned values

by Emmanuel Bernard (JIRA)

Validation of method parameters and returned values --------------------------------------------------- Key: BVAL-36 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-36 Project: Bean Validation Issue Type: New Feature Components: spec-general Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard The goal is to expose the necessary APIs to validate method parameters and returned type. This API can typically be used by an interceptor framework. Validator { List<IC> validateParameters(Method, Object[] parameterValues); List<IC> validateParameter(Method, Object parameterValue, int parameterIndex); List<IC> validateReturnedValue(Method, Object returnedValue); List<IC> validateParameters(Constructor, Object[] parameterValues); List<IC> validateParameter(Constructor, Object parameterValue, int parameterIndex); } Metadata Validator { BeanDescriptor getConstraintsForBean() PropertyDescriptor getConstraintsForProperty(String propertyName); MethodDescriptor getConstraintsForMethod(Method); MethodDescriptor getConstraintsForConstructor(Constructor); String[] getValidatedProperties(); Method[] getValidatedMethods(); Constructor[] getValidatedConstructors(); } ElementDescriptor { ElementType getElementType(); Class getType(); List<ConstraintDescriptor> getConstraintDescriptors(); } PropertyDescriptor extends ElementDescriptor { boolean isCascaded(); String getPropertyPath(); } ParameterDescriptor extends ElementDescriptor { boolean isCascaded(); int getIndex(); } BeanDescriptor extends ElementDescriptor { } MethodDescriptor extends ElementDescriptor { List<ParameterDescriptor> getParameterDescriptors(); //index aligned boolean isCascaded(); } ConstructorDescriptor extends ElementDescriptor { List<ParameterDescriptor> getParameterDescriptors(); //index aligned } How to read parameter annotations Class<?> parameterTypes = method.getParameterTypes() Annotation[][] parameterAnnotations = method.getParameterAnnotations() -- 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, 2 months

2
5
0 / 0

[Hibernate-JIRA] Created: (EJB-254) Allow DataSource overriding through createEntityManager(String, Map override)

by Emmanuel Bernard (JIRA)

Allow DataSource overriding through createEntityManager(String, Map override) ----------------------------------------------------------------------------- Key: EJB-254 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-254 Project: Hibernate Entity Manager Type: Improvement Components: EntityManager Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Fix For: 3.2.1 -- 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, 2 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3204) core-manual-parent pom doesn't build because core-parent doesn't contain the jboss repo

by Geoffrey De Smet (JIRA)

core-manual-parent pom doesn't build because core-parent doesn't contain the jboss repo --------------------------------------------------------------------------------------- Key: HHH-3204 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3204 Project: Hibernate3 Issue Type: Bug Components: build Reporter: Geoffrey De Smet to reproduce: mv ~/.m2/repository ~/.m2/backup_local_repository cd core-parent mvn clean install cd core-manual-parent mvn clean install result ===== Reason: POM 'org.jboss.maven.plugins:maven-jdocbook-plugin' not found in repository: Unable to download the artifact from any repository org.jboss.maven.plugins:maven-jdocbook-plugin:pom:2.1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) for project org.jboss.maven.plugins:maven-jdocbook-plugin solution ======= Just add this in the core-parent pom: <repositories> <repository> <id>jboss</id> <url>http://repository.jboss.com/maven2/</url> </repository> <repository> <id>jboss-snapshot</id> <url>http://snapshots.jboss.org/maven2</url> <snapshots> <enabled>true</enabled> </snapshots> <releases> <enabled>false</enabled> </releases> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>jboss</id> <url>http://repository.jboss.com/maven2/</url> </pluginRepository> </pluginRepositories> -- 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, 2 months

2
5
0 / 0

[Hibernate-JIRA] Created: (EJB-294) Hibernate throwing QueryException when using alias for aggregate functions in named queries

by Saravanabavagugan Vengadasundaram (JIRA)

Hibernate throwing QueryException when using alias for aggregate functions in named queries ------------------------------------------------------------------------------------------- Key: EJB-294 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-294 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.2.0.ga Environment: Hibernate 3.2 GA, Reporter: Saravanabavagugan Vengadasundaram Hibernate throwing QueryException when using alias for aggregate functions in named queries. The following query does not work: select sum(emp.salary) as totalSalary from Employee as emp select sum(emp.salary) totalSalary from Employee as emp but this works: select sum(emp.salary) from Employee as emp -- 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, 2 months

6
9
0 / 0

[Hibernate-JIRA] Created: (BVAL-39) Replace recursive validation algorithm with a ConstraintIterator

by Hardy Ferentschik (JIRA)

Replace recursive validation algorithm with a ConstraintIterator ---------------------------------------------------------------- Key: BVAL-39 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-39 Project: Bean Validation Issue Type: Improvement Components: ri-general Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Priority: Minor Introduce a ConstraintValidator which given a bean finds all constraints to validate and makes them accessible for validation via an iterator. This algorithm might be easier to understand then the current recursive one. -- 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, 2 months

1
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-75) Make sure *Descriptor are immutable in the RI

by Emmanuel Bernard (JIRA)

Make sure *Descriptor are immutable in the RI --------------------------------------------- Key: BVAL-75 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-75 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard Fix For: 1.0 public draft -- 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, 2 months

2
4
0 / 0

[Hibernate-JIRA] Created: (BVAL-46) ElementDescriptor is now split into PropertyDescriptor and BeanDescriptor

by Emmanuel Bernard (JIRA)

ElementDescriptor is now split into PropertyDescriptor and BeanDescriptor ------------------------------------------------------------------------- Key: BVAL-46 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-46 Project: Bean Validation Issue Type: Bug Components: ri-general, spec-general Reporter: Emmanuel Bernard -- 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, 2 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3214) Update unit tests and config files to use non-depracated Oracle dialects

by Gail Badner (JIRA)

Update unit tests and config files to use non-depracated Oracle dialects ------------------------------------------------------------------------ Key: HHH-3214 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3214 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.2.x There are still references to OracleDialect and Oracle9Dialect in hibernate.properties and unit tests. These dialects are depracated so references to them in unit tests and config files (e.g, hibernate.properties) should be changed to refer to non-deprecated dialects. -- 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, 2 months

2
9
0 / 0

[Hibernate-JIRA] Created: (BVAL-50) Be consistent in the spec, use @author or not

by Emmanuel Bernard (JIRA)

Be consistent in the spec, use @author or not --------------------------------------------- Key: BVAL-50 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-50 Project: Bean Validation Issue Type: Improvement Components: spec-general Reporter: Emmanuel Bernard -- 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, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-72) Validating an object multiple times if in a different branch of the graph

by Emmanuel Bernard (JIRA)

Validating an object multiple times if in a different branch of the graph ------------------------------------------------------------------------- Key: BVAL-72 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-72 Project: Bean Validation Issue Type: Improvement Components: spec-general Reporter: Emmanuel Bernard 3-F) 3.5.1 "The InvalidConstraint objects reflect the path to reach the object from the root validated object": What happens if the same invalid object is referenced twice by an object (see the example below). Will there be generated two InvalidConstraint objects one reflecting the path b.ref1.value and one for b.ref2.value? If the referenced invalid object is only validated once, which property path will be used? class A { @NotNull String value = null; } class B { @Valid A ref1; @Valid A ref2; } b = new B(); b.ref1 = new A(); b.ref2 = ref1; Only one ConstraintViolation is created. from 3.1.3 The @Valid annotation is applied recursively. A conforming implementation avoids infinite loops by validating an object the first time it is encountered in the graph, and ignores it if it is encountered through at different path. The path chosen is not defined. Any alternative? Fine with me, I just wanted to have that clarified. I thought about that a bit. We have the current rule wich is simple but a bit indeterministic in the case an object is referenced twice in an object graph Or we could adopt the following rule For a given object graph branch, the same instance cannot be validated several times. This would lead to the validation of the same object several times provided it is in different branches in Sebastian's example b.ref1 and b.ref2 would be validated and generate the same constraintViolations (with different paths) Opinions? - only one validation pass per instance (with some indeterminism) - several validation pass and error reports provided that the object graph branches are different? -- 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, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (BVAL-71) Should we have group aggregation?

by Emmanuel Bernard (JIRA)

Should we have group aggregation? --------------------------------- Key: BVAL-71 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-71 Project: Bean Validation Issue Type: New Feature Components: spec-general Reporter: Emmanuel Bernard Like group seuqnce without the execution constraint -- 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, 2 months

1
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-59) Rethink the group sequence inheritance rules

by Emmanuel Bernard (JIRA)

Rethink the group sequence inheritance rules -------------------------------------------- Key: BVAL-59 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-59 Project: Bean Validation Issue Type: Improvement Components: spec-general Reporter: Emmanuel Bernard Sebastian wrote: 3-F) 3.4 "Two group sequences must not share the same group name in a given object graph". Does this mean If an object of type A references an object of type B and A and B have a group sequences with the same name this would result to an exception? Why would such a limitation be necessary? Or is the term "object graph" misplaced here? Emmanuel replied: "When an object graph is validated (through the use of @Valid), the children elements of the graph inherit the sequence definitions of their parent." Yes this was the intend. Because group sequence definitions are inherited from a parent to a child, the rule makes sense. I think you assumed that a group sequence was not inherited. Children would be validated against the expanded groups of their parents. Let's go back to the drawing board (in a different thread) and evaluate the merit of both rules using common usecases. -- 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, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (BVAL-65) Additional built-in constraints

by Emmanuel Bernard (JIRA)

Additional built-in constraints ------------------------------- Key: BVAL-65 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-65 Project: Bean Validation Issue Type: New Feature Components: spec-general Reporter: Emmanuel Bernard @Like(caseSensitive, escapeChar) or @Contains(startWith, endWith, caseSentitive) @Email / @Url @NoNullElements (for collections or arrays) -- 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, 2 months

1
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-51) UML diagram of the specification classes

by Emmanuel Bernard (JIRA)

UML diagram of the specification classes ---------------------------------------- Key: BVAL-51 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-51 Project: Bean Validation Issue Type: New Feature Components: spec-general Reporter: Emmanuel Bernard -- 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, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (BVAL-54) Specify that constraints on non getter methods are ignored (if BVAL-36 is not accepted)

by Emmanuel Bernard (JIRA)

Specify that constraints on non getter methods are ignored (if BVAL-36 is not accepted) --------------------------------------------------------------------------------------- Key: BVAL-54 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-54 Project: Bean Validation Issue Type: Improvement Components: spec-general Reporter: Emmanuel Bernard -- 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, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (BVAL-32) Describe what is happening when a composition is not consistent

by Emmanuel Bernard (JIRA)

Describe what is happening when a composition is not consistent --------------------------------------------------------------- Key: BVAL-32 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-32 Project: Bean Validation Issue Type: Improvement Components: spec-general Reporter: Emmanuel Bernard -- 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, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3528) FETCH JOIN query doesn't work in a StatelessSession

by Oscar Pearce (JIRA)

FETCH JOIN query doesn't work in a StatelessSession --------------------------------------------------- Key: HHH-3528 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3528 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1, 3.2.6 Environment: Hibernate core 3.3.1 and 3.2.6, HSQLDB 1.8.0 and PostgreSQL 8.1 Reporter: Oscar Pearce Attachments: slsession.zip, StatelessSessionImpl.patch A query with an explicit JOIN FETCH, such as the following: from DomainObject obj join fetch obj.a fails when run in a StatelessSession, giving the following exception: org.hibernate.SessionException: proxies cannot be fetched by a stateless session at org.hibernate.impl.StatelessSessionImpl.immediateLoad(StatelessSessionImpl.java:243) at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:95) at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:140) at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:190) The attached zip file contains a small project (buildable with maven) that demonstrates the problem. Applying the patch to StatelessSessionImpl fixes it. The cause of the problem is with the internalLoad method of StatelessSessionImpl. The method currently first tries to generate a proxy and, only if no proxy is available, then it uses the data that it loaded as part of the query. The patch changes it to use any loaded data from the query in preference to creating a proxy. (I suspect that the check for eager should be omitted, and that an exception should be thrown if getEntity fails and no proxy can be created, but I don't know the code well enough to be sure of that.) -- 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, 2 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3053) Left Outer Join on Unmapped Tables

by Ravi Bala (JIRA)

Left Outer Join on Unmapped Tables ---------------------------------- Key: HHH-3053 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3053 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.1 Environment: Hibernate 3, Oracle 10g Reporter: Ravi Bala I am trying to use left outer join on two unmapped tables. How is this possible in HQL? I tried to see if there is any such problem submitted already from the forums, but I could not find one. Please let me know the link if this is already discussed. Here is the problem: Table A Table B I want to use Select a.field1, b.field2 from A a left outer join B b on a.field1 = b.field1 Thanks, Ravi -- 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, 2 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3522) Null value cannot be cache using hibernate

by Lao Shing Kit (JIRA)

Null value cannot be cache using hibernate -------------------------------------------- Key: HHH-3522 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3522 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Environment: Hibernate 3.3.1, Ehcache 1.5, Java1.5 Reporter: Lao Shing Kit I'm using Hibernate with 2nd level cache using Ehcache. We found that if the result returned using session.get() (searching by primary key) is NULL, the value will not be cached in 1st level and 2nd level cache and SQL will be fired to database. There is no problem if the value retuurned is not null for the same entity. I have debug using the hibernate and ehcache source and I'm sure that the cache is enabled and called properly. Actually the null value is expected to be cached also. I have browser all hibernate and ehcache documentation and forum and no related config is available. So, is it a bug? Thanks all for your help! -- 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, 2 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3455) Component polymorphism (<subclass> within <component>)

by Jasper Blues (JIRA)

Component polymorphism (<subclass> within <component>) ------------------------------------------------------ Key: HHH-3455 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3455 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: Jasper Blues The following feature request occurs on the Hibernate forums from time to time - it would be especially useful in mapping complex legacy schemas: <class name="Critter"> <component name="breathingStrategy" class="BreathingStrategy"> <discriminator column="BREATHING_STRATEGY" type="integer" /> <subclass name="Lungs" discriminator-value="0" > <set name="alveoli"> <key column="CRITTER_ID" /> <one-to-many class="Alveolus" /> </set> </subclass> <subclass name="Gills" discriminator-value="1" > <set name="alveoli"> <key column="CRITTER_ID" /> <one-to-many class="Gill" /> </set> </subclass> </component> </class> Will a patch that implements this feature be accepted? What do you think if there was an option to inherit a discriminator from the owning entity? How about some convention over configuration? By default the discriminator from the owning entity is inherited, unless one is supplied at the component level. Would an equivalent annotation mapping be required? -- 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, 2 months

3
4
0 / 0

[Hibernate-JIRA] Created: (BVAL-83) Take TraversableResolver contract into account

by Emmanuel Bernard (JIRA)

Take TraversableResolver contract into account ---------------------------------------------- Key: BVAL-83 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-83 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard Fix For: 1.0 public draft -- 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, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-38) Add built-in constraints

by Emmanuel Bernard (JIRA)

Add built-in constraints ------------------------ Key: BVAL-38 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-38 Project: Bean Validation Issue Type: New Feature Components: ri-general, spec-general Reporter: Emmanuel Bernard @NotNull @Null @AssertFalse @AssertTrue @Digits(integer, fraction) @Past @Future @Min / @Max @Size (String collection, arrays) Probably need: @Like(caseSensitive, escapeChar) or @Contains(startWith, endWith, caseSentitive) @RegExp seems a complex problem Maybe @Email, @URL as they are standardized in HTML 5 -- 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, 2 months

2
6
0 / 0

[Hibernate-JIRA] Created: (BVAL-80) Implement sequences on group interfaces and group inheritance

by Emmanuel Bernard (JIRA)

Implement sequences on group interfaces and group inheritance ------------------------------------------------------------- Key: BVAL-80 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-80 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard Fix For: 1.0 public draft -- 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, 2 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2920) Polymorphic association with explicit table_per_class strategy: properties of subclass are not retrieved by queries.

by Andrea Silva (JIRA)

Polymorphic association with explicit table_per_class strategy: properties of subclass are not retrieved by queries. -------------------------------------------------------------------------------------------------------------------- Key: HHH-2920 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2920 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: Java 1.5 - Hypersonic DB - Standalone application Reporter: Andrea Silva Priority: Minor Attachments: src.zip Item class has a one-to-many association to Bid. Bid class has a subclass called CashBid (meaningless design I know, but that's not the point). If I create and save an instance of Item with an associated CashBid, when I query for items the properties defined in CashBid are not retrieved. NB Bid is not mapped as abstract. Here is a code snippet: ... // First Session Session session = sessionFactory.openSession(); Transaction transaction = session.beginTransaction(); Bid bid = new CashBid(new BigDecimal(100.0d), "euro"); Item item = new Item("pc"); Serializable bidId = session.save(bid); item.addBid(bid); session.save(item); transaction.commit(); session.close(); // Second Session session = sessionFactory.openSession(); transaction = session.beginTransaction(); //session.load(CashBid.class, bidId); Query query = session.createQuery("from Item"); List<Item> list = query.list(); for (Item item_ : list) { System.out.println(item_); } transaction.commit(); session.close(); ... The bid in the item retrieved by the query is a CashBid (that's correct) but the properties that are defined in CashBid and not in Bid are null. If I uncomment the line //session.load(CashBid.class, bidId); the problem is not there anymore. If Bid is not mapped as abstract the problem doesn't show. My apologies if I'm just missing something very obvious. Please find the source code and the mappings 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

17 years, 2 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3371) Criteria Query Issue with Projection and restriction

by Michael Kuhinica (JIRA)

Criteria Query Issue with Projection and restriction ---------------------------------------------------- Key: HHH-3371 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3371 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.6 Environment: Hibernate version: 3.2.6ga, MySQL 5 Reporter: Michael Kuhinica When I try to add a restriction to a property with a projection, hibernate generate the SQL using the property alias on the where clause instead of the property name. Here is an code example: Criteria c = session.createCriteria(Customer.class).setProjection( Projections.projectionList() .add(Projections.property(Customer.PROP_ID), "id") .add(Projections.property(Customer.PROP_NAME), "name") ) .add(Restrictions.like(Customer.PROP_EMAIL, email)) .add(Restrictions.like(Customer.PROP_NAME, name)); And the generated SQL: select this_.ctm_id as y0_, this_.ctm_name as y1_ from customers this_ where this_.ctm_mail like ? and y1_ like ? Notice that hibernate used the right name for the customer e-mail (that has no projection on it) but it used an alias for the name that have a projection set. See: http://forum.hibernate.org/posting.php?mode=editpost&p=2388756 -- 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, 2 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3546) invalid sql when using projection and restriction

by Martin Trummer (JIRA)

invalid sql when using projection and restriction -------------------------------------------------- Key: HHH-3546 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3546 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: MS SQL Server/HSQLDB Reporter: Martin Trummer from this forum "discussion" (in fact it's a monologue): http://forum.hibernate.org/viewtopic.php?p=2398068#2398068 * the criteria Criteria criteria = getActorDao().createCriteria(); criteria.add(Restrictions.or( Restrictions.ilike("name", "adi"), Restrictions.ilike("description", "adi") )); criteria.setProjection(Projections.projectionList() .add(Projections.groupProperty("name"), "name") .add(Projections.groupProperty("description"), "description") ); criteria.setResultTransformer(new AliasToBeanResultTransformer(ActorTestDTO.class)); List result = criteria.list(); * the generated SQL (show_sql=true): select this_.name as y0_, this_.description as y1_ from Actor this_ left outer join Action this_1_ on this_.id=this_1_.id left outer join Location this_2_ on this_.id=this_2_.id left outer join UserGroup this_3_ on this_.id=this_3_.id left outer join WebUser this_4_ on this_.id=this_4_.id where (lower(y0_) like ? or lower(y1_) like ?) group by this_.name, this_.description * the Problem This generated SQL works on HSQLDB but NOT on MS-SqlServer. The wrong code: where (lower(y0_) like ? or lower(y1_) like ?) The correct code: where (lower(this_.name) like ? or lower(this_.description) like ?) I verified this by issuing the sql directly in SQL-server. -- 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, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (BVAL-15) Object graph traversed too many times

by Emmanuel Bernard (JIRA)

Object graph traversed too many times ------------------------------------- Key: BVAL-15 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-15 Project: Bean Validation Issue Type: Bug Components: ri-general Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik You seem to traverse the object graph once per group. I made the spec so that multiple traversals were not necessary unless you physically force group sequence. Actually the prototype I gave you was doing some clever things to minimize the number of AFAIR I made the spec so that this multiple traversals are not needed unless you physically sequenciate them. In a prototype I had, I actually worked on an algorithm to validate as much groups as possible in a same traversal. Unfortunately I lost it, probably in my hardware crash :( The idea was to compute a tree of groups to validate with their respective sequential constraints and run as less cycle as possible at a given time e=|- a - b (b seq after a) f=|- c - d (d seq after c) validating e, f would run a and c in // in the same cycle and b and d in the second cycle. -- 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, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2792) Session.delete is validate all fields are null

by Daniel Passos (JIRA)

Session.delete is validate all fields are null ---------------------------------------------- Key: HHH-2792 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2792 Project: Hibernate3 Issue Type: Bug Components: core Reporter: Daniel Passos session.delete operation would not have to validate if the fields are null The problem in DefaultDeleteEventListener.deleteEntity -> Nullability.checkNullability -- 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, 2 months

6
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2801) wrong insert/delete order when updating record-set

by Christoph Mayerhofer (JIRA)

wrong insert/delete order when updating record-set -------------------------------------------------- Key: HHH-2801 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2801 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Environment: hibernate-3.2.4.sp1, hibernate-annotations-3.3.0.GA, hibernate-entitymanager-3.3.1.GA, Oracle 10g Express Edition Reporter: Christoph Mayerhofer Attachments: model.zip Overview: I have a record with a OneToMany association. From this associated record-set a record is removed and added again, both records identified with the same key. When doing a merge, I get a Unique constraint violation, because Hibernate first tries to insert the new record. Hibernate should first delete the old record, and after this insert the new record, avoiding the unique constraint violation. Detailed description: I have the following entities: Patient, SocialInsurance, PatientSocialInsurance. A patient could have several social insurances assigned to it. A social insurance could be assigned several times to a patient, we have a m:n relation between Patient and SocialInsurance. The relation-table has the name PatientSocialInsurance, with a unique constraint over patient_id and social_insurance_id. Each POJO inherits from a Base-POJO, which holds the id and the insert- and update-timestamps and userstamps. Base ---> PatientEntity ---> Patient Base ---> SocialInsuranceEntity ---> SocialInsurance Base ---> PatientSocialInsuranceEntity ---> PatientSocialInsurance Note: All *Entity model objects are generated with Hibernate-Tools from the db-schema, assuming that there are no wrong annotations, no wrong fields or wrong getter-/setter-methods in these model-classes. (I have enclosed all model-classes within an zipped attachment.) Now I try to delete an existing social insurance from a patient and add the same social insurance to the patient again: public void deleteSocialInsurance(Patient p, PatientSocialInsurance s) { if (p == null || s == null) { throw new IllegalArgumentException(); } s.setSocialInsurance(null); s.setPatient(null); p.getPatientSocialInsurances().remove(s); } public void addPatientSocialInsurance(Patient p, PatientSocialInsurance s) throws DuplicatePatientSocInsException { if (p == null || s == null) { throw new IllegalArgumentException(); } s.setPatient(p); p.getPatientSocialInsurances().add(s); } After doing a merge on the patient object, I get the following error: DEBUG - persisting patient... DEBUG - transaction org.hibernate.ejb.TransactionImpl@44ac6a started DEBUG - update timestamp and userstamp for base record set DEBUG - update timestamp and userstamp for base record set DEBUG - update timestamp and userstamp for base record set DEBUG - update timestamp and userstamp for base record set DEBUG - update timestamp and userstamp for base record set DEBUG - select rawtohex(sys_guid()) from dual DEBUG - insert timestamp and userstamp for base record set DEBUG - insert into dseas.PATIENT_SOCIAL_INSURANCE (TIME_CRE, TIME_UPD, USER_CRE, USER_UPD, CODE_MEMBERSHIP_NO, CODE_TYPE_DEFAULT, PATIENT_ID, SOC_INS_ID, ID) values (?, ?, ?, ?, ?, ?, ?, ?, ?) ERROR - ORA-00001: Unique Constraint (DSEAS.PATIENT_SOCIAL_INSURANCE_UK) verletzt ERROR - ORA-00001: Unique Constraint (DSEAS.PATIENT_SOCIAL_INSURANCE_UK) verletzt ERROR - Could not synchronize database state with session org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:71) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:253) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:237) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:141) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at org.hibernate.ejb.TransactionImpl.commit(TransactionImpl.java:54) at org.dseas.base.hibernate.EntityManagerFacade.commit(EntityManagerFacade.java:78) at org.dseas.business.service.maindata.PatientEditorService.save(PatientEditorService.java:112) at org.dseas.ui.rcp.editor.patient.PatientEditorPart.doSave(PatientEditorPart.java:1298) at org.eclipse.ui.internal.SaveableHelper$1.run(SaveableHelper.java:143) at org.eclipse.ui.internal.SaveableHelper$4.run(SaveableHelper.java:266) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313) at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:758) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:755) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2451) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:274) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:253) at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:148) at org.eclipse.ui.internal.EditorManager.savePart(EditorManager.java:1345) at org.eclipse.ui.internal.WorkbenchPage.savePart(WorkbenchPage.java:3184) at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3197) at org.eclipse.ui.internal.SaveAction.run(SaveAction.java:73) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:443) 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.dseas.ui.rcp.Application.start(Application.java:22) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153) 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(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:504) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443) at org.eclipse.equinox.launcher.Main.run(Main.java:1169) at org.eclipse.equinox.launcher.Main.main(Main.java:1144) Caused by: java.sql.BatchUpdateException: ORA-00001: Unique Constraint (DSEAS.PATIENT_SOCIAL_INSURANCE_UK) verletzt at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:343) at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10657) at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:246) ... 55 more ERROR - Error while commiting the transaction -- 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, 2 months

10
21
0 / 0

[Hibernate-JIRA] Created: (BVAL-55) Exception policy

by Emmanuel Bernard (JIRA)

Exception policy ---------------- Key: BVAL-55 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-55 Project: Bean Validation Issue Type: New Feature Components: spec-general Reporter: Emmanuel Bernard -- 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, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (BVAL-52) Define the exception hierarchy and rules

by Emmanuel Bernard (JIRA)

Define the exception hierarchy and rules ---------------------------------------- Key: BVAL-52 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-52 Project: Bean Validation Issue Type: New Feature Components: spec-general Reporter: Emmanuel Bernard -- 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, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (BVAL-56) Raise exception if two GroupSequences share the same name

by Emmanuel Bernard (JIRA)

Raise exception if two GroupSequences share the same name --------------------------------------------------------- Key: BVAL-56 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-56 Project: Bean Validation Issue Type: New Feature Components: ri-general, spec-general Reporter: Emmanuel Bernard -- 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, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-234) add to maven repository (not jboss).

by chun ping wang (JIRA)

add to maven repository (not jboss). ------------------------------------- Key: HSEARCH-234 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-234 Project: Hibernate Search Issue Type: Improvement Reporter: chun ping wang is it possible to copy the jboss repository and move the dependecy toward main maven 2 repository. I kinda don't want to point to two different repository. -- 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, 2 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HBX-893) "Can't create session factory" if any @NamedQuery annotations on entities have errors in them

by Joseph Marques (JIRA)

"Can't create session factory" if any @NamedQuery annotations on entities have errors in them --------------------------------------------------------------------------------------------- Key: HBX-893 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-893 Project: Hibernate Tools Type: Bug Versions: 3.2beta8 Reporter: Joseph Marques This seems to be a pretty big restriction - especially if you want to be able to cater to those that try to adopt Hibernate Tools part of the way through development, where some annotations may already have errors in them. Instead, it should be much more user-friendly to expand the session factory anyway, but just not load those entities - perhaps even marking them with a little red 'X' to indicate that the user needs to fix something in them. -- 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, 2 months

2
5
0 / 0

[Hibernate-JIRA] Created: (BVAL-58) Group sequence sequences can contain group sequence names

by Emmanuel Bernard (JIRA)

Group sequence sequences can contain group sequence names --------------------------------------------------------- Key: BVAL-58 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-58 Project: Bean Validation Issue Type: Bug Components: ri-general Reporter: Emmanuel Bernard The algorithm only expand group sequences to one level. -- 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, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-57) Group sequence expansion and validation execution should be decoupled

by Emmanuel Bernard (JIRA)

Group sequence expansion and validation execution should be decoupled --------------------------------------------------------------------- Key: BVAL-57 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-57 Project: Bean Validation Issue Type: Bug Components: ri-general Reporter: Emmanuel Bernard Priority: Critical Today if I try to validate validate(object, "a", "b") where Object has a group sequence "a" = "c", "d" The algorithm only validates c and stops if c has a violation. According to the rules, it should validate (in no respective order: - c - b -- 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, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HBX-1047) Constructor uses the non generated properties even though Meta tag attribute="gen-property" value is set to "false".

by Sukirtha Joseph (JIRA)

Constructor uses the non generated properties even though Meta tag attribute="gen-property" value is set to "false". --------------------------------------------------------------------------------------------------------------------- Key: HBX-1047 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1047 Project: Hibernate Tools Issue Type: Bug Components: hbm2java Environment: Hibernate 3.0 Reporter: Sukirtha Joseph Constructor uses the non generated properties even though Meta tag attribute="gen-property" value is set to "false". Thus class compilation fails. -- 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, 2 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HHH-3509) Sybase - Insert into temp table is in inverted order

by Juraci Paixao Krohling (JIRA)

Sybase - Insert into temp table is in inverted order ----------------------------------------------------- Key: HHH-3509 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3509 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 As per Sybase documentation [1], this is the supported way to create temp tables based on the results of a select: select type, "Total_amount" = sum(advance) into #whatspent from titles group by type But Hibernate [2] is generating: insert into #Vehicle select vehicle0_.id as id from ( select id, vin, owner, 3 as clazz_ from SUV union select id, vin, owner, 4 as clazz_ from Pickup union select id, vin, owner, 1 as clazz_ from Car union select id, vin, owner, 2 as clazz_ from Truck ) vehicle0_ [1] http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15... [2] BulkManipulationTest#testTempTableGenerationIsolation -- 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, 2 months

2
8
0 / 0

[Hibernate-JIRA] Created: (BVAL-14) ValidatorImpl.expandGroupName() does not seem to expand recursively, this goes against the spec

by Emmanuel Bernard (JIRA)

ValidatorImpl.expandGroupName() does not seem to expand recursively, this goes against the spec ----------------------------------------------------------------------------------------------- Key: BVAL-14 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-14 Project: Bean Validation Issue Type: Bug Components: ri-general Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik -- 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, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (ANN-597) @Index doesn't create multi-column indexes

by Christian Bauer (JIRA)

@Index doesn't create multi-column indexes ------------------------------------------ Key: ANN-597 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-597 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.0.ga Reporter: Christian Bauer Priority: Minor @org.hibernate.annotations.Index(name = "IDX_COMPONENT_PROPERTY_NAME", columnNames = {"COMPONENT_NAME", "PROPERTY_NAME"}) create index IDX_COMPONENT_PROPERTY_NAME on PREFERENCE (PROPERTY_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

17 years, 2 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HBX-1053) [PATCH] In Hbm2DDLExporterTask report errors if schemaUpdate = true

by Johannes Rudolph (JIRA)

[PATCH] In Hbm2DDLExporterTask report errors if schemaUpdate = true ------------------------------------------------------------------- Key: HBX-1053 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1053 Project: Hibernate Tools Issue Type: Patch Components: ant Affects Versions: 3.2.1 Reporter: Johannes Rudolph Attachments: better_exception_reporting.patch The current hbm2ddl doesn't report any errors if schemaUpdate=true. This may be that the SQL Driver cannot be found or any errors when exporting the generated script to DB. I attached a patch to fix it by reusing the error reporting code use if schemaUpdate=false. -- 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, 3 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HBX-757) Add output file name, delimiter, halt on error, and format options to SchemaUpdate/<hbm2ddl>

by Dan Ports (JIRA)

Add output file name, delimiter, halt on error, and format options to SchemaUpdate/<hbm2ddl> -------------------------------------------------------------------------------------------- Key: HBX-757 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-757 Project: Hibernate Tools Type: Improvement Components: ant Versions: 3.2beta7 Reporter: Dan Ports Priority: Minor The file name, delimiter, halt on error, and format options are provided by SchemaExport/<hbm2ddl> already, so it makes sense to add their functionality to SchemaUpdate as well. I'll submit a patch shortly. (Is this the right place to post this, since SchemaUpdate is in the Hibernate core SVN?) -- 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, 3 months

3
17
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-325) org.hibernate.search.query.FullTextQueryImpl.iterate() ommit the last result.

by Ivan Latysh (JIRA)

org.hibernate.search.query.FullTextQueryImpl.iterate() ommit the last result. ----------------------------------------------------------------------------- Key: HSEARCH-325 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-325 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.1.0.GA Reporter: Ivan Latysh Priority: Blocker line 152 : int size = max - first + 1 < 0 ? 0 : max - first + 1; will produce wrong size, because max( first, queryHits.totalHits ) returns not the size of the selection but the max element index so for 3 hits max=2. And since first element is 1 and not 0 we have to account for it. Correct size calculation: line 152 : int size = max - first + 2 < 0 ? 0 : max - first + 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, 3 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HBX-1101) Opening database part of a hibernate configuration results in java.lang.StringIndexOutOfBoundsException: String index out of range: 0 while reading Progress OpenEdge

by Thijs Thiessens (JIRA)

Opening database part of a hibernate configuration results in java.lang.StringIndexOutOfBoundsException: String index out of range: 0 while reading Progress OpenEdge --------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HBX-1101 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1101 Project: Hibernate Tools Issue Type: Bug Components: reverse-engineer Affects Versions: 3.2.0.GA Environment: Ubuntu/Eclipse Progress Open Edge Reporter: Thijs Thiessens Attachments: hibernate.png I am trying to reverse engineer a progress openedge database 10.1 using com.ddtek.jdbc.openedge.OpenEdgeDriver. Some databases can be read. Others can't resulting in a java.lang.StringIndexOutOfBoundsException: String index out of range: 0 in plugin org.hibernate.eclipse.console. No stacktrace could be found. -- 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, 3 months

4
6
0 / 0

[Hibernate-JIRA] Created: (EJB-362) JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp

by josef (JIRA)

JPA Max/Min aggregate functions do not return same state-field type when argument is a java.sql.Timestamp --------------------------------------------------------------------------------------------------------- Key: EJB-362 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-362 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.2.GA Environment: JDK 1.6, Postgres 8.2, JDBC 4 Reporter: josef According the JPQL specification, MAX and MIN aggregate functions should return the type of the state-field to which they are applied. However, if one tries to query MAX or MIN on a java.sql.Timestamp entity field and tries to populate a class which expects a java.sql.Timestamp in the constructor with the result of MAX or MIN, Hibernate fails with javax.persistence.PersistenceException. The result of MAX or MIN in this case are being java.util.Date instead. The error result in type mismatch should ideally also be more helpful, because it is very difficult to understand what and where the problem is, unless you know about it beforehand. Here is an example Entity, with the aggregate class and query, together with the exception that occurs: ... import java.sql.Timestamp; @Entity @Table(name="pending_events") public class PendingEvent implements Serializable { ... @Column(name="event_time", updatable=false, nullable=false) private Timestamp eventTime; ... } import java.sql.Timestamp; public class EventEntry { private String sender; private Timestamp lastEventTime; public EventEntry(String sender, Timestamp lastEventTime) { this.sender= sender; this.lastEventTime = lastEventTime; } ... } SELECT NEW mt.com.jbx.EventEntry(p.sender, MAX(p.eventTime)) FROM PendingEvent p WHERE p.recipient.id=? GROUP BY p.sender ORDER BY MAX(p.eventTime) DESC java.lang.ExceptionInInitializerError Caused by: javax.persistence.PersistenceException: [PersistenceUnit: EventsPU] Unable to build EntityManagerFactory at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:34) at mt.com.jbx.EventHandler.<clinit>(EventHandler.java:33) Caused by: org.hibernate.HibernateException: Errors in named queries: getEventSummary at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:365) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1300) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669) -- 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, 3 months

5
11
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 December 2008