December 2011 - hibernate-issues - Jboss List Archives

[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

12 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HV-536) Upgrade JSoup dependency

by Hardy Ferentschik (JIRA)

Upgrade JSoup dependency ------------------------ Key: HV-536 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-536 Project: Hibernate Validator Issue Type: Task Components: validators Affects Versions: 4.2.0.Final Reporter: Hardy Ferentschik Fix For: 4.3.0.next Upgrade from 1.5.2 to 1.6.1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6882) add API to AbstractCollectionEvent for accessing CollectionPersister

by Krasimir Chobantonov (JIRA)

add API to AbstractCollectionEvent for accessing CollectionPersister -------------------------------------------------------------------- Key: HHH-6882 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6882 Project: Hibernate Core Issue Type: Improvement Environment: any Reporter: Krasimir Chobantonov When collection events are fired by Hibernate and the collection is not initialized because it was not PersistenceCollection or it was null then the listener will get the event but there is no way to tell which property of the entity is being changed. Because the collection is null then we can't get the collection persister using the session. The collection role is also not stored anywhere in the event. For listeners that performs audit/security and etc. this information is needed even when the target persistence collection was not loaded. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-537) Reintroduce jdocbook.ignoreTranslations in the docbook configuration

by Hardy Ferentschik (JIRA)

Reintroduce jdocbook.ignoreTranslations in the docbook configuration -------------------------------------------------------------------- Key: HV-537 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-537 Project: Hibernate Validator Issue Type: Bug Reporter: Hardy Ferentschik Fix For: 4.3.0.next After making the documentation its own module the docbook configuration changed and the property _jdocbook.ignoreTranslations_ which is still defined in the master pom is not used anymore. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-535) Validator sees all nulls on proxy object when proxied entity class has constraint annotations applied to fields instead of methods

by Jesse Hutton (JIRA)

Validator sees all nulls on proxy object when proxied entity class has constraint annotations applied to fields instead of methods ---------------------------------------------------------------------------------------------------------------------------------- Key: HV-535 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-535 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.2.0.Final, 4.1.0.Final Environment: RHEL 6.1 Reporter: Jesse Hutton When hibernate creates a proxy of an entity relation (eg. when FetchType.LAZY is specified on a @ManyToOne relationship) and the Bean Validation annotations have been applied on the proxied class to fields instead of methods, the validator can't see any values. All it sees are nulls. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 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

12 years, 6 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6879) EntityMode.DOM4J cannot be resolved

by Pascal favre (JIRA)

EntityMode.DOM4J cannot be resolved ----------------------------------- Key: HHH-6879 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6879 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.CR7 Reporter: Pascal favre Priority: Blocker EntityMode.DOM4J seems not to be supported any longer! Session session = SessionFactoryUtil.getSessionFactory().openSession(); session = session.getSession(EntityMode.DOM4J); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-6878) cannot insert a blank or empty xml element through dom4j entity mode

by Pascal favre (JIRA)

cannot insert a blank or empty xml element through dom4j entity mode -------------------------------------------------------------------- Key: HHH-6878 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6878 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.8, 3.6.1 Reporter: Pascal favre Priority: Blocker Attachments: blankXmlElement.tar.gz I'd like to insert or update data through xml data. I cannot send empty element for the type Integer, Long, ... to reset or nullify fields that are nullable. the following execption is thrown: Exception in thread "main" java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:468) the data I'd like to nullify: <PersonBlankValue> <agePerson xsi:nill=\"true\" xmlns:xsi= \"http://www.w3.org/2001/XMLSchema-instance\"/> <name> .... </PersonBlankValue> I provide you a simple test case -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-6866) UUID wrongly mapped as 'char(255) for bit data' on DB2

by Hardy Ferentschik (JIRA)

UUID wrongly mapped as 'char(255) for bit data' on DB2 ------------------------------------------------------ Key: HHH-6866 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6866 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.CR6 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.0.0.next The value range for char on DB2 is 1 to 254! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
7
0 / 0

[Hibernate-JIRA] Updated: (HHH-1123) Cannot put more than 1000 elements in a InExpression

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1123?page=c... ] Steve Ebersole updated HHH-1123: -------------------------------- Pull Requests: (was: https://github.com/hibernate/hibernate-core/pull/234) > Cannot put more than 1000 elements in a InExpression > ---------------------------------------------------- > > Key: HHH-1123 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1123 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Affects Versions: 3.1 rc2, 3.2.0.alpha1 > Environment: Oracle 9i > Reporter: Alexis Seigneurin > Attachments: Animal.hbm.xml, hibernate-inexpression-oracle-3.2.patch, HQLHelper.java, LongInElementsTest.java, patch.txt > > Original Estimate: 1h > Remaining Estimate: 1h > > The number of elements that we can put in a "in" expression is limited to a certain amount (1000 for Oracle, for instance). When creating a criteria query, the org.hibernate.criterion.InExpression class should split the expression into several smaller ones. > Attached is a patch which splits the expression by slices of 500 elements. For example, if we have 1001 elements to put in the "in" expression, the result would be : > (entity.field in (?, ?, ?...) or entity.field in (?, ?, ?...) or entity.field in (?)) > The surrounding parantheses are useful to avoid problems with other conditions (a "and" condition taking over the one of the "or" conditions). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2011