January 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2034) Potential ClassCastException in catch block in NullableType

by Galen Palmer (JIRA)

Potential ClassCastException in catch block in NullableType ----------------------------------------------------------- Key: HHH-2034 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2034 Project: Hibernate3 Type: Improvement Components: core Versions: 3.1.3 Environment: Hibernate 3.1.3 Reporter: Galen Palmer Priority: Minor It is possible to throw an exception from within the catch block of NullableType.nullSafeSet() since the toString(value) method calls in many cases (e.g. StringType) simply result in a cast of return (String)value. This may mask the underlying problem for the users. A proposed solution would be to replace the call in the catch blog of toString(value) with a reference to value. For example: line 87: log().info( "could not bind value '" + value + "' to parameter: " + index + "; " + re.getMessage() ); and line 91: log().info( "could not bind value '" + value + "' to parameter: " + index + "; " + se.getMessage() ); This change would prevent the catch block from throwing the exception. -- 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, 3 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HB-1566) LICENSE VIOLATION: Japanese font files for PDF reference documentation

by Takayoshi Kimura (JIRA)

LICENSE VIOLATION: Japanese font files for PDF reference documentation ----------------------------------------------------------------------- Key: HB-1566 URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-1566 Project: Hibernate2 Type: Task Reporter: Takayoshi Kimura Priority: Critical Attachments: userconfig.xml.patch There are two font files, msgothic.ttf and msmincho.ttf are committed in Hibernate CVS for Japanese PDF reference documentation. Those font files are part of Microsoft Windows. We cannot use those files for the PDF. The PDF file is: http://www.hibernate.org/hib_docs/reference/ja/pdf/hibernate_reference.pdf (149pages) The following instructions are to use sazanami font instead of Microsoft one. Sazanami font is free, you can download sazanami font via http://sourceforge.jp/projects/efont/ . This is sample PDF file that uses sazanami font: http://jbento.sourceforge.net/tmp/hibernate/hibernate_reference-sazanami.pdf (154pages) 1). Download sazanami font I put hibernate-sazanami.zip on my sourceforge project site: http://jbento.sourceforge.net/tmp/hibernate/hibernate-sazanami.zip (10MB) The zipped file includes: $ unzip -t hibernate-sazanami.zip Archive: hibernate-sazanami.zip testing: sazanami-gothic.ttf OK testing: sazanami-gothic.xml OK testing: sazanami-mincho.ttf OK testing: sazanami-mincho.xml OK No errors detected in compressed data of hibernate-sazanami.zip. Those files based on sazanami-20040629 (newest one) . 2). Change to use sazanami font $ cd /path/to/Hibernate2/ $ patch -p0 < userconfig.xml.patch $ cd doc/reference/ja/fop/ $ unzip /path/to/hibernate-sazanami.zip 3). Run ant to generate new PDF file $ cd /path/to/Hibernate2/ $ ant refdoc 4). Commit changes $ cd /path/to/Hibernate2/doc/reference/ja/fop/ $ cvs rm -f ms*.ttf ms*.xml $ cvs add sazanami-*.xml $ cvs add -kb sazanami-*.ttf $ cvs commit 5). Update PDF file on Hibernate site I don't know about this step. -- 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, 3 months

5
19
0 / 0

[Hibernate-JIRA] Created: (ANN-519) Introduce a worker factory and its configuration

by Emmanuel Bernard (JIRA)

Introduce a worker factory and its configuration ------------------------------------------------ Key: ANN-519 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-519 Project: Hibernate Annotations Type: New Feature Components: search 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

17 years, 3 months

1
2
0 / 0

[Hibernate-JIRA] Created: (ANN-523) JMS Worker: send Hibernate Search updates through JMS

by Emmanuel Bernard (JIRA)

JMS Worker: send Hibernate Search updates through JMS ----------------------------------------------------- Key: ANN-523 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-523 Project: Hibernate Annotations Type: New Feature Components: search Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Fix For: 3.2.2 -- 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, 3 months

1
2
0 / 0

[Hibernate-JIRA] Created: (ANN-531) EntityMode.DOM4J does not deserialize collection entities

by Laurent Perez (JIRA)

EntityMode.DOM4J does not deserialize collection entities --------------------------------------------------------- Key: ANN-531 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-531 Project: Hibernate Annotations Type: Bug Components: binder Versions: 3.2.2 Environment: PATCH ANN-517 APPLIED (see http://opensource.atlassian.com/projects/hibernate/browse/ANN-517), revision 11026. Reporter: Laurent Perez The XML deserialization of an entity does not deserializes its child properties but only its id, following sample : Foobean are children of a Screen : @Entity @Table (name="foobean") public class Foobean implements java.io.Serializable { private String name; private String age; private Screen screen; @Id @Column(name="name") public String getName() { return name; } public void setName(String name) { this.name = name; } @ManyToOne public Screen getScreen() { return this.screen; } public void setScreen(Screen screen) { this.screen = screen; } @Column(name="age") public String getAge() { return age; } public void setAge(String age) { this.age = age; } } Relevant parent Screen annotations : private Set<Foobean> fooBeans = new HashSet<Foobean>(); @OneToMany(cascade=CascadeType.ALL, fetch=FetchType.EAGER) public Set<Foobean> getFoobeans(){ return this.fooBeans; } public void setFoobeans(Set<Foobean> fooBeans) { this.fooBeans = fooBeans; } Association : Foobean foobean = new Foobean(); foobean.setName("foo"); foobean.setAge("age"); foobean.setScreen(screen); screen.getFoobeans().add(foobean); Generated XML (the age property of Foobean is missing, i.e there is no <name>foo</name><age>age</age>) : <Screen> <id>1</id> <foobeans> <Foobean>foo</Foobean> </foobeans> </Screen> -- 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, 3 months

3
7
0 / 0

[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, 3 months

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, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2376) Query with fully qualified entity class fails

by Neukomm (JIRA)

Query with fully qualified entity class fails --------------------------------------------- Key: HHH-2376 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2376 Project: Hibernate3 Type: Bug Components: query-hql Versions: 3.2.1 Environment: Hibernate 3.2.1ga, HSQLDB 1.8.0.4 Reporter: Neukomm Attachments: DiscriminatorTest2.java We've recently ran into a problem while migrating from Hibernate 3.1.1 to Hibernate 3.2.1ga: While queries against the class attribute still work, if the class is non-qualified, the query fails if the name is fully qualified. e.g. "from Person p where p.class = Person" works fine while "from Person p where p.class = org.hibernate.test.discriminator.Person" fails. I've attached a test case to illustrated the problem. It should work when it's put into the 'discriminator' package of the hibernate junit test cases. Both testcases work fine for hibernate versions up to and including 3.2.0cr2. In later versions, specifically in 3.2.1ga, the test case that uses the fully qualified class name ('testQueryWithPackage') fails. -- 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, 3 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2398) Have hi/lo strategies use delegation rather than inheritence

by Steve Ebersole (JIRA)

Have hi/lo strategies use delegation rather than inheritence ------------------------------------------------------------ Key: HHH-2398 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2398 Project: Hibernate3 Type: Improvement Reporter: Steve Ebersole Allows: 1) simplier reusability 2) simplier testability -- 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, 3 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2340) Entity second level cache put operations should either fail silently or provider to retry

by Galder Zamarreno (JIRA)

Entity second level cache put operations should either fail silently or provider to retry ----------------------------------------------------------------------------------------- Key: HHH-2340 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2340 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.1 Reporter: Galder Zamarreno Using JBossCache as second level cache and optimistic locking, rollbacks can still happen in systems under load as concurrent transactions could be modifying data in the cache. Hibernate clients could retry the update, but it's probably better if either, a similar silent failover mechanism was used for entity cache, or alternatively, Hibernate to attempt a retry. -- 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, 4 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2007