October 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (EJB-361) Query#setParameter(int position, Object value) wrong implementation

by Fabrice Daugan (JIRA)

Query#setParameter(int position, Object value) wrong implementation ------------------------------------------------------------------- Key: EJB-361 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-361 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.2.GA Reporter: Fabrice Daugan The Hibernate JPA javax.persistence.Query#setParameter(int position, Object value) implementation does not suit to the JPA specicafication. Indeed, the actual integer passed to the operation is converted to String by Hibernate and then used to find the named parameter. Please have a look to the folowing stack trace : java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalArgumentException: org.hibernate.QueryParameterException: could not locate named parameter [1] at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:185) at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:240) at org.springframework.orm.jpa.JpaTemplate$9.doInJpa(JpaTemplate.java:316) To repoduce this 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

14 years

3
4
0 / 0

[Hibernate-JIRA] Created: (HV-423) Publish an API change report as part of the documentation

by Hardy Ferentschik (JIRA)

Publish an API change report as part of the documentation --------------------------------------------------------- Key: HV-423 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-423 Project: Hibernate Validator Issue Type: Improvement Components: documentation Affects Versions: 4.2.0.Beta1 Reporter: Hardy Ferentschik Fix For: 4.x These reports can be generated via JDiff or clirr. See also HV-417. -- 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

14 years

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-6556) Bind unsaved value for identifier/version property

by Strong Liu (JIRA)

Bind unsaved value for identifier/version property -------------------------------------------------- Key: HHH-6556 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6556 Project: Hibernate Core Issue Type: Task Components: metamodel Reporter: Strong Liu Fix For: 4.0.0.next currently org.hibernate.metamodel.binding.KeyValueBinding#getUnsavedValue is not binded -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-6617) Remove deprecation from Configuration until after new metamodel completely in place

by Steve Ebersole (JIRA)

Remove deprecation from Configuration until after new metamodel completely in place ----------------------------------------------------------------------------------- Key: HHH-6617 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6617 Project: Hibernate Core Issue Type: Task Reporter: Steve Ebersole Assignee: Steve Ebersole Decided to leave in place for {{Ejb3Configuration}} since JPA bootstrapping was always the recommended and supported mechanism for JPA use cases. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-959) Create copyright.txt as mentioned by the license headers

by Hardy Ferentschik (JIRA)

Create copyright.txt as mentioned by the license headers -------------------------------------------------------- Key: HSEARCH-959 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-959 Project: Hibernate Search Issue Type: Bug Affects Versions: 4.0.0.CR1 Reporter: Hardy Ferentschik Priority: Minor Fix For: 4.1 See also https://hibernate.onjira.com/browse/HV-518 We probably can apply the same solution as the one applied on HV. Maybe we can/should create a consistent author tag format at the same time. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[Hibernate-JIRA] Created: (HV-457) Simplify IDE setup of annotation processor by providing a shaded jar

by Kevin Pollet (JIRA)

Simplify IDE setup of annotation processor by providing a shaded jar -------------------------------------------------------------------- Key: HV-457 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-457 Project: Hibernate Validator Issue Type: Improvement Components: annotation-processor Reporter: Kevin Pollet When configuring the annotation processor in IDEs it's classpath has to be specified. In IDEs like Netbeans or IntelliJ the annotation processor can use the project classpath. But it's better if the classpath of project and annotation processor are isolated. In that case people shall setup manually the annotation processor classpath which has to contain at least HV and BV dependency. As Gunnar said it would be usefull to simplify the annotation processor configuration in IDEs by providing a shaded jar. -- 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

14 years

3
16
0 / 0

[Hibernate-JIRA] Created: (HHH-6624) Interaction between the JBossTS and the datasource is broken causing envers test failures

by Gail Badner (JIRA)

Interaction between the JBossTS and the datasource is broken causing envers test failures ----------------------------------------------------------------------------------------- Key: HHH-6624 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6624 Project: Hibernate Core Issue Type: Bug Components: envers Reporter: Gail Badner Fix For: 4.0.0.next This will probably be fixed by switching from XAPool to ironjacama. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
13
0 / 0

[Hibernate-JIRA] Created: (HHH-6552) Map returned by MetadataImpl.getImports() does not include entries for unqualified entity names

by Gail Badner (JIRA)

Map returned by MetadataImpl.getImports() does not include entries for unqualified entity names ----------------------------------------------------------------------------------------------- Key: HHH-6552 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6552 Project: Hibernate Core Issue Type: Bug Reporter: Gail Badner Assignee: Gail Badner -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
8
0 / 0

[Hibernate-JIRA] Created: (HV-479) Implement an eviction strategy for BeanMetaDataCache

by Gunnar Morling (JIRA)

Implement an eviction strategy for BeanMetaDataCache ---------------------------------------------------- Key: HV-479 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-479 Project: Hibernate Validator Issue Type: Improvement Components: engine Reporter: Gunnar Morling Fix For: 4.x In {{BeanMetaDataCache}} we have a map from {{Class}} to {{BeanMetaDataImpl}}. Currently there is no eviction strategy for this cache meaning entries will never be removed once they were added to the cache and the {{ValidatorFactoryImpl}} holding the cache exists. In particular this means that the concerned class objects never can be garbage-collected. This might cause problems in long-running applications (especially as there is typically one long-living {{ValidatorFactory}} instance per application). Maybe {{WeakHashMap}} or similar might be useful here. -- 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

14 years

3
11
0 / 0

[Hibernate-JIRA] Created: (HV-521) TypeDescriptor#getConstraintsForMethod() should return null for unconstrained methods

by Gunnar Morling (JIRA)

TypeDescriptor#getConstraintsForMethod() should return null for unconstrained methods ------------------------------------------------------------------------------------- Key: HV-521 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-521 Project: Hibernate Validator Issue Type: Improvement Components: engine Reporter: Gunnar Morling Fix For: 4.3.0.next The method {{TypeDescriptor#getConstraintsForMethod()}} always returns a {{MethodDescriptor}}, also if the specified method is actually unconstrained. This differs from the behavior of {{BeanDescriptor#getConstraintsForProperty()}} which returns {{null}} if the specified property has no constraints. This change might break clients relying on the current behavior, but nevertheless we should change this IMO better earlier than later. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
9
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 October 2011