June 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (EJB-288) Execute the EJB 3.0 callback on collection change

by Emmanuel Bernard (JIRA)

Execute the EJB 3.0 callback on collection change ------------------------------------------------- Key: EJB-288 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-288 Project: Hibernate Entity Manager Issue Type: Improvement Components: EntityManager Reporter: Emmanuel Bernard Today collection change does not trigger an event, but we it will, it makes sense to trigger the ejb 3 lifecycle (minus calling it twice??). -- 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, 8 months

2
7
0 / 0

[Hibernate-JIRA] Created: (ANN-754) hibernate annotation 3.4.0.CR1's pom.xml misses the slf4j dependency

by Sylvain Vieujot (JIRA)

hibernate annotation 3.4.0.CR1's pom.xml misses the slf4j dependency -------------------------------------------------------------------- Key: ANN-754 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-754 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.CR1 Reporter: Sylvain Vieujot The current pom only has the dependency to slf4j-api. It should have a dependency to the slf4j-log4j12. Adding <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <version>1.5.0</version> </dependency> fixes 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, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-1065) Named Query DAO methods with Primitive types fail to compile with JDK 1.4

by Joe Porcheddu (JIRA)

Named Query DAO methods with Primitive types fail to compile with JDK 1.4 ------------------------------------------------------------------------- Key: HBX-1065 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1065 Project: Hibernate Tools Issue Type: Bug Components: hbm2java Affects Versions: 3.2.0.GA Reporter: Joe Porcheddu Attachments: hbx469.zip This is the same issue as HBX-469, but I was asked to create a new case and attach my test case. Please see attached Eclipse/Maven project. The problem is that if a named query with a type of "java.lang.Long" or "java.lang.Integer" exists in an HBM file, then the Hbm2Dao task converts it to a primitive long. This causes the compile to fail if you are using JDK 1.4. For example: <query name="findBySomeLong"> <query-param name="someLong" type="java.lang.Long" /> from Hbx469 where someLong=:someLong </query> when run through hbm2dao generates the following code: public List findBySomeLong(long someLong) { Query query = sessionFactory.getCurrentSession() .getNamedQuery("Hbx469.findBySomeLong"); query.setParameter("someLong", someLong); return query.list(); } You will get a compile error on query.setParameter() when using JDK 1.4 because the java.lang.Long has been generated as a Java primitive long. -- 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, 9 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-198) Documentation out of sync with implemented/released features

by Hardy Ferentschik (JIRA)

Documentation out of sync with implemented/released features ------------------------------------------------------------ Key: HSEARCH-198 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-198 Project: Hibernate Search Issue Type: Bug Components: documentation, mapping Affects Versions: 3.0.1.GA Reporter: Hardy Ferentschik Fix For: 3.0.2.GA The online documentation of 3.0.1GA claims that the termVector parameter for the @Field annotation is already available, but the code and jar file shipped in 3.0.1GA does actually not support this feature yet. However, everything seems to be implemented on the trunk. It is just a question of a new release. Regarding the documentation - the 'Field.' part in the values for termVector has to be dropped. It should eg be @Field( index = Index.TOKENIZED, termVector = TermVector.YES ). TermVector is its own enum class. -- 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, 9 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HBX-1067) [SchemaExport] Duplicate unique constraint with unique="true" and natural-id

by Vincent Ricard (JIRA)

[SchemaExport] Duplicate unique constraint with unique="true" and natural-id ---------------------------------------------------------------------------- Key: HBX-1067 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1067 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2.0.GA Environment: Hibernate 3.2.5, MySQL 5.0.51 (InnoDB), Java 1.5 Reporter: Vincent Ricard Priority: Minor In my foo.hbm.xml, if i put this: <natural-id> <property name="barId" column="bar_id" not-null="true" length="128"/> </natural-id> SchemaExport creates this: create table foo (id bigint not null auto_increment, version integer not null, bar_id varchar(128) not null, primary key (id), unique (bar_id)) ENGINE=InnoDB; And MySQL creates only one index for bar_id. But, if my foo.hbm.xml contains this: <natural-id> <property name="barId" column="bar_id" not-null="true" unique="true" length="128"/> </natural-id> SchemaExport generates this: create table foo (id bigint not null auto_increment, version integer not null, bar_id varchar(128) not null unique, primary key (id), unique (bar_id)) ENGINE=InnoDB; And MySQL creates 2 indices for bar_id. So, i think it'd be cool if schemaexport was smarter (even if MySQL could be too). -- 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, 9 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-209) merge FullTextIndexCollectionEventListener into FullTextIndexEventListener

by Sanne Grinovero (JIRA)

merge FullTextIndexCollectionEventListener into FullTextIndexEventListener -------------------------------------------------------------------------- Key: HSEARCH-209 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-209 Project: Hibernate Search Issue Type: Task Components: engine Reporter: Sanne Grinovero Fix For: 3.1.0 FullTextIndexCollectionEventListener contains: " FIXME deprecate as soon as we target Core 3.3 and merge back into the superclass" I suppose it should be done for 3.1 as we are targeting core 3.3 -- 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, 9 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-174) Improve transparent filter caching by wrapping filters into our own CachingWrapperFilter

by Emmanuel Bernard (JIRA)

Improve transparent filter caching by wrapping filters into our own CachingWrapperFilter ---------------------------------------------------------------------------------------- Key: HSEARCH-174 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-174 Project: Hibernate Search Issue Type: Improvement Components: engine Reporter: Emmanuel Bernard Fix For: 3.1.0 See http://forum.hibernate.org/viewtopic.php?t=984107&highlight=filter+cache -- 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, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-212) Added a new very efficient ReaderProvider

by Sanne Grinovero (JIRA)

Added a new very efficient ReaderProvider ----------------------------------------- Key: HSEARCH-212 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-212 Project: Hibernate Search Issue Type: Improvement Components: directory provider Reporter: Sanne Grinovero Assignee: Sanne Grinovero Creating a new ReaderProvider, it should be faster and more scalable compared to the current ones. Here are some numbers on a little 9MB index; it should improve on bigger indexes: (SharingBufferReaderProvider is the name it had during tests) using 100 threads: Performance test for org.hibernate.search.reader.SharingBufferReaderProvider: 34735ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for org.hibernate.search.reader.SharingBufferReaderProvider: 34396ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for org.hibernate.search.reader.SharingBufferReaderProvider: 37347ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for org.hibernate.search.reader.SharingBufferReaderProvider: 36895ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for org.hibernate.search.reader.SharingBufferReaderProvider: 36100ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for shared: 42433ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for shared: 44830ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for shared: 40704ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for shared: 43685ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for not-shared: 50452ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for not-shared: 48171ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for not-shared: 52862ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for not-shared: 49999ms. (20000 searches, 1000 insertions, 2000 updates) 20 Threads: Performance test for org.hibernate.search.reader.SharingBufferReaderProvider: 31133ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for org.hibernate.search.reader.SharingBufferReaderProvider: 31408ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for shared: 38170ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for shared: 36327ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for not-shared: 41712ms. (20000 searches, 1000 insertions, 2000 updates) Performance test for not-shared: 42224ms. (20000 searches, 1000 insertions, 2000 updates) -- 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, 9 months

2
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-157) Make explicit in FAQ and doc that query.list() followed by query.getResultSize() triggers only one query

by Emmanuel Bernard (JIRA)

Make explicit in FAQ and doc that query.list() followed by query.getResultSize() triggers only one query -------------------------------------------------------------------------------------------------------- Key: HSEARCH-157 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-157 Project: Hibernate Search Issue Type: Improvement Components: documentation Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.0.2.GA, 3.1.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

17 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-164) Class built-in bridge

by Emmanuel Bernard (JIRA)

Class built-in bridge --------------------- Key: HSEARCH-164 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-164 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.1.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

17 years, 9 months

1
2
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 June 2008