April 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-715) EntityBinder rarely reveals offending class name

by Paul Benedict (JIRA)

EntityBinder rarely reveals offending class name ------------------------------------------------ Key: ANN-715 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-715 Project: Hibernate Annotations Issue Type: Improvement Components: binder Affects Versions: 3.3.1.GA Reporter: Paul Benedict When AnnotationException is thrown, the code rarely ever includes the class name of the offending entity. The developer (such as I) has to go through a lot of guess work to determine which class has the problem. -- 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, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (ANN-711) Maven pom.xml of annotations 3.3.1.GA depends on hibernate-commons-annotations 3.0.0.ga instead of 3.3.0.ga

by Geoffrey De Smet (JIRA)

Maven pom.xml of annotations 3.3.1.GA depends on hibernate-commons-annotations 3.0.0.ga instead of 3.3.0.ga ----------------------------------------------------------------------------------------------------------- Key: ANN-711 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-711 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA Reporter: Geoffrey De Smet I could be wrong, but it looks very strange to me that the latest hibernate annotations 3.3.1.GA doesn't depend on the latest hibernate-commons-annotations 3.3.0.ga. <project ...> <modelVersion>4.0.0</modelVersion> <groupId>org.hibernate</groupId> <artifactId>hibernate-annotations</artifactId> <packaging>jar</packaging> <version>3.3.1.GA</version> ... <dependencies> ... <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-commons-annotations</artifactId> <version>3.0.0.ga</version> </dependency> ... </dependencies> </project> If it is intended, please add a note in the pom.xml: <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-commons-annotations</artifactId> <version>3.0.0.ga</version>  </dependency> The same issue occurs for hibernate-entitymanager. Also, it's confusing to use "...ga" and "...GA" with a different case-sensitivity in the version number. -- 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, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-724) @Size(min) fails in PostLoad

by Albert Gorski (JIRA)

@Size(min) fails in PostLoad ---------------------------- Key: ANN-724 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-724 Project: Hibernate Annotations Issue Type: Bug Components: validator Affects Versions: 3.3.0.ga Environment: hibernate 3.2.6.ga, hibernate-annotations 3.3.1.ga, hibernate-commons-annotations 3.0.0.ga, hibernate-entitymanager 3.3.1.ga, hibernate-validator 3.0.0.ga Linux (PClinuxOS), MySQL 5.x Reporter: Albert Gorski I've standard parent-child mapping. In parent I set validation for the childList list for minimum 1 and maximum 4 (max is not a problem) I create then a Parent and add Child to childCollection (one child added). When I call validation new ClassValidator<Person>(Person.class).getInvalidValues(myPerson); I see no exception/message - all is fine. The problem appears when I call entityManager.merge(myPerson) - there is an information that minimum child number is 1. I think it is a problem in PostLoad -> Parent entity is persisted and validated in PostLoad. Child entries are not yet persisted and it leads to exception. Is it possible to disable automatic validation in PostLoad or general when I want to validate manually? Is there any way around? Parent-children classes: @Entity @Table(name = "parent") public class Parent { @Id @GeneratedValue(strategy = GenerationType.AUTO) private Long id; @OneToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY, mappedBy ="parent") @Fetch(value = FetchMode.SUBSELECT) @OptimisticLock(excluded = true) @Size(min = 1, max = 4) private List<Child> childList = new java.util.Vector<Child>(4, 1); } @Entity @Table(name = "child") public class Child extends AbstractEntity { /** Serial UID. */ private static final long serialVersionUID = 1L; @Id @GeneratedValue(strategy = GenerationType.AUTO) private Long id; @ManyToOne(fetch = FetchType.LAZY) @NotNull private Parent parent; } -- 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, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-726) IncrementGenerator ignores catalog/schema of @Table annotation in domain object

by Michael Thiele (JIRA)

IncrementGenerator ignores catalog/schema of @Table annotation in domain object ------------------------------------------------------------------------------- Key: ANN-726 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-726 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA, 3.3.1.CR1 Environment: Hibernate 3.2.6.GA, Sybase ASE Reporter: Michael Thiele The Generator only uses the default schema and catalog, if set. It ignores the schema and catalog set in the @Table annotation in the domain class: example: default schema set in hibernate.cfg.xml: <property name="default_schema">someDefaultSchema</property> schema and catalog set in domain object: @Table(name = "someTable", catalog = "someCatalog", schema = "someOtherSchema") SQL statement executet: select max(someId) from someDefaultSchema.someTable catolog is missing in statement, schema is someDefaultSchema instead of someOtherSchema. -- 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, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-727) AccessType not being inherited correctly when using @CollectionOfElements

by Kenny MacLeod (JIRA)

AccessType not being inherited correctly when using @CollectionOfElements ------------------------------------------------------------------------- Key: ANN-727 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-727 Project: Hibernate Annotations Issue Type: Bug Components: binder Reporter: Kenny MacLeod Priority: Minor Attachments: BugTestCase.java See attached test case. To summarise, I have two @Entity classes, one of which contains a single @Embeddable ComponentA, the other of which contains a @CollectionOfElements of ComponentA. ComponentA in turn contains an instance of the @Embeddable ComponentB. Both @Entity classes have the @Id on an instance field, so I understand that means that all embedded components should inherit that access type. The test works fine for the @Entity which contains the single instance of ComponentA, but fails with an exception with the @Entity which contains the @CollectionOfElements. For some reason, the access type behaviour is lost when it gets to ComponentB - but only when I use @CollectionOfElements. If I explicitly annotate ComponentB with @AccessType("field"), it works fine - but I shouldn't have to. -- 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, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (ANN-734) Character Set.

by lukesh shirkey (JIRA)

Character Set. -------------- Key: ANN-734 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-734 Project: Hibernate Annotations Issue Type: Task Environment: Hibernate3 and Hibernate Annotation Reporter: lukesh shirkey I am using Oracle 10g, in this few column contains "€" characters, and when i fetch data using hibernate annotation "€" disappears. In hiberante can can we change the Character Set to UTF-8 -- 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, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-484) Do not filter classes on queries when we know that Directory <-> Entity is a one to one relationship

by Emmanuel Bernard (JIRA)

Do not filter classes on queries when we know that Directory <-> Entity is a one to one relationship ---------------------------------------------------------------------------------------------------- Key: ANN-484 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-484 Project: Hibernate Annotations Type: Improvement Components: lucene Reporter: Emmanuel Bernard Priority: Minor -- 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, 1 month

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3243) VARBINARY primary key with mysql doesn't function

by Marc Ewert (JIRA)

VARBINARY primary key with mysql doesn't function ------------------------------------------------- Key: HHH-3243 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3243 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.1 Environment: MySQL-5.0.51a, hibernate-3.2.1.ga Reporter: Marc Ewert We have a 16-byte UUID type, which should be persisted in a VARBINARY (tinyblob) in a mysql database. But the primary key statement is invalid for mysql: ERROR 11:34:13 [main] (SchemaExport.java:create:274) - Unsuccessful: create table T_GRI_USER (C_ID tinyblob not null, C_ATTRIBUTES text, C_VERSION integer, C_PASSWORD varchar(255), C_VISIBILITIES blob, C_STATE integer not null, C_LOGIN varchar(255) not null unique, C_EMAIL varchar(255), primary key (C_ID)) ERROR 11:34:13 [main] (SchemaExport.java:create:275) - BLOB/TEXT column 'C_ID' used in key specification without a key length The statement should end with ... primary key (C_ID({length})). This has to be done in the class PrimaryKey, which forms this part of the statement without involving the Dialect. The MySQLDialect has also a little bug, it doesn't write the length while defining the tinyblob column. But unfortunately this doesn't solve the SQL-Error. Unfortunately because the dialect is much better patchable for us as the PrimaryKey class deep in hibernate is... -- 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, 1 month

1
2
0 / 0

[Hibernate-JIRA] Created: (HV-48) There is no DefaultValidatorMessage_en leading to no message loaded when locale is explicit and the system default is not en

by Emmanuel Bernard (JIRA)

There is no DefaultValidatorMessage_en leading to no message loaded when locale is explicit and the system default is not en ---------------------------------------------------------------------------------------------------------------------------- Key: HV-48 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-48 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 3.0.0.ga Reporter: Emmanuel Bernard Fix For: 3.0.1 -- 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, 1 month

1
2
0 / 0

[Hibernate-JIRA] Created: (HV-36) DefaultValidatorMessages_ja.properties

by WATANABE Takashi (JIRA)

DefaultValidatorMessages_ja.properties -------------------------------------- Key: HV-36 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-36 Project: Hibernate Validator Issue Type: Patch Reporter: WATANABE Takashi Priority: Trivial Attachments: 20070705_2145.patch.txt, 20070705_2145.sample.DefaultValidatorMessages_ja.png http://anonsvn.jboss.org/repos/hibernate/trunk/HibernateExt/validator/src... I'm not a professional translator, and turned to translators of the JJBug(Japan JBoss User Group; www.jbug.jp). http://lists.sourceforge.jp/mailman/archives/japan-jbug-translators/2007-... Mr. Kimura gave me some good advice there, and (I believe) I managed to translate it into Japanese that is not only straightforward, but also respectful of the original text. I assumed the messages of assertFalse, assertTrue, notNull, notEmpty, and pattern were meant for programmers rather than end users because of the existence of words such as "assertion", "null", and "regex(and match)". I hope that's useful. -- 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, 1 month

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2008