April 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3887) Envers hbm xml based configuration

by Helmut Pasch (JIRA)

Envers hbm xml based configuration ---------------------------------- Key: HHH-3887 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3887 Project: Hibernate Core Issue Type: Improvement Components: envers Affects Versions: 3.5 Environment: Hibernate: All Hibernate Versions including Envers as subproject Our Project: Hibernate 3.3.1, Spring 2.5.6, Spring DM 1.2.0, Swing, GWT, .... Reporter: Helmut Pasch Currently the tool library Envers can only be configured / mapped to java POJOs by annotations. We would appreciate if this mapping could be done by hbm xml files. Using this approach the POJO won't be bound to Envers annotations. They simply would be left as POJOs instead of transformed to JPA like Entity Beans. We use POJOs to directly serialize them to a client tier, e.g. a Swing or GWT client tier. If our POJOs have to rely on Envers annotations similar like JPA annotations we see only two options objects may leave the server tier. First by a copy to an annotation less value object, which is consuming performance and resources. Second by coping / using Envers / Hibernate libraries for reference purposes on the client tier. Both solutions are not very attractive compared to the very well working hbm xml approach Hibernate core ORM functionality provides us. It is our intention to reduce / eliminate in client server communication model transformations like coping objects or transforming them to other formats like XML, e.g. like web services does. The easiest way would be to just serialize the Java POJO objects. But never then less the client should only depend (logically) on the server API. It is not intended to rely on a specific server implementation. -- 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

14 years, 5 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5525) Convert Getting Started Guide to use DocBook 5

by Steve Ebersole (JIRA)

Convert Getting Started Guide to use DocBook 5 ---------------------------------------------- Key: HHH-5525 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5525 Project: Hibernate Core Issue Type: Task Components: documentation Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6.0.CR1 This may require work on jDocBook to support, not sure. For sure we will need a docbook 5 bundle for maven respoitory -- 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

14 years, 5 months

2
13
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-571) MassIndexer eats lock Exception

by Marc Schipperheyn (JIRA)

MassIndexer eats lock Exception ------------------------------- Key: HSEARCH-571 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-571 Project: Hibernate Search Issue Type: Improvement Components: engine Affects Versions: 3.2.1 Reporter: Marc Schipperheyn MassIndexer eats Lock exceptions and reports in stead: org.hibernate.search.SearchException: Unable to open IndexWriter -- 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

14 years, 5 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3410) @OneToMany forces unique key in @JoinTable when inverseJoinColumns = @JoinColumn(unique=false)

by Kamil Morong (JIRA)

@OneToMany forces unique key in @JoinTable when inverseJoinColumns = @JoinColumn(unique=false) ---------------------------------------------------------------------------------------------- Key: HHH-3410 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3410 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Environment: MySQL 5.0.51b, Hibernate Core 3.2.6 GA, Hibernate Annotations 3.3.1 GA Reporter: Kamil Morong Hi, I need to have this class composition with one to many relation: @Entity @Table(name="USER") public class User implements java.io.Serializable { private Long id; private String username; private String password; private Set<Role> roles = new LinkedHashSet<Role>(); public User() { } @Id @GeneratedValue(strategy = GenerationType.AUTO) @Column(name = "USER_ID") public Long getId() { return id; } public void setId(Long id) { this.id = id; } @Column(name="USERNAME", nullable=false, unique=true) public String getUsername() { return username; } public void setUsername(String userName) { this.username = userName; } @Column(name="PASSWORD", nullable=false) public String getPassword() { return password; } public void setPassword(String password) { this.password = password; } @CollectionOfElements @OneToMany(cascade={CascadeType.PERSIST, CascadeType.MERGE}) @JoinTable(name = "USER_ROLE", joinColumns = @JoinColumn(name = "USER_ID", unique=false), inverseJoinColumns = @JoinColumn(name = "ROLE_ID", unique=false)) @Cascade(org.hibernate.annotations.CascadeType.SAVE_UPDATE) @LazyCollection(LazyCollectionOption.FALSE) public Set<Role> getRoles() { return roles; } public void setRoles(Set<Role> roles) { this.roles = roles; } } @Entity @Table(name="ROLE") public class Role implements java.io.Serializable { private Long id; private String name; public Role() { } @Id @GeneratedValue(strategy = GenerationType.AUTO) @Column(name = "ROLE_ID") public Long getId() { return id; } public void setId(Long id) { this.id = id; } @Column(name="NAME", nullable=false, unique=true) public String getName() { return name; } public void setName(String name) { this.name = name; } } This will create db tables like SQL script CREATE TABLE `user` ( `USER_ID` BIGINT(20) NOT NULL AUTO_INCREMENT, `PASSWORD` VARCHAR(255) NOT NULL DEFAULT '', `USERNAME` VARCHAR(255) NOT NULL DEFAULT '', PRIMARY KEY (`USER_ID`), UNIQUE KEY `USERNAME` (`USERNAME`) ); CREATE TABLE `role` ( `ROLE_ID` BIGINT(20) NOT NULL AUTO_INCREMENT, `NAME` VARCHAR(255) NOT NULL DEFAULT '', PRIMARY KEY (`ROLE_ID`), UNIQUE KEY `NAME` (`NAME`) ); CREATE TABLE `user_role` ( `USER_ID` BIGINT(20) NOT NULL, `ROLE_ID` BIGINT(20) NOT NULL, PRIMARY KEY (`USER_ID`, `ROLE_ID`), UNIQUE KEY `ROLE_ID` (`ROLE_ID`), KEY `FKBC16F46A1174FFAB` (`ROLE_ID`), KEY `FKBC16F46AB69FC38B` (`USER_ID`), CONSTRAINT `FKBC16F46AB69FC38B` FOREIGN KEY (`USER_ID`) REFERENCES `user` (`USER_ID`), CONSTRAINT `FKBC16F46A1174FFAB` FOREIGN KEY (`ROLE_ID`) REFERENCES `role` (`ROLE_ID`) ); Tables USER and ROLE are right, but the join table USER_ROLE still have defined UNIQUE KEY `ROLE_ID` (`ROLE_ID`). This causes there cannot be one user with many roles. There must be some bug while generating database scheme. I am not able to remove unique key. -- 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

14 years, 6 months

7
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3716) Sybase - null values for columns mapped as "boolean" are persisted as 0 (zero) instead of NULL

by Gail Badner (JIRA)

Sybase - null values for columns mapped as "boolean" are persisted as 0 (zero) instead of NULL ---------------------------------------------------------------------------------------------- Key: HHH-3716 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3716 Project: Hibernate Core Issue Type: Bug Components: core Environment: Sybase Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.2.x, 3.3.x, 3.4 Null values for columns mapped as "boolean" are persisted as 0 (zero) instead of NULL. This happens because Hibernate persists a null Boolean value by calling: PreparedStatement.setNull( index, java.sql.Types.BIT ) The SQL code, java.sql.Types.BIT, is used because the Hibernate BooleanType defines its code as java.sql.Type.BIT. Sybase JDBC converts the null to 0, apparently because Sybase does not allow nullable bit columns. This can be reproduced using an annotations unit test, Java5FeaturesTest.testAutoboxing().. Sybase maps bit columns to tinyint, so when the unit test is executed, the column in the underlying table is actually of type tinyint, not bit. Sybase allows nullable tinyint columns, so there should be no problem persisting a null value as null. I've verified that changing the call to: PreparedStatement.setNull( index, java.sql.Types.TINYINT ) persists the null value without being converted to 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

14 years, 6 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5413) null values for columns mapped as "boolean" cause exception when saving entity with Sybase jdbc4

by Strong Liu (JIRA)

null values for columns mapped as "boolean" cause exception when saving entity with Sybase jdbc4 ------------------------------------------------------------------------------------------------ Key: HHH-5413 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5413 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0.Beta1, 3.5.4, 3.5.3 Environment: Sybase jdbc4 Reporter: Strong Liu ASE doesn't allow 'null' value for 'BIT' datatype; While performing insert operation using jconn3.jar it permit you to have 'null' value, this 'null' value is converted into bit 0 by jconn3 & hence ASE doesn't throw any exception; But incase of jconn4.jar 'null' value is not converted into bit 0, hence jconn4 directly reports an exception for 'null' value(which is the expected correct behavior) Hibernate persists a null Boolean value by calling: PreparedStatement.setNull( index, java.sql.Types.BIT ) The SQL code, java.sql.Types.BIT, is used because the Hibernate BooleanType defines its code as java.sql.Type.BIT. This can be reproduced using an annotations unit test, Java5FeaturesTest.testAutoboxing().. Sybase maps bit columns to tinyint, so when the unit test is executed, the column in the underlying table is actually of type tinyint, not bit. Sybase allows nullable tinyint columns, so there should be no problem persisting a null value as null. I've verified that changing the call to: PreparedStatement.setNull( index, java.sql.Types.TINYINT ) persists the null value without being converted to 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

14 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4452) Sybase ingroes the last byte when persis a byte [] with BinaryType and the last byte is 0

by strong liu (JIRA)

Sybase ingroes the last byte when persis a byte [] with BinaryType and the last byte is 0 ------------------------------------------------------------------------------------------ Key: HHH-4452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4452 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0.Beta-1 Environment: hibernate-core trunk + sybase ase 15 Reporter: strong liu this issue can be repro with org.hibernate.test.annotations.LobTest.testBinary(). and that test will throw an ArrayIndexOutOfBoundsException. but if we change metadata[1] = (byte) 0; to metadata[1] = (byte) 2; (something else except 0), then the test will pass. -- 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

14 years, 6 months

4
5
0 / 0

[Hibernate-JIRA] Created: (ANN-692) StringClobType doesn't work with Sybase ASA

by Paul Middelkoop (JIRA)

StringClobType doesn't work with Sybase ASA ------------------------------------------- Key: ANN-692 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-692 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Database: Adaptive Server Anywhere, version: 9.0.1.1753 JDBC: jConnect (TM) for JDBC(TM)/6.05(Build 26023) Reporter: Paul Middelkoop Sybase ASA doesn't support the CLOB datatype. However StringClobType works fine except when inserting a null value in the PreparedStatement. I fixed this by changing st.setNull(index, Types.CLOB) to st.setString(index, null). Maybe this can be added to the next release? -- 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

14 years, 6 months

5
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5612) Document the transaction manager to be used in GlassFish

by Sanne Grinovero (JIRA)

Document the transaction manager to be used in GlassFish -------------------------------------------------------- Key: HHH-5612 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5612 Project: Hibernate Core Issue Type: New Feature Components: documentation Reporter: Sanne Grinovero Fix For: 3.6.x As discussed on mailing list, several people get the transaction manager configuration wrong, and wen pointed to the documentation they can't find any reference to GlassFish. It appears that they should use SunONETransactionManagerLookup, I'd like to see this mentioned in the documentation, and maybe even subclassed to a new name to minimize any doubt. -- 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

14 years, 6 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HHH-5679) NPE in PutFromLoadValidator with JBC as a 2nd level cache

by Brian Stansberry (JIRA)

NPE in PutFromLoadValidator with JBC as a 2nd level cache --------------------------------------------------------- Key: HHH-5679 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5679 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.6.0, 3.5.6, 3.5.5 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.6.1, 3.x, 4.0.0.Alpha1 See HHH-5599 -- the same issue discussed there exists in the JBC 2LC integration; fix is the same as well. -- 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

14 years, 6 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 April 2011