July 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Updated: (ANN-391) SecondaryTables not recognized when using JOINED inheritance

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-391?page=co... ] Diego Pires Plentz updated ANN-391: ----------------------------------- Component/s: binder > SecondaryTables not recognized when using JOINED inheritance > ------------------------------------------------------------ > > Key: ANN-391 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-391 > Project: Hibernate Annotations > Issue Type: Bug > Components: binder > Affects Versions: 3.1.0.Beta10, 3.2.0.cr1 > Environment: Hibernate 3.2.0CR1; db is irrelevant, as the buildSessionFactory() fails. > Reporter: Sebastian Kirsch > Attachments: TestSecondaries.java, TestSecondaries.java, TestSecondaries.java > > > The Configuration doesn't recognize secondary tables of a super class. > Calling AnnotationConfiguration.buildSessionFactory fails, claiming that the secondary table used in the super class cannot be found in the subclass. > Adding the secondary table to the subclass doesn't help either. > See attached JUnit test case. -- 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

16 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (ANN-394) <properties> for annotations

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-394?page=co... ] Diego Pires Plentz updated ANN-394: ----------------------------------- Priority: Blocker Component/s: binder > <properties> for annotations > ---------------------------- > > Key: ANN-394 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-394 > Project: Hibernate Annotations > Issue Type: New Feature > Components: binder > Reporter: Emmanuel Bernard > Priority: Blocker > > It is actually hard to find a good annotation representing such a grouping. > @Properties at the entity level is nasty but is the only one I can think of that fits all the needs. -- 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

16 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HV-16) Validator ignores components

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-16?page=com.... ] Diego Pires Plentz updated HV-16: --------------------------------- Component/s: engine > Validator ignores components > ---------------------------- > > Key: HV-16 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-16 > Project: Hibernate Validator > Issue Type: Bug > Components: engine > Reporter: Emmanuel Bernard > -- 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

16 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HV-20) Include the Validator class on the InvalidValue object

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-20?page=com.... ] Diego Pires Plentz updated HV-20: --------------------------------- Component/s: engine > Include the Validator class on the InvalidValue object > ------------------------------------------------------ > > Key: HV-20 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-20 > Project: Hibernate Validator > Issue Type: Improvement > Components: engine > Reporter: Leonardo Quijano > Priority: Minor > > It'd be nice to know which validator caused an InvalidValue entry to appear. > For example, for a @NotNull annotation we'd have: > InvalidValue.getValidatorClass() == org.hibernate.validator.NotNullValidator > Then, on the web layer of the application, we could iterate over every InvalidValue[], summarizing all the NotNullValidator entries we get, and showing a msg: > * Some required fields are missing. > (and put some asterisks on the required fields, for example). > (I guess that can be done with an additional BeanValidator, but this solution lets us work with the InvalidValue[] array after all validation has taken place) -- 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

16 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-432) @Range broken for BigDecimal/BigInteger

by Emmanuel Bernard (JIRA)

@Range broken for BigDecimal/BigInteger --------------------------------------- Key: ANN-432 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-432 Project: Hibernate Annotations Type: Bug Components: validator Versions: 3.2.0.cr1 Reporter: Emmanuel Bernard -- 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

16 years, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (ANN-506) Request for Expression Language (EL) for Validator annotations

by Chris Hansen (JIRA)

Request for Expression Language (EL) for Validator annotations -------------------------------------------------------------- Key: ANN-506 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-506 Project: Hibernate Annotations Type: New Feature Components: validator Environment: All Reporter: Chris Hansen Since annotations are limited to primitive types, I would like to see a type of EL for the Validator annotations (similar to the JSF/JSP EL). This would effectively overcome this limitation of annotations and allow for very powerful functionality, such as utilizing the natural ordering of classes. For example: @Range(min="#{MyClass.MIN_OBJECT}", max="#{MyClass.MAX_OBJECT}") public MyClass getCurrent() Assuming MIN_OBJECT and MAX_OBJECT are (static, final) instances of MyClass and MyClass implements Comparable<myClass>, the validator could compare the return value of the method with both MIN_OBJECT and MAX_OBJECT and validate that it is within the desired range. This is just an example. I'm sure there are many more interesting uses possible because this is a powerful concept. The regular functionality of the annotatinos could be preserved by treating static (non-EL) values, such as the string "0", as old-style primitives, e.g. @Min(value="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

16 years, 11 months

3
3
0 / 0

[Hibernate-JIRA] Updated: (HV-21) Base class validations are not over-ridden

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-21?page=com.... ] Diego Pires Plentz updated HV-21: --------------------------------- Component/s: engine > Base class validations are not over-ridden > ------------------------------------------ > > Key: HV-21 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-21 > Project: Hibernate Validator > Issue Type: Improvement > Components: engine > Environment: hibernate 3.2 cr2 > Reporter: Aseel Abbas > > When the same validation annotation is applied to an over-riding method in a subclass the expected behaviour is that the validation annotation in the base class is over-ridden. Currently, both validations are executed. This severely limits the usability of the package for domain models where inheritance is used. > The problem also occurs with over-riding interfaces. > For example: > class A { > @Length (min = 0, max = 32) > Integer getFoo() { > return foo; > } > } > class B extends A > { > @Length (min = 15, max = 20) > Integer getFoo() { > return super.getFoo(); > } > } > In this case validating an instance of class B which has a foo value of 100 will result in two error messages: "foo must be between 15 and 20" and "foo must be between 0 and 32". -- 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

16 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HV-19) Consider higher level validations, such as email, URL, credit card, etc.

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-19?page=com.... ] Diego Pires Plentz updated HV-19: --------------------------------- Component/s: validators > Consider higher level validations, such as email, URL, credit card, etc. > ------------------------------------------------------------------------ > > Key: HV-19 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-19 > Project: Hibernate Validator > Issue Type: New Feature > Components: validators > Reporter: Ted Bergeron > Priority: Minor > > I was looking at the release notes for commons validator 1.2 http://wiki.apache.org/jakarta-commons/ValidatorVersion120 and wondered if the higher level constructs fit the design goals of hibernate validator. > They have email, URL, Credit card and ISBN. These could all be handled via @Pattern with regex matching a constant declared somewhere. > Would it be desirable to have Hibernate supply the values for these constants? Such as: > @Pattern(type="email") or @Pattern(regex=org.hibernate.validator.Pattern.EMAIL) or @Email > Email and URL are global patterns. This probably wouldn't work for something like phone number which is locale sensitive. -- 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

16 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HV-15) @Past validation annotation generates incorrect DDL for Oracle 8.x

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-15?page=com.... ] Diego Pires Plentz updated HV-15: --------------------------------- Component/s: engine > @Past validation annotation generates incorrect DDL for Oracle 8.x > ------------------------------------------------------------------ > > Key: HV-15 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-15 > Project: Hibernate Validator > Issue Type: Bug > Components: engine > Environment: Hibernate 3.0.5 > Oracle 8.1.7 (running on Win XP Pro) > Reporter: Aye Thu > Priority: Minor > > The following validation code: > @Past > public Date getBirthDate() > { > return birthDate; > } > produces the following DDL when using the OracleDialect: > create table Person (party_id number(19,0) not null, birth_date date check (birth_date < current_date), primary key (party_id)) > The "current_date" was introduced only in Oracle 9i and is not available in earlier Oracle versions and the following SQL exception is thrown: > ORA-02438: Column check constraint cannot reference other columns > According to Gavin, the current validation framework is not aware of Dialects. (http://forum.hibernate.org/viewtopic.php?t=943378) -- 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

16 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-619) Problem with @OneToOne relation in composite key

by Artur Legan (JIRA)

Problem with @OneToOne relation in composite key ------------------------------------------------ Key: ANN-619 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-619 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: PostgreSQL 8 Reporter: Artur Legan Attachments: jira.zip I got: [java] Exception in thread "main" java.lang.ExceptionInInitializerError [java] at util.HibernateUtil.<clinit>(Unknown Source) [java] at one.Start.main(Unknown Source) [java] Caused by: java.lang.NullPointerException [java] at org.hibernate.cfg.AnnotationBinder.bindOneToOne(AnnotationBinder.java:1960) [java] at org.hibernate.cfg.AnnotationBinder.processElementAnnotations(AnnotationBinder.java:1346) [java] at org.hibernate.cfg.AnnotationBinder.fillComponent(AnnotationBinder.java:1731) [java] at org.hibernate.cfg.AnnotationBinder.bindId(AnnotationBinder.java:1768) [java] at org.hibernate.cfg.AnnotationBinder.processElementAnnotations(AnnotationBinder.java:1229) [java] at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:733) [java] at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:498) [java] at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:277) [java] at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1286) [java] at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915) [java] ... 2 more when I tried to run application where i have @OneToOne in composite key (@ManyToOne worked fine) I made this code as short as I could, just put path to jars in build.xml and to database in hibernate.cfg.xml if you want to check it If I upload to much or to few just let me know, couse it's first time i'm adding stuff here I'm posting it because emmanuel told me to do it :) -- 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

16 years, 11 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2007