March 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-486) @AllField to concatenate all fields in a massive searchable one

by Emmanuel Bernard (JIRA)

@AllField to concatenate all fields in a massive searchable one --------------------------------------------------------------- Key: ANN-486 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-486 Project: Hibernate Annotations Type: New Feature Reporter: Emmanuel Bernard Fix For: 3.3.0 This is not useful strictly speaking since MultiFieldQueryParser solve the problem, but it is convenient. Note that it will only work for StringBridges @AllField(name="all", properties = {""} ) //optionally include only properties listed -- 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, 1 month

1
1
0 / 0

[Hibernate-JIRA] Moved: (HV-11) consider making validator framework truely independant of hibernate core

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-11?page=all ] Emmanuel Bernard moved ANN-318 to HV-11: ---------------------------------------- Version: (was: 3.1beta9) Component: (was: validator) engine Key: HV-11 (was: ANN-318) Project: Hibernate Validator (was: Hibernate Annotations) > consider making validator framework truely independant of hibernate core > ------------------------------------------------------------------------ > > Key: HV-11 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-11 > Project: Hibernate Validator > Type: Improvement > Components: engine > Reporter: Andreas Schildbach > > > I'd like to use the validator framework, but without pulling hibernate in as a dependency. > Currently, if I try to instantiate a ClassValidator, a org.hibernate.MappingException cannot be found. > Consequently, the validator framework could also be independent of the rest of the annotations, and be distributed in its own jar. -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-552) Transparent event integration for Search and Validator

by Emmanuel Bernard (JIRA)

Transparent event integration for Search and Validator ------------------------------------------------------ Key: ANN-552 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-552 Project: Hibernate Annotations Type: New Feature Reporter: Emmanuel Bernard Fix For: 3.3.0 breaks current configurations, so tag it for 3.3 -- 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, 1 month

1
1
0 / 0

[Hibernate-JIRA] Created: (ANN-528) avoid auto import of superclasses to avoid inheritance mapping

by Armin Haaf (JIRA)

avoid auto import of superclasses to avoid inheritance mapping -------------------------------------------------------------- Key: ANN-528 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-528 Project: Hibernate Annotations Type: New Feature Components: binder Reporter: Armin Haaf It is not possible to avoid inheritance mapping if the superclass of a entity is also a entity. Background: A framework provides a basic mapping of a entity, but I want to extend that. With annotations it is not possible to just map my extended version and have the superclass behave like a MappedSuperclass. This behaviour is acceptable but it is not possible to override a the id generation. So it might be better to have a new annotation (e.g. @RootEntity(mapSuperclass=true)) to avoid auto import of the entity superclass. With that approach it would be easier to create modules and frameworks -- 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, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-569) Map the same class twice in orm.xml

by Christian Bauer (JIRA)

Map the same class twice in orm.xml ----------------------------------- Key: ANN-569 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-569 Project: Hibernate Annotations Type: New Feature Components: binder Reporter: Christian Bauer Priority: Minor Regular annotated class, I'd like to map it again in orm.xml with a different set of persistent attributes (they are annotated transient in the regular class):  <entity class="Node" name="RegularNode" access="FIELD"> <table name="NODE"/> </entity> <entity class="Node" name="HistoricalNode" access="FIELD"> <table name="NODE_HISTORY"/> <attributes> <id name="historicalNodeId"> <column name="NODE_HISTORY_ID"/> <generated-value/> </id> <basic name="revision" optional="false"> <column name="NODE_REVISION"/> </basic> <basic name="id" optional="false"> <column name="NODE_ID"/> </basic> </attributes> </entity> I currently only have 3.2.0 CR1 (Seam...) here: [hibernatetool] javax.persistence.PersistenceException: java.lang.IllegalStateException: Duplicate XML entry for org.jboss.seam.wiki.core.node.Node [hibernatetool] java.lang.IllegalStateException: Duplicate XML entry for org.jboss.seam.wiki.core.node.Node If the spec forbids duplicate class names in orm.xml (does it?) - how can I override mappings under a different entity alias? -- 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, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (ANN-570) @DiscriminatorForumla typo

by Diego Pires Plentz (JIRA)

@DiscriminatorForumla typo -------------------------- Key: ANN-570 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-570 Project: Hibernate Annotations Type: Bug Components: documentation Versions: 3.2.1 Reporter: Diego Pires Plentz Priority: Minor http://www.hibernate.org/hib_docs/annotations/reference/en/html_single/#e... @Entity @DiscriminatorFor***um***la("case when forest_type is null then 0 else forest_type end") public class Forest { ... } should be @Entity @DiscriminatorFor***mu***la("case when forest_type is null then 0 else forest_type end") public class Forest { ... } -- 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, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-557) The BigDecimal is not correct to save to database

by Anton P. (JIRA)

The BigDecimal is not correct to save to database ------------------------------------------------- Key: ANN-557 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-557 Project: Hibernate Annotations Type: Bug Versions: 3.1beta3 Environment: Hibernate-Version: 3.1.3, Oracle 10.0.1 JDK 1.5.0_07-b03 Reporter: Anton P. The release of BigDecimal differents in jvm 1.4 and 1.5. in jvm 1.5 BigDecimal.toString() will return ~ 0E-07 if this 0.0000000 and when hibernate make save this. in that field of table will put 7. that is not good. http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6298816 http://www.obscured.info/java/java-5-and-the-bigdecimal/ -- 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, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-567) Ability to specify a custom persister on a collection seems to be missing

by Shawn Clowater (JIRA)

Ability to specify a custom persister on a collection seems to be missing ------------------------------------------------------------------------- Key: ANN-567 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-567 Project: Hibernate Annotations Type: Bug Components: binder Versions: 3.2.1 Environment: Hibernate 3.2.2 Reporter: Shawn Clowater There doesn't seem to be a mechanism to set the collectionPersister property on a Collection via annotations. I think the solution is as simple as adding a new annotation, kind of like the org.hibernate.annotation.Entity that would allow the user to specify the persister class and then having the AnnotationBinder parse that when it's parsing the annotations like @Cache, etc. If there is a particular name that you would like for the annotation I'll even do it up and provide a patch as I'm going to need it PDQ to continue on my side of things. -- 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, 1 month

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2483) Equals method of Embeddable object not getting called.

by Unnikrishnan.k.v (JIRA)

Equals method of Embeddable object not getting called. ------------------------------------------------------ Key: HHH-2483 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2483 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.2 Environment: Hibernate 3.2.2, JavaDB Reporter: Unnikrishnan.k.v As a work around to issue reported in HHH-2482, I tried using a Embeddable object *PasswordHolder* which implements correct equals method to compare char[]'s. But even then hibernate is calling equals method of char[] instead of equals method implemented in PasswordHolder. I am pasting the PasswordHolder source below. To reproduce the issue, 1. create an entity with PasswordHolder as embedded field. 2. Use version number for optimistic locking. 3. Insert a row into db. 4. Now fetch this row through Hibernate entity manager. 5. After the program exits, check the version number of the accessed row. import java.io.Serializable; import java.sql.SQLClientInfoException; import javax.persistence.Column; import javax.persistence.Embeddable; /** * * @author unni */ @Embeddable public class PasswordHolder implements Serializable { /** Creates a new instance of Password */ public PasswordHolder() { } public PasswordHolder(char[] password) { this.password = password; } private char[] password; @Column(length = 32, nullable = false) public char[] getPassword() { return password; } public void setPassword(char[] password) { this.password = password; } public boolean equals(Object o) { if (o instanceof PasswordHolder) { AppUtil appUtil = AppUtil.getInstance(); return (0 == appUtil.compare(this.password, ((PasswordHolder)o).password)); } return false; } public int hashCode() { return password.hashCode(); } } -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2482) Equals method missing in CharArrayType

by Unnikrishnan.k.v (JIRA)

Equals method missing in CharArrayType -------------------------------------- Key: HHH-2482 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2482 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.2 Environment: hibernate-3.2.2.ga, JavaDB Reporter: Unnikrishnan.k.v I am working on a Hibernate entity which contains a char[] field to store password. public class Contact implements java.io.Serializable { private String userName; private char[] password; private Integer version; } Now the problem that I am observing is, version is getting incremented even when none of the fields are changed. Hibernate log showed that *password* field is getting dirty. But, on doing single step debug I found that hibernate is using EqualsHelper.equals() method to compare two arrays. This results in wrong result. I think, the correct implementation should be to add an equals method in CharArrayType.java. -- 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, 1 month

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 March 2007