August 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-684) Query with an IN Clause object that holds an Enum is failing with ORA-01722: invalid number (Criteria) OR ORA-17041: Missing IN or OUT parameter at index (HQL)

by Li Ho (JIRA)

Query with an IN Clause object that holds an Enum is failing with ORA-01722: invalid number (Criteria) OR ORA-17041: Missing IN or OUT parameter at index (HQL) --------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: ANN-684 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-684 Project: Hibernate Annotations Issue Type: Bug Components: search Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0 (cr4) Oracle Annotations Reporter: Li Ho I am trying to do a query with an IN clause. The object I am passing into the IN clause contains an Enum. I'm not 100% sure, but I think the Enum is causing the problem based on the resulting error message. When I use the Criteria API, I get the following error: ORA-01722: invalid number When I use the equivalent HQL, I get: ORA-17041: Missing IN or OUT parameter at index Here is some code (using criteria) that produces the error List<AccountKey> accountKeys; // AccountKey contains some Strings and an Enum ... List results = session.createCriteria(MyObject.class). add(Expression.in("key.account.key", accountKeys)). list(); The debug SQL looks right... and when I manually try it by replacing the ? params with valid values, it works! So, it seems like there's a problem with the passing of the query parameter values. I am currently working around this issue by bypassing the object comparison. I extract the variables I want to compare and force it to do a direct String comparison on those elements. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-177) Payload of composed constraints are ignored, the main constraint payload is propagated

by Emmanuel Bernard (JIRA)

Payload of composed constraints are ignored, the main constraint payload is propagated -------------------------------------------------------------------------------------- Key: BVAL-177 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-177 Project: Bean Validation Issue Type: Bug Components: spec-general Affects Versions: 1.0 proposed final draft 2 Reporter: Emmanuel Bernard Priority: Minor Fix For: 1.0 final -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-214) Constraints from interfaces and superclasses are not inherited when XML descriptors are used

by Igor Drobiazko (JIRA)

Constraints from interfaces and superclasses are not inherited when XML descriptors are used -------------------------------------------------------------------------------------------- Key: HV-214 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-214 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.0.0.Beta3 Reporter: Igor Drobiazko Attachments: test.zip When using XML descriptors the contraints from interfaces and superclasses are not inherited. Let's have a look at following example. public interface Person { String getFirstName(); String getMiddleName(); String getLastName(); } public class Customer implements Person { private String firstName; private String middleName; private String lastName; private String customerId; private String password; ... } <constraint-mappings xmlns="http://jboss.org/xml/ns/javax/validation/mapping" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation= "http://jboss.org/xml/ns/javax/validation/mapping validation-mapping-1.0.xsd"> <default-package>com.acme</default-package> <bean class="Person" ignore-annotations="false"> <getter name="firstName"> <constraint annotation="javax.validation.constraints.NotNull"/> </getter> </bean> <bean class="Customer" ignore-annotations="false"> <field name="lastName"> <constraint annotation="javax.validation.constraints.NotNull"/> </field> </bean> </constraint-mappings> The constraint @NotNull for the property firstName is not considered. A Customer without a firstName would pass the validation successfuly. Accoring to annotations it should be possible to define contraints for superclasses and interfaces which will be inherited. A testcase is 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

15 years, 4 months

2
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-74) Make sure Validator<T> is thread-safe in the RI

by Emmanuel Bernard (JIRA)

Make sure Validator<T> is thread-safe in the RI ----------------------------------------------- Key: BVAL-74 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-74 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

15 years, 4 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HV-185) Change package name in codebase from org.hibernate.validation to org.hibernate.validator

by Hardy Ferentschik (JIRA)

Change package name in codebase from org.hibernate.validation to org.hibernate.validator ---------------------------------------------------------------------------------------- Key: HV-185 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-185 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 4.0.0.Beta2 Reporter: Hardy Ferentschik Fix For: 4.0.0.GA Need to think about this 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

15 years, 4 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HV-183) Composite constraints have to honour the payload parameter as well

by Hardy Ferentschik (JIRA)

Composite constraints have to honour the payload parameter as well ------------------------------------------------------------------ Key: HV-183 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-183 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.0.0.Beta1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik i tested the current payload impl. it works for simple constraints - e.g.: @NotNull(payload = Severity.Warn.class) but it doesn't work for composite constraints - e.g.: @NickName(payload = Severity.Warn.class) with the following workaround it works: @NotNull @Size //... public @interface NickName { @OverridesAttribute.List({ @OverridesAttribute(constraint = NotNull.class, name = "payload"), @OverridesAttribute(constraint = Size.class, name = "payload") }) Class<? extends ConstraintPayload>[] payload() default {}; //... } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HV-189) ResourceBundleMessageInterpolator should cache the interpolation results for step 1-3 of the interpolation algorithm

by Hardy Ferentschik (JIRA)

ResourceBundleMessageInterpolator should cache the interpolation results for step 1-3 of the interpolation algorithm -------------------------------------------------------------------------------------------------------------------- Key: HV-189 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-189 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 4.0.0.Beta2 Reporter: Hardy Ferentschik Fix For: 4.0.0.GA Some parts of the interpolation process can be cached by the MessageInterpolator. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HV-208) Wrong Path in ConstrinViolations

by Alexey Romanchuk (JIRA)

Wrong Path in ConstrinViolations -------------------------------- Key: HV-208 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-208 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.0.0.Beta3 Environment: beta 3 snapshot from aug 11 Reporter: Alexey Romanchuk Priority: Critical In Path we always have leading dot for every validate field. class A { @NotNull String b; } causes ".b" in Path when @NotNull 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

15 years, 4 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HV-211) Class name refactoring

by Hardy Ferentschik (JIRA)

Class name refactoring ---------------------- Key: HV-211 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-211 Project: Hibernate Validator Issue Type: Task Components: engine Affects Versions: 4.0.0.Beta3 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.0.0.CR1 Before releasing CR1 we should rename: - HibernateValidatorProvider into HibernateValidator - HibernateValidatorConfiguration into ValidatorConfiguration -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-212) Group sequence resolution has to take sequence order of composing groups (via inheritance or other group sequence) into account

by Hardy Ferentschik (JIRA)

Group sequence resolution has to take sequence order of composing groups (via inheritance or other group sequence) into account ------------------------------------------------------------------------------------------------------------------------------- Key: HV-212 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-212 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.0.0.Beta3 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.0.0.CR1 See assertion 3.4.2 c of tck audit file -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2009