January 2013 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] (BVTCK-35) Improve TCK packaging for people unfamiliar with the technologies used

by Emmanuel Bernard (JIRA)

13 years, 2 months

1
2
0 / 0

[Hibernate-JIRA] (HHH-7955) UX improvement: Check for inconsistency between declared and actual class to prevent "IllegalArgumentException: object is not an instance of declaring class"

by Ondra Žižka (JIRA)

13 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7954) Allow instantiation of components using interceptor

by Nicolas DUFAILLY (JIRA)

13 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] (HSEARCH-1264) Document usage of JBoss AS 7 module

by Davide D'Alto (JIRA)

13 years, 2 months

2
3
0 / 0

[Hibernate-JIRA] (HHH-7856) Deprecate TableHiLoGenerator

by Gail Badner (JIRA)

13 years, 2 months

3
9
0 / 0

[Hibernate-JIRA] (HHH-465) order by nulls first / last

by Brett Meyer (JIRA)

13 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7951) Allow arguments to appear more than once in SQLFunctions

by Christopher Ng (JIRA)

13 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7950) bind custom tuplizer on composite attribute

by Strong Liu (JIRA)

13 years, 2 months

1
1
0 / 0

[Hibernate-JIRA] (BVAL-340) Denote method parameter constraints at declaration site (vs. at definition site)

by George Sapountzis (JIRA)

13 years, 2 months

3
10
0 / 0

[Hibernate-JIRA] Created: (BVAL-192) Add 'exclusive' boolean attribute to @DecimalMin/@DecimalMax constraints

by Jaro Kuruc (JIRA)

Add 'exclusive' boolean attribute to @DecimalMin/@DecimalMax constraints ------------------------------------------------------------------------ Key: BVAL-192 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-192 Project: Bean Validation Issue Type: Improvement Components: spec-general Affects Versions: 1.0 final Environment: Hibernate Validator 4.0.0.GA Reporter: Jaro Kuruc Attachments: patch.patch Hi, may I suggest to enhance @DecimalMin/@DecimalMax constraints with additional 'exclusive' boolean attribute? This would allow to define a constraints like: a positive non-zero decimal number @DecimalMin(value = "0.0", exclusive = true) a negative non-zero decimal number @DecimalMax(value = "0.0", exclusive = true) This makes sense when dealing with decimal numbers where one might want to allow a number regardless of the precision. @DecimalMin("0.0001") vs. @DecimalMin("0.000000001"), etc. To maintain backward compatibility, default value for new 'exclusive' boolean attribute should be false. -- 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

13 years, 2 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 January 2013