July 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5937) @Enumerated(EnumType.STRING) not taken into account in an @Embeddable included in another @Embeddable

by Thomas Vanstals (JIRA)

@Enumerated(EnumType.STRING) not taken into account in an @Embeddable included in another @Embeddable ----------------------------------------------------------------------------------------------------- Key: HHH-5937 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5937 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.6.1 Environment: MySQL 5.1.40 / hibernate-entitymanager 3.6.1.Final Reporter: Thomas Vanstals I have a Customer entity containing a collection of Investment. The Investment ({{@Embeddable}}) class contains a MonetaryAmount. The MonetaryAmount ({{@Embeddable}}) contains an enumerated property ('currency') annotated with {{(a)Enumerated(EnumType.STRING)}}. The 'currency' field is mapped to a column having the following definition: {{`currency` int(11) DEFAULT NULL}}. This is not correct. The column definition should be {{`currency` varchar(3) DEFAULT NULL}}. If a add a MonetaryAmount property in the Customer class, the generated column definition is correct ({{`currency` varchar(3) DEFAULT NULL}}). {code:title=Customer.java|borderStyle=solid} @Entity public class Customer { @Valid @ElementCollection(fetch = FetchType.EAGER) private List<Investment> investments = new ArrayList<Investment>(); } {code} {code:title=Investment.java|borderStyle=solid} @Embeddable public class Investment { @Valid @NotNull private MonetaryAmount amount; @Column(length = 500) @Length(max = 500) private String description; private Date date; } {code} {code:title=MonetaryAmount.java|borderStyle=solid} @Embeddable public class MonetaryAmount { @NotNull private Double amount; @Column(length = 3) @Enumerated(EnumType.STRING) private CurrencyCode currency; } {code} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HV-438) Call to TraversableResolver.isReachable() threw an exception

by Denis Chapligin (JIRA)

Call to TraversableResolver.isReachable() threw an exception ------------------------------------------------------------ Key: HV-438 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-438 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.2.0.Beta1, 4.1.0.Final Environment: hibernate 3.6.1.Final and hibernate validator 4.1.0.Final, GlassFish Server Open Source Edition 3.0.1, Spring 3.0.5 Reporter: Denis Chapligin I have a problem with custom class level constraint. When i try to validate a simple entity, like: @Entity @Table(name="users") @Unique //My custom constraint public class User implements Serializable { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) @Column(name="id") private Integer id; } using a spring validation helper: User u = new User(); Errors result = new BindException(u,"User"); validator.validate(u,result); It throws a NullPointer exception: # Caused by: java.lang.NullPointerException # at java.lang.Class.searchFields(Class.java:2599) # at java.lang.Class.getDeclaredField(Class.java:1880) # at org.hibernate.ejb.util.PersistenceUtilHelper$MetadataCache.findMember(PersistenceUtilHelper.java:190) # at org.hibernate.ejb.util.PersistenceUtilHelper$MetadataCache.getMember(PersistenceUtilHelper.java:178) # at org.hibernate.ejb.util.PersistenceUtilHelper.get(PersistenceUtilHelper.java:91) # at org.hibernate.ejb.util.PersistenceUtilHelper.isLoadedWithReference(PersistenceUtilHelper.java:83) # at org.hibernate.ejb.HibernatePersistence$1.isLoadedWithReference(HibernatePersistence.java:93) # at javax.persistence.Persistence$PersistenceUtilImpl.isLoaded(Persistence.java:120) # at org.hibernate.validator.engine.resolver.JPATraversableResolver.isReachable(JPATraversableResolver.java:33) # at org.hibernate.validator.engine.resolver.DefaultTraversableResolver.isReachable(DefaultTraversableResolver.java:112) # at org.hibernate.validator.engine.resolver.SingleThreadCachedTraversableResolver.isReachable(SingleThreadCachedTraversableResolver.java:47) # at org.hibernate.validator.engine.ValidatorImpl.isValidationRequired(ValidatorImpl.java:764) Some investigation revealed, that in PersistenceUtil calls the 'property' parameter value is null and in the validator.engine functions 'name' var in value of the first and single entry of propertyPath.nodeList is null too. Mot interested thing, is that when i try validation code, shown above, in JUnit environment, it works well. I've attached a simple webapp, that reproduces the issue. It is too big, to be uploaded here, so i put it to the dropbox: http://dl.dropbox.com/u/17691684/hvbug.tar.gz Initial report was on hibernate forums: https://forum.hibernate.org/viewtopic.php?f=9&t=1009612&start=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, 4 months

4
17
0 / 0

[Hibernate-JIRA] Created: (HHH-5902) In Oracle Dialect Paging query always contains "rownum" pseudo-column when the first result > 0

by Andremoniy (JIRA)

In Oracle Dialect Paging query always contains "rownum" pseudo-column when the first result > 0 ----------------------------------------------------------------------------------------------- Key: HHH-5902 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5902 Project: Hibernate Core Issue Type: Bug Components: core, query-sql Affects Versions: 3.3.2 Environment: Java 1.5, Java 1.6... Reporter: Andremoniy Priority: Critical The issue is about paging query. For example, we have simple SQL Query: "SELECT p.ID FROM SomeTable p ORDER BY p.ID". SQLQuery testQuery = HibernateUtil.currentSession().createSQLQuery("SELECT p.ID FROM SomeTable p ORDER BY p.ID"); When we set: testQuery.setFirstResult(0); testQuery.setMaxResults(10); List objs = testQuery.list(); "objs" will contain 10 simple objects of String type (for example). But, when se set: testQuery.setFirstResult(10); // here, any value > 0 testQuery.setMaxResults(10); List objs = testQuery.list(); we will receive list of Object[2] objects: ID ROWNUM 3212 11 5212 12 5435 13 ... It is absolutely clear, that the core of the problem is in this construction: Oracle9iDialect.class, public String getLimitString(String sql, boolean hasOffset) { ... if (hasOffset) { pagingSelect.append("select * from ( select row_.*, rownum rownum_ from ( "); } The resulting query will be: select * from ( select row_.*, rownum rownum_ from ( SELECT p.ID FROM SomeTable p ORDER BY p.ID ) row_ where rownum <=20) where rownum_ > 10 Why this is a bug? 1. Because I don't want to check: if my query will return simple Object types or Object[] depends on "First Result value". 2. Because I don't need to have second pseudo-column with "rownum" value. It must be optional parameter. Simple solution for this example could be (see on >>> ID <<<): select >>> ID <<< from ( select row_.*, rownum rownum_ from ( SELECT p.ID FROM SomeTable p ORDER BY p.ID ) row_ where rownum <=20) where rownum_ > 10 But, of course, in this case this first part of "select" query must be retranslated from inner source query (so, it will be not "SELECT p.ID..." but "SELECT ID" and so on). -- 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, 4 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-800) Should we move ORM related APIs to org.hibernate.search.orm? Today they are in org.hibernate.search

by Emmanuel Bernard (JIRA)

Should we move ORM related APIs to org.hibernate.search.orm? Today they are in org.hibernate.search --------------------------------------------------------------------------------------------------- Key: HSEARCH-800 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-800 Project: Hibernate Search Issue Type: Improvement Reporter: Emmanuel Bernard Fix For: 4.0 Thoughts? -- 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, 4 months

2
9
0 / 0

[Hibernate-JIRA] Created: (HV-496) Include Hibernate Validator test classes in a different classifier

by George Gastaldi (JIRA)

Include Hibernate Validator test classes in a different classifier ------------------------------------------------------------------ Key: HV-496 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-496 Project: Hibernate Validator Issue Type: Task Reporter: George Gastaldi It would be nice if the Hibernate Validator test classes were included in a different classifier so that these test classes could be reused on another projects as well. -- 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, 4 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HV-502) Changing Generic Type on @Size, @Pattern a.s.o. from String to CharacterSequence

by Andreas Grund (JIRA)

Changing Generic Type on @Size, @Pattern a.s.o. from String to CharacterSequence -------------------------------------------------------------------------------- Key: HV-502 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-502 Project: Hibernate Validator Issue Type: Improvement Components: validators Affects Versions: 4.2.0.CR1 Environment: Hibernate Validator 4.2 Reporter: Andreas Grund Priority: Minor Hi, it would be nice, if the Generic Type of the Validators for the @Size or @Pattern Annotation (exactly for all String based Validators) could be changed from String to CharSequence. This allows the user to implement it own CharSequence Implementations (e.g. a String Delegation class) and to use the Bean validation with his own Implementation without the need of additional configuration. 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, 4 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HV-473) Add option to Canonicalize String Input

by Chris Schmidt (JIRA)

Add option to Canonicalize String Input --------------------------------------- Key: HV-473 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-473 Project: Hibernate Validator Issue Type: Improvement Components: engine Environment: n/a Reporter: Chris Schmidt Add the ability to enable canonicalization (normalization) of Strings prior to validation processing. By default this behavior should be enabled. Canonicalization is imperative in validation logic, without it - it is possible to bypass many validation contraints (string based) to perform things like encoding attacks (XSS, SQLi) and Path traversal attacks (RFI, LFI). This canonicalization should be configurable to allow Multiple or Mixed encoding in a string (with a default to fail validation if either condition is true) through the use of annotation: @Canonicalize(allowMixed=true, allowMultiple=true) @Pattern(regexp=".*") private String someString; This is necessary, especially when using validation on machine generated values (webservices, etc.) to allow a string to be canonicalized to it's base form even if there are multiple or mixed encodings in the string. However, this is not behavior that a normal application user would display - hence the approach of disallowing a string of this type by default. Please reference the OWASP ESAPI for an example of how to implement: http://code.google.com/p/owasp-esapi-java/source/browse/trunk/src/main/ja... For additional information on the importance of canonicalization in validation see: https://www.owasp.org/index.php/Canonicalization,_locale_and_Unicode Feel free to use the ESAPI Library or any of it's code to help Hibernate-Validator be more secure and complete! -- 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, 4 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HV-507) Let people specify via properties the name of the resource file

by Emmanuel Bernard (JIRA)

Let people specify via properties the name of the resource file --------------------------------------------------------------- Key: HV-507 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-507 Project: Hibernate Validator Issue Type: New Feature Reporter: Emmanuel Bernard Priority: Minor See https://forum.hibernate.org/viewtopic.php?f=26&t=1011623&p=2447057#p2447057 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4108) Invalid result in native query

by Oleksandr Fedorenko (JIRA)

Invalid result in native query ------------------------------ Key: HHH-4108 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4108 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.2 Environment: 3.3.2, MySQL 5.1 Reporter: Oleksandr Fedorenko Priority: Critical We have the native query executed with entity manager, example : Query query = entityManager.createNativeQuery(sqlString); List result = query.getResultList(); The returned result is an array of objects that has projection values. When table column has type CHAR(N) , the result value is always instance of java.lang.Character and here we have only first character of database field and the rest characters are lost. It is supposed to have result of java.lang.String class here. When the column is altered to VARCHAR(N), the result is java.lang.String. -- 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, 4 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3684) Sybase - Setting FetchMode.JOIN fails if there are 3 or more joins and at least one join involves a union

by Gail Badner (JIRA)

Sybase - Setting FetchMode.JOIN fails if there are 3 or more joins and at least one join involves a union --------------------------------------------------------------------------------------------------------- Key: HHH-3684 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3684 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Gail Badner Assignee: Gail Badner This is reproduced by UnionSubclassTest.testUnionSubclassFetchMode().. This may be due to a bug in Sybase. A similar problem is discussed here: http://www.forumtopics.com/busobj/viewtopic.php?p=442226&sid=40bd96248c52... For the unit test mentioned above, changing: select ... from ( select ... from humans union select ... from employees ) this_ inner join locations location2_ on this_.location=location2_.id left outer join ( select ... from employees union select ... from humans union select ... from aliens ) beings3_ on location2_.id=beings3_.location : to: select ... from ( select ... from humans union select ... from employees ) this_ inner join (locations location2_ left outer join ( select ... from employees union select ... from humans union select ... from aliens ) beings3_ on location2_.id=beings3_.location) : on this_.location=location2_.id fixes the problem. This changer is similar to what is documented for a "right-nested outer join" at http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc32300.150.... -- 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, 4 months

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