May 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-36) Meaningful exception message when Search Listeners are not initialized

by Emmanuel Bernard (JIRA)

Meaningful exception message when Search Listeners are not initialized ---------------------------------------------------------------------- Key: HSEARCH-36 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-36 Project: Hibernate Search Issue Type: Improvement Affects Versions: 3.0.0.beta2 Reporter: Emmanuel Bernard Priority: Trivial org.hibernate.HibernateException: Lucene event listener not initialized at org.hibernate.search.util.ContextHelper.getSearchFactoryBySFI(ContextHelper.java:31) at org.hibernate.search.query.FullTextQueryImpl.list(FullTextQueryImpl.java:145) at mil.darpa.tn.model.ReportModelFactory.searchReports(ReportModelFactory.java:128) at mil.darpa.tn.model.ReportFactory.searchReports(ReportFactory.java:82) at mil.darpa.tn.TNMain.main(TNMain.java:89) -- 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

17 years, 7 months

2
2
0 / 0

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

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-21?page=com.... ] Emmanuel Bernard moved ANN-344 to HV-21: ---------------------------------------- Affects Version/s: (was: 3.2.0.cr1) Component/s: (was: validator) Key: HV-21 (was: ANN-344) Project: Hibernate Validator (was: Hibernate Annotations) > 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 > 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

17 years, 7 months

1
0
0 / 0

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

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-20?page=com.... ] Emmanuel Bernard moved ANN-143 to HV-20: ---------------------------------------- Affects Version/s: (was: 3.1beta6) Component/s: (was: validator) Key: HV-20 (was: ANN-143) Project: Hibernate Validator (was: Hibernate Annotations) > 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 > 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

17 years, 7 months

1
0
0 / 0

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

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-19?page=com.... ] Emmanuel Bernard moved ANN-150 to HV-19: ---------------------------------------- Affects Version/s: (was: 3.1beta6) Component/s: (was: validator) Key: HV-19 (was: ANN-150) Project: Hibernate Validator (was: Hibernate Annotations) > 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 > 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

17 years, 7 months

1
0
0 / 0

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

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-16?page=com.... ] Emmanuel Bernard moved ANN-65 to HV-16: --------------------------------------- Affects Version/s: (was: 3.1beta4) Component/s: (was: validator) Key: HV-16 (was: ANN-65) Project: Hibernate Validator (was: Hibernate Annotations) > Validator ignores components > ---------------------------- > > Key: HV-16 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-16 > Project: Hibernate Validator > Issue Type: Bug > 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

17 years, 7 months

1
0
0 / 0

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

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-15?page=com.... ] Emmanuel Bernard moved ANN-21 to HV-15: --------------------------------------- Affects Version/s: (was: 3.1beta3) Component/s: (was: validator) Key: HV-15 (was: ANN-21) Project: Hibernate Validator (was: Hibernate Annotations) > @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 > 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

17 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Assigned: (ANN-28) @Any

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-28?page=com... ] Emmanuel Bernard reassigned ANN-28: ----------------------------------- Assignee: Emmanuel Bernard > @Any > ---- > > Key: ANN-28 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-28 > Project: Hibernate Annotations > Issue Type: Patch > Components: binder > Affects Versions: 3.1beta3 > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Priority: Trivial > Fix For: 3.3.1 > > Attachments: annotations-any-patch.txt, annotations-any-patch2.txt > > > @AnyValue(value="", class="") //or MetaValue? > @Any(idType="", metaType="", metaValues={@MetaValue()}, columns={@Column()}) -- 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

17 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-43) Expose resultSize and do not load object when only resultSize is retrieved

by Emmanuel Bernard (JIRA)

Expose resultSize and do not load object when only resultSize is retrieved -------------------------------------------------------------------------- Key: HSEARCH-43 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-43 Project: Hibernate Search Issue Type: New Feature Components: query Reporter: Emmanuel Bernard Fix For: 3.0.0.beta2 -- 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

17 years, 7 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2611) hibernate-mapping-3.0.dtd: add support for "node" attribute in "list-index" element

by Jens Fischer (JIRA)

hibernate-mapping-3.0.dtd: add support for "node" attribute in "list-index" element ----------------------------------------------------------------------------------- Key: HHH-2611 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2611 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.4 Environment: Hibernate 3.2.4, HSQLDB 1.8.0.7 Reporter: Jens Fischer Priority: Minor Attachments: hibernate-list-index-node.zip Current hibernate-mapping-3.0.dtd does not support an optional "node" attribute for the element "list-index", as supported for instance for the element "map-key". Find attached a JUnit test case showing the effects when writing XML using EntityMode.DOM4J, once with and once without a "node" attribute. -- 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

17 years, 7 months

1
1
0 / 0

[Hibernate-JIRA] Commented: (ANN-199) NPE when mappedBy property is wrong on a @OneToOne

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-199?page=co... ] Emmanuel Bernard commented on ANN-199: -------------------------------------- can you open a new jira issue with a reproducible test case? > NPE when mappedBy property is wrong on a @OneToOne > -------------------------------------------------- > > Key: ANN-199 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-199 > Project: Hibernate Annotations > Issue Type: Bug > Components: binder > Affects Versions: 3.1beta7 > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Priority: Minor > Fix For: 3.1beta8 > > -- 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

17 years, 7 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 May 2007