May 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

17 years, 10 months

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

17 years, 10 months

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

17 years, 10 months

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

17 years, 10 months

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

17 years, 10 months

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

17 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-740) Fail fast when a pojo is marked with @org.hibernate.annotations.Entity instead of @javax.persistence.Entity and is <class> in persistence.xml

by Geoffrey De Smet (JIRA)

Fail fast when a pojo is marked with @org.hibernate.annotations.Entity instead of @javax.persistence.Entity and is <class> in persistence.xml --------------------------------------------------------------------------------------------------------------------------------------------- Key: ANN-740 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-740 Project: Hibernate Annotations Issue Type: Improvement Components: binder Affects Versions: 3.3.1.GA Reporter: Geoffrey De Smet Priority: Minor When a pojo is annotatedwith @org.hibernate.annotations.Entity, but not with @javax.persistence.Entity and it's in the persistence.xml as such: <class>me.MyPojo</class> <exclude-unlisted-classes>true</exclude-unlisted-classes> it shouldn't quietly ignore that MyPojo class, but instead fail fast with an exception "Class me.MyPojo is defined in persistence.xml but isn't an @javax.persistence.Entity". I just started with Seam and JBoss AS and I made that mistake and it took me a couple of days to track this down (I know, it looks so simple and so obvious)... because I always figured JBoss classloading was to blame (while it wasn't). It's actually one of the reasons I threw JBoss AS out and started using Jetty and Tomcat (which is working fine now). -- 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, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-745) @Where annotation is not processed with "Extra-lazy" loading

by Gregory Klimov (JIRA)

@Where annotation is not processed with "Extra-lazy" loading ------------------------------------------------------------ Key: ANN-745 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-745 Project: Hibernate Annotations Issue Type: Bug Reporter: Gregory Klimov Priority: Minor Consider code: public class Transaction { ... @OneToMany @Fetch(FetchMode.SUBSELECT) @LazyCollection(LazyCollectionOption.EXTRA) @Where(clause = "entity=4") @JoinColumn(name = "entity_id") private List<Alert> alerts; ... } public class Alert { ... @Any(metaColumn = @Column(name = "entity"), fetch = FetchType.LAZY) @AnyMetaDef( idType = "long", metaType = "integer", metaValues = { @MetaValue(value = "4", targetEntity = Document.class), @MetaValue(value = "9", targetEntity = Transaction.class)}) @JoinColumn(name = "entity_id", insertable = false, updatable = false) private Object relatedObject; ... } produces wrong SQL on size retrieval operation: select count(id) from alerts where entity_id =? -- 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, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-204) Improper calls to Session during a projection not involving THIS

by Emmanuel Bernard (JIRA)

Improper calls to Session during a projection not involving THIS ---------------------------------------------------------------- Key: HSEARCH-204 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-204 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.0.1.GA Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Priority: Critical Fix For: 3.1.0 This creates a x2 overhead on simple perf tests like HSEARCH-194 -- 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, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-203) Counter of index modification operations not always incremented

by Sanne Grinovero (JIRA)

Counter of index modification operations not always incremented --------------------------------------------------------------- Key: HSEARCH-203 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-203 Project: Hibernate Search Issue Type: Bug Components: optimizer Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Trivial Fix For: 3.1.0 It could happen some operation on the index would'nt increment the "operations" counter, delaying optimization. -- 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, 10 months

1
1
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 May 2008