July 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5832) JPA Query and IdClass Causing NullPointerException

by Erich Heard (JIRA)

JPA Query and IdClass Causing NullPointerException -------------------------------------------------- Key: HHH-5832 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5832 Project: Hibernate Core Issue Type: Bug Components: metamodel Affects Versions: 3.5.1 Environment: Hibernate version 3.5.1 and Oracle 10g. Reporter: Erich Heard We had an issue when building queries dynamically with JPA objects when we accessed an @Id property of an entity class that used @IdClass. Under these conditions, Path.get( ) would return null. Here is a short illustration: The entity was specified like: @Entity // snipped more annotations @IdClass( RetailerId.class ) public class Retailer { @Id private String retailerId; public String getRetailerId( ) { return this.retailerId; } public void setRetailerId( String value ) { this.retailerId = value; } @Id private String divisionCode; public String getDivisionCode( ) { return this.divisionCode; } public void setDivisionCode( String value ) { this.divisionCode = value; } // snipped other attributes } And the ID class was specified like: @Embeddable public class RetailerId implements Serializable { private static final long serialVersionUID = -2639451633891197777L; @Column( name = "RETLR_ID", nullable = false, length = 7 ) private String retailerId; public String getRetailerId( ) { return this.retailerId; } public void setRetailerId( String value ) { this.retailerId = value; } @Column( name = "DIV_CDE", nullable = false, length = 2 ) private String divisionCode; public String getDivisionCode( ) { return this.divisionCode; } public void setDivisionCode( String value ) { this.divisionCode = value; } // snipped implementations of Serializable methods } The code that caused the error condition: CriteriaQuery<RetailerConfigurationPreference> query = cb.createQuery(RetailerConfigurationPreference.class); Root<RetailerConfigurationPreference> root = query.from(RetailerConfigurationPreference.class); Predicate predicate = root.get("retailer").get("retailerId").in(retailerIds); In this case, the 'get("retailerId")' would return null. To get around this issue, I altered the class org.hibernate.ejb.metamodel.AbstractIdentifiableType and overrode its super method getAttribute() to check the ID class for the attribute before deferring to its superclass. @Override public Attribute<? super X, ?> getAttribute(String name) { if( this.idClassAttributes != null ) { Attribute<? super X, ?> attribute = null; Iterator<SingularAttribute<? super X, ?>> i = this.idClassAttributes.iterator( ); while( i.hasNext( ) ) { attribute = i.next( ); if( attribute.getName( ).equals( name ) ) return attribute; } } return super.getAttribute( name ); } I didn't test this with EmbeddedId - that may work as is or it may need a case of its own. This is the first time I've submitted anything here, so I apologize if it is not to form. -- 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, 9 months

3
13
0 / 0

[Hibernate-JIRA] Created: (HHH-5765) Wire in JdbcServices

by Gail Badner (JIRA)

Wire in JdbcServices -------------------- Key: HHH-5765 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5765 Project: Hibernate Core Issue Type: Sub-task Components: core Reporter: Gail Badner Assignee: Gail Badner Fix For: 4.0.0.Alpha1 -- 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, 9 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-643) Have the MassIndexer use the error handler to report exceptions

by Sanne Grinovero (JIRA)

Have the MassIndexer use the error handler to report exceptions --------------------------------------------------------------- Key: HSEARCH-643 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-643 Project: Hibernate Search Issue Type: New Feature Components: massindexer Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.4.0 -- 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, 9 months

3
6
0 / 0

[Hibernate-JIRA] Created: (BVAL-224) Provide a way for accessing default implementations for XML configured bootstrap artifacts

by Gunnar Morling (JIRA)

Provide a way for accessing default implementations for XML configured bootstrap artifacts ------------------------------------------------------------------------------------------ Key: BVAL-224 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-224 Project: Bean Validation Issue Type: New Feature Components: spec-general Reporter: Gunnar Morling Using {{validation.xml}} one can specify custom implementations for constraint validator factory, message interpolator etc. Right now there is no way to delegate from within these custom implementations to the default ones. This would be possible when using the configuration API: {code} HibernateValidatorConfiguration configuration = Validation.byProvider(HibernateValidator.class).configure(); ConstraintValidatorFactory defaultFactory = configuration.getDefaultConstraintValidatorFactory(); ConstraintValidatorFactory customFactory = new CustomConstraintValidatorFactory(defaultFactory); configuration.constraintValidatorFactory(customFactory); {code} One idea to allow for such a delegation is to support constructors taking the default implementation as parameter: {code} CustomConstraintValidatorFactory implements ConstraintValidatorFactory { ConstraintValidatorFactory delegate; CustomConstraintValidatorFactory(ConstraintValidatorFactory defaultFactory) { this.delegate = defaultFactory; } } {code} For XML-configured artifacts the runtime could invoke this delegate constructor if existent, otherwise the default constructor could be invoked. -- 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, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-235) Support parameterized payload attributes

by Sebastian Thomschke (JIRA)

Support parameterized payload attributes ---------------------------------------- Key: BVAL-235 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-235 Project: Bean Validation Issue Type: New Feature Components: spec-general Affects Versions: 1.0 final Reporter: Sebastian Thomschke JSR303's payload attribute values are limited to class references. The idea is to allow the specification of an additional String value for each payload declaration allowing more flexible configurations. For example: public @interface Payload { Class< ? > type(); String value(); } @interface MinLength { Payload[] payload() default {}; // ... } class Account { @MinLength(value=4, payload = { @Payload(type=ErrorCode.class, value="1234"), @Payload(type=When.class, value="groovy:this.owner != null && this.foobar > 3") }) String name; } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HV-492) Validation of CGLIB enhanced Objects always return null

by Christian Fehmer (JIRA)

Validation of CGLIB enhanced Objects always return null ------------------------------------------------------- Key: HV-492 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-492 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.2.0.Beta2, 4.1.0.Final Environment: Hibernate Validator 4.1.0-final and 4.2.0-BETA2, cglib 2.2 Reporter: Christian Fehmer A validation of a cglib enhanced object will always validate "null". The validator (i tested it with an custom validator) always gets "null" as the value in the isValid method. The cglib enhanced object has a field "selection" and a getter/setter pair for this field. The hibernate validator uses the org.hibernate.validator.util.ReflectionHelper to access the field selection directly. That fails on a cglib enhanced object. My workaround for now: I replaced the org.hibernate.validator.util.ReflectionHelper.getValue method. When object is a cglib enhanced object i invoke the getter method instead of accessing the field directly. replaced method: public static Object getValue(Member member, Object object) { Object value = null; if (member instanceof Method) { ... } else if (member instanceof Field) { // FIX: use getter method on cglib fields if (object.getClass().getName().contains("$$")) { String methodName = member.getName(); methodName = "get"+ String.valueOf(methodName.charAt(0)).toUpperCase()+ methodName.substring(1); try { Method method = member.getDeclaringClass().getMethod( methodName); method.setAccessible(true); value = method.invoke(object); } catch (Exception e) { throw new ValidationException("Unable to access " + methodName, e); } } else { ... } } return value; } -- 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, 9 months

2
14
0 / 0

[Hibernate-JIRA] Created: (EJB-276) Support for CLOB not working for DB2 when table per concrete class is being used

by breako (JIRA)

Support for CLOB not working for DB2 when table per concrete class is being used -------------------------------------------------------------------------------- Key: EJB-276 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-276 Project: Hibernate Entity Manager Type: Bug Versions: 3.2.1 Reporter: breako Hi, This came up in the forums: http://forum.hibernate.org/viewtopic.php?p=2344008#2344008 Sample code: Two Pojos @Entity public class Person { private int i; @Identity public int getI() { return i; } public void setI(int i){ this.i = i; } } @Entity public class Employee extends Person{ @Basic(fetch=FetchType.LAZY) @Lob public String getClobAttr() { return clobAttr; } public void setClobAttr(String clobAttr) { this.clobAttr = clobAttr; } } Simple test: public static void main (String args[]) { Query queryImpl = em.createQuery(" from Person"); List list = queryImpl.getResultList(); } This will generate SQL select person0_.clobAttr as clobAttr1 from (select nullif(0,0) as clobAttr from TPerson union all select clobAttr from TEmployee) person0_ which chucks the exception: DB2 SQL error: SQLCODE: -415, SQLSTATE: 42825, SQLERRMC: null I think the SQL hibernate should generate should be: select person0_.clobAttr as clobAttr1 from (select cast(null as CLOB) as clobAttr from TPerson union all select clobAttr from TEmployee) person0_ -- 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, 9 months

5
4
0 / 0

[Hibernate-JIRA] Created: (BVAL-193) Publish javax.validation:validation-api to Maven central

by Pete Muir (JIRA)

Publish javax.validation:validation-api to Maven central -------------------------------------------------------- Key: BVAL-193 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-193 Project: Bean Validation Issue Type: Task Reporter: Pete Muir -- 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, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-200) Validator cannot find validation.xml unless is placed in /WEB-INF/classes/META-INF

by Cris Webber (JIRA)

Validator cannot find validation.xml unless is placed in /WEB-INF/classes/META-INF ---------------------------------------------------------------------------------- Key: BVAL-200 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-200 Project: Bean Validation Issue Type: Bug Components: ri-general - obsolete go to HValidator Environment: Java SE 1.5.0_10; Hibernate Validator 4.0.2.GA. Reporter: Cris Webber Priority: Minor Hibernate Validator requires that the validation.xml file is placed in the META-INF directory in order to load it. In the case of having a WAR file, placing the validation.xml file in /META-INF (at the same level as the WEB-INF directory) does not work, as Hibernate Validator cannot find the file there. Placing the file in /WEB-INF/classes/META-INF worked fine. I believe this is just a workaround and Hibernate Validator should be able to find validation.xml in /META-INF. -- 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, 9 months

3
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-231) String validation for custom types

by Andreas Grund (JIRA)

String validation for custom types ---------------------------------- Key: BVAL-231 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-231 Project: Bean Validation Issue Type: Improvement Affects Versions: 1.1 Reporter: Andreas Grund Priority: Minor Hi, as already described in ticket: http://opensource.atlassian.com/projects/hibernate/browse/HV-502 it would be nice to allow the user using e.g. @Size or @Pattern on its own types. From the point of view of the reference implementation of the Java Bean Validation, it means, that the validator classes have to be changed in the generics from String to CharSequence. Greetings, Andreas -- 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, 9 months

3
2
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 July 2011