March 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Moved: (HV-8) Make Validator support pure JavaPersistence players

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-8?page=all ] Emmanuel Bernard moved ANN-546 to HV-8: --------------------------------------- Fix Version: (was: 3.2.2) FIRST Component: (was: validator) engine Key: HV-8 (was: ANN-546) Project: Hibernate Validator (was: Hibernate Annotations) > Make Validator support pure JavaPersistence players > --------------------------------------------------- > > Key: HV-8 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-8 > Project: Hibernate Validator > Type: New Feature > Components: engine > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Fix For: FIRST > > > Through EntityListeners > It won't support parameters such as interpolator though since the listener lifecycle is not defined and there is no way to pass the PU properties -- 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

18 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Moved: (HSEARCH-29) Share the initialization state across all Search event listeners instance

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-29?page... ] Emmanuel Bernard moved ANN-524 to HSEARCH-29: --------------------------------------------- Fix Version: (was: 3.2.2) FIRST Component: (was: search) engine Key: HSEARCH-29 (was: ANN-524) Project: Hibernate Search (was: Hibernate Annotations) > Share the initialization state across all Search event listeners instance > ------------------------------------------------------------------------- > > Key: HSEARCH-29 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-29 > Project: Hibernate Search > Type: Improvement > Components: engine > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Fix For: FIRST > > > Not a major issue, but allows faster initialization and better lock scheme -- 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

18 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Moved: (HV-7) Two level @Valid annotation doesn't work

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-7?page=all ] Emmanuel Bernard moved ANN-511 to HV-7: --------------------------------------- Version: (was: 3.2.1) Bundle 3.2.1 Fix Version: (was: 3.2.2) FIRST Component: (was: validator) engine Key: HV-7 (was: ANN-511) Project: Hibernate Validator (was: Hibernate Annotations) > Two level @Valid annotation doesn't work > ----------------------------------------- > > Key: HV-7 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-7 > Project: Hibernate Validator > Type: Bug > Components: engine > Versions: Bundle 3.2.1 > Environment: hibernate-annotations 3.2.1.ga > Reporter: Rakesh Kalra > Assignee: Emmanuel Bernard > Fix For: FIRST > > Original Estimate: 1 hour > Remaining: 1 hour > > I have object depth of 3: Form, Member, Address. I get the following exception when initializing ClassValidator: > java.lang.NullPointerException > at org.hibernate.validator.ClassValidator.<init>(ClassValidator.java:142) > at org.hibernate.validator.ClassValidator.createChildValidator(ClassValidator.java:252) > at org.hibernate.validator.ClassValidator.initValidator(ClassValidator.java:216) > at org.hibernate.validator.ClassValidator.<init>(ClassValidator.java:149) > at org.hibernate.validator.ClassValidator.createChildValidator(ClassValidator.java:252) > at org.hibernate.validator.ClassValidator.initValidator(ClassValidator.java:216) > at org.hibernate.validator.ClassValidator.<init>(ClassValidator.java:134) > at org.hibernate.validator.ClassValidator.<init>(ClassValidator.java:105) > at org.hibernate.validator.ClassValidator.<init>(ClassValidator.java:97) > ... > This works fine with 3.2.0.ga. > I think the problem is in the following constructor, where instance level "reflectionManager" is not being initialized. > protected ClassValidator( > XClass beanXClass, ResourceBundle resourceBundle, MessageInterpolator userInterpolator, > Map<XClass, ClassValidator> childClassValidators, ReflectionManager reflectionManager > ) { > this.beanClass = reflectionManager.toClass( beanXClass ); > this.messageBundle = resourceBundle == null ? > getDefaultResourceBundle() : > resourceBundle; > this.defaultMessageBundle = ResourceBundle.getBundle( DEFAULT_VALIDATOR_MESSAGE ); > this.userInterpolator = userInterpolator; > this.childClassValidators = childClassValidators; > initValidator( beanXClass, childClassValidators ); > } > The other constructor initializes reflectionManager. -- 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

18 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Moved: (HSEARCH-28) Wrong indexDir property in Apache Lucene Integration

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-28?page... ] Emmanuel Bernard moved ANN-534 to HSEARCH-28: --------------------------------------------- Fix Version: (was: 3.2.2) FIRST Component: (was: documentation) documentation Key: HSEARCH-28 (was: ANN-534) Project: Hibernate Search (was: Hibernate Annotations) > Wrong indexDir property in Apache Lucene Integration > ---------------------------------------------------- > > Key: HSEARCH-28 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-28 > Project: Hibernate Search > Type: Bug > Components: documentation > Environment: Hibernate 3.2.1 > Reporter: Bartosz Jablonski > Assignee: Emmanuel Bernard > Fix For: FIRST > > > According to documentation property to configure indexes directory is named "hibernate.search.*.indexDir", but in hibernate 3.2.1 FSDirectoryProvider searches for property ending with "indexBase". -- 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

18 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Moved: (HV-6) @EAN

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-6?page=all ] Emmanuel Bernard moved ANN-510 to HV-6: --------------------------------------- Fix Version: (was: 3.2.2) FIRST Component: (was: validator) validators Key: HV-6 (was: ANN-510) Project: Hibernate Validator (was: Hibernate Annotations) > @EAN > ---- > > Key: HV-6 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-6 > Project: Hibernate Validator > Type: New Feature > Components: validators > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Priority: Minor > Fix For: FIRST > > -- 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

18 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Moved: (HV-5) Multiple validators of the same type per element (John Gilbert)

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-5?page=all ] Emmanuel Bernard moved ANN-513 to HV-5: --------------------------------------- Version: (was: 3.2.1) Bundle 3.2.1 Fix Version: (was: 3.2.2) FIRST Component: (was: validator) validators Key: HV-5 (was: ANN-513) Project: Hibernate Validator (was: Hibernate Annotations) > Multiple validators of the same type per element (John Gilbert) > --------------------------------------------------------------- > > Key: HV-5 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-5 > Project: Hibernate Validator > Type: Improvement > Components: validators > Versions: Bundle 3.2.1 > Reporter: Edwin van der Elst > Assignee: Emmanuel Bernard > Priority: Minor > Fix For: FIRST > Attachments: ClassValidator.java, validators_patch.txt > > > I have a suggestion for the following problem: > I created an Validator to check if a 'date'> 'another date' > The annotation looks like this: > @After(property="endDate", after="beginDate", message="End should be after begin") > Since it involves 2 properties, it is a class-level validation. > Now.... > I want multiple 'after' validations on a single bean. > But that is not possible (you can only place an annotation once on a class). > My proposal is to add an annotation 'Validations': > @Validations( {@After(...), @After(..)} ) > I could do the multiple validations in a single validatorclass, but I want all the messages added to the invalidValues array, not a single message. > This change would also require changes in the ClassValidator class. > What do you think of this proposal? Should I add it to Jira (I can propably implement it if there are no objections to the required changes) -- 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

18 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2376) Query with fully qualified entity class fails

by Neukomm (JIRA)

Query with fully qualified entity class fails --------------------------------------------- Key: HHH-2376 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2376 Project: Hibernate3 Type: Bug Components: query-hql Versions: 3.2.1 Environment: Hibernate 3.2.1ga, HSQLDB 1.8.0.4 Reporter: Neukomm Attachments: DiscriminatorTest2.java We've recently ran into a problem while migrating from Hibernate 3.1.1 to Hibernate 3.2.1ga: While queries against the class attribute still work, if the class is non-qualified, the query fails if the name is fully qualified. e.g. "from Person p where p.class = Person" works fine while "from Person p where p.class = org.hibernate.test.discriminator.Person" fails. I've attached a test case to illustrated the problem. It should work when it's put into the 'discriminator' package of the hibernate junit test cases. Both testcases work fine for hibernate versions up to and including 3.2.0cr2. In later versions, specifically in 3.2.1ga, the test case that uses the fully qualified class name ('testQueryWithPackage') fails. -- 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

18 years, 7 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HBX-913) launch config are not really deleted when deleting console configs

by Max Rydahl Andersen (JIRA)

launch config are not really deleted when deleting console configs ------------------------------------------------------------------ Key: HBX-913 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-913 Project: Hibernate Tools Type: Bug Components: consoleconfiguration Versions: 3.2beta10 Reporter: Max Rydahl Andersen when restarting they pops back up again -- 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

18 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2476) PersistentMap.put() incorrect on uninitialized, non-extra-lazy map

by Steve Ebersole (JIRA)

PersistentMap.put() incorrect on uninitialized, non-extra-lazy map ------------------------------------------------------------------ Key: HHH-2476 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2476 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.2 Reporter: Steve Ebersole Assigned to: Steve Ebersole Fix For: 3.2.3 Essentially, an uninitialized PersistentMap loses the first put() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#put() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to read the element directly from the map. Long story short, PersistentMap#put() does not properly check the return value from readElementByIndex() and react accordingly. -- 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

18 years, 7 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HBX-912) Table Filter folds schema name to lowercase in query -- fails on Oracle9

by James Garrison (JIRA)

Table Filter folds schema name to lowercase in query -- fails on Oracle9 ------------------------------------------------------------------------ Key: HBX-912 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-912 Project: Hibernate Tools Type: Bug Components: reverse-engineer Versions: 3.2beta9 Environment: Hibernate tools 3.2.0beta9 Oracle 9 Reporter: James Garrison Attachments: reveng1.gif, reveng2.gif In the RevEng table filter dialog I enter the schema name in uppercase. When HBX generates the query to fetch the names of database objects, it folds the schema name to lowercase. Since Oracle does a case-sensitive comparison, no database objects are returned. I have verified this by running a network packet capture with Wireshark, and attached screenshots of the Table Filters page and the session trace. -- 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

18 years, 7 months

2
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2007