January 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HV-410) Clarify the license on both the website and the reference documentation

by Emmanuel Bernard (JIRA)

Clarify the license on both the website and the reference documentation ----------------------------------------------------------------------- Key: HV-410 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-410 Project: Hibernate Validator Issue Type: Improvement Reporter: Emmanuel Bernard Fix For: 4.2.0.Beta1 I've talked to a few people confused by the lack of information on the license we use for Hibernate Validator as well as the Bean Validation API and TCK. We should make it clearer on the web site. -- 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

13 years, 11 months

2
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-1123) Cannot put more than 1000 elements in a InExpression

by Siddharth Shankar (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1123?page=c... ] Siddharth Shankar commented on HHH-1123: ---------------------------------------- Hi, Any idea as to when the fix would be incorporated into hibernate and made available for the users? > Cannot put more than 1000 elements in a InExpression > ---------------------------------------------------- > > Key: HHH-1123 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1123 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Affects Versions: 3.1 rc2, 3.2.0.alpha1 > Environment: Oracle 9i > Reporter: Alexis Seigneurin > Assignee: Strong Liu > Attachments: Animal.hbm.xml, hibernate-inexpression-oracle-3.2.patch, LongInElementsTest.java, patch.txt > > Original Estimate: 1h > Remaining Estimate: 1h > > The number of elements that we can put in a "in" expression is limited to a certain amount (1000 for Oracle, for instance). When creating a criteria query, the org.hibernate.criterion.InExpression class should split the expression into several smaller ones. > Attached is a patch which splits the expression by slices of 500 elements. For example, if we have 1001 elements to put in the "in" expression, the result would be : > (entity.field in (?, ?, ?...) or entity.field in (?, ?, ?...) or entity.field in (?)) > The surrounding parantheses are useful to avoid problems with other conditions (a "and" condition taking over the one of the "or" conditions). -- 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

13 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-4413) Support interface inheritance mapping

by Tristan ROBET (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4413?page=c... ] Tristan ROBET commented on HHH-4413: ------------------------------------ Hi all, 6 years later, this request has not been fullfilled and is not part of Hibernate Annotations. Is it really an "Improvement" ? I would call it a bug, because as far as I know, annotations are nowadays supposed to be a "standard" replacement for Hibernate mapping files. I would like to implement the "Payment" example which can be found in Hibernate documentation using a "Payment" interface and annotations, but I can't : http://docs.jboss.org/hibernate/core/3.3/reference/en/html/inheritance.html > Support interface inheritance mapping > ------------------------------------- > > Key: HHH-4413 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4413 > Project: Hibernate Core > Issue Type: Improvement > Components: annotations > Reporter: Steve Ebersole > Attachments: hibernate3-annotations-3.1beta5-3896-3948.diff, hibernate3-annotations-3.1beta5-3896-4138.diff > > > It should be possible to create a mapping with interfaces, as described by the documentation here: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#inheritanc... > Specifically right now it is impossible to annotate interfaces and according to HBX-231 even if you could @Entity is only meant to get used on classes so the question becomes "what do you annotate it with?" > As I pointed out here http://forum.hibernate.org/viewtopic.php?p=2238824#2238824 the additional problem seems to be that XDoclet doesn't support interface annotation either (http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1345) so I'm left without a workaround. > I can't convert the interfaces to abstract classes because I implement multiple interfaces in my application and Java does not do multiple inheritance. > If you know of a nice workaround, please let me know :) -- 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

13 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (BVTCK-19) Move license text to license.txt

by Emmanuel Bernard (JIRA)

Move license text to license.txt -------------------------------- Key: BVTCK-19 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVTCK-19 Project: Bean Validation TCK Issue Type: Improvement Affects Versions: 1.0.5.Beta1 Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 1.0.5.GA -- 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

13 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4887) @IdClass on derived entity fails when derived entity is persisted before the associated entity

by Emmanuel Bernard (JIRA)

@IdClass on derived entity fails when derived entity is persisted before the associated entity ---------------------------------------------------------------------------------------------- Key: HHH-4887 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4887 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-4 Reporter: Emmanuel Bernard -- 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

13 years, 11 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5835) Error/Bug getting PluralAttribute on SessionFactoyImpl using @Inheritance and @MappedSuperclass

by Francisco Philip (JIRA)

Error/Bug getting PluralAttribute on SessionFactoyImpl using @Inheritance and @MappedSuperclass ----------------------------------------------------------------------------------------------- Key: HHH-5835 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5835 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.5 Environment: testcase java6-sun Reporter: Francisco Philip Hi, I'm looking an attribute by name root.get("nameOfCollection"), but i think that we have a limitation or bug because if the entity inheritance of this collection they don't resolve correctly the name of "role" to call a getCollectionPersister method of SessionFactory. Example {noformat} @MappedSuperclass @Inheritance(strategy = InheritanceType.SINGLE_TABLE) @DiscriminatorColumn( name = "dtype") class c{ @CollectionOfElements private Collection<EmbeddedEntity> nameOfCollection; .... } @Entity EntityA extends AbstractEntity{ } @Entity EntityB extends AbstractEntity{ @CollectionOfElements private Collection<EmbeddedEntity> nameOfCollection2; } {noformat} if I call root.get("nameOfCollection") of they cant find it because de variable role is resolved as "AbstractEntity.nameOfCollection", meantime the collectionPersisters have stored EntityA.nameOfCollection, EntityB.nameOfCollection and EntityB.nameOfCollection2 this is a bug? SessionFactoryImpl.java {noformat} public CollectionPersister getCollectionPersister(String role) throws MappingException { CollectionPersister result = (CollectionPersister) collectionPersisters.get(role); if (result==null) { throw new MappingException( "Unknown collection role: " + role ); } return result; } {noformat} AbstractManagedType.java {noformat} @SuppressWarnings({ "unchecked" }) public Attribute<? super X, ?> getAttribute(String name) { Attribute<? super X, ?> attribute = declaredAttributes.get( name ); if ( attribute == null && getSupertype() != null ) { attribute = getSupertype().getAttribute( name ); } return attribute; } {noformat} -- 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

13 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5390) Index column on inverse List should throw a warning

by Chris Bredesen (JIRA)

Index column on inverse List should throw a warning --------------------------------------------------- Key: HHH-5390 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5390 Project: Hibernate Core Issue Type: Improvement Components: annotations Affects Versions: 3.5.3 Reporter: Chris Bredesen The manual correctly warns against trying to map an indexed inverse collection on a List. However, a configuration containing this invalid mapping builds successfully but causes null values to be inserted for the index column. Hibernate should be helpful and, if possible, throw a warning to the user (perhaps an error?) that explains the invalid combination. Here is an example that would run but produce invalid results: @Entity public class Parent { @OneToMany(mappedBy="parent") @OrderColumn(name="order") private List<Child> children; } @Entity public class Child { @ManyToOne private Parent parent; } The above is a typical one to many with the addition of @OrderColumn. Because Child owns the relationship, the index column is lost/ignored. Hibernate should warn about this. -- 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

13 years, 11 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5834) Example shows an indexed collection configured with 'mappedBy=...'

by Gail Badner (JIRA)

Example shows an indexed collection configured with 'mappedBy=...' ------------------------------------------------------------------ Key: HHH-5834 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5834 Project: Hibernate Core Issue Type: Bug Components: documentation Affects Versions: 3.6.0 Reporter: Gail Badner Fix For: 3.6.1, 4.0.0.Alpha1 The Hibernate documentation http://docs.jboss.org/hibernate/core/3.6/reference/en-US/html/collections... shows an example of an indexed collection incorrectly configured with "mappedBy=...". -- 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

13 years, 12 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5028) Calling em.remove() on child object @OneToMany relationship when CascadeType.ALL and FetchType.EAGER are set throws exception

by Jesse Hutton (JIRA)

Calling em.remove() on child object @OneToMany relationship when CascadeType.ALL and FetchType.EAGER are set throws exception ----------------------------------------------------------------------------------------------------------------------------- Key: HHH-5028 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5028 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-CR-2 Environment: Confirmed bug using MySQL, PostgreSQL, and Hsqldb, which is what the test is configured with. Hibernate version is 3.5.0-CR-2 (see test app pom.xml) Reporter: Jesse Hutton Attachments: HibernateManyToOneEagerRemove.tar.gz Calling em.remove(foo) on the child object of a @OneToMany relationship that is defined with CascadeType.ALL and FetchType.EAGER throws an Exception. The cause is given as: javax.persistence.EntityNotFoundException: deleted entity passed to persist: And all I'm doing in the test is removing an object. See attached test case. If, however, I remove FetchType.EAGER from the @OneToMany relationship, no exception is thrown. -- 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

13 years, 12 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-5311) + operator in JPQL subselect query results in NullPointerException

by Grzegorz Olędzki (JIRA)

+ operator in JPQL subselect query results in NullPointerException ------------------------------------------------------------------ Key: HHH-5311 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5311 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.0-Final Environment: hibernate-3.5.0-Final.jar, java version "1.6.0_17", database platform seems irrelevant (H2 and MySQL tested) Reporter: Grzegorz Olędzki When trying to use a {{+}} arithmetic operator in a subquery of my JPQL query I end up with a NullPointerException from {{org.hibernate.hql.ast.HqlSqlWalker}}. I've played with adding/removing parentheses, aliases, but that doesn't seem to help. -- 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

13 years, 12 months

2
9
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2011