May 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4042) StatelessSession does not flush when using jdbc batch_size > 1

by Gael Beaudoin (JIRA)

StatelessSession does not flush when using jdbc batch_size > 1 -------------------------------------------------------------- Key: HHH-4042 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4042 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: JBoss 4.2.3, Linux, java 1.6, hibernate 3.3.1, entityManager 3.4.0, jboss seam 2.1.2, postgresql 8.3 Reporter: Gael Beaudoin I'm using a StetelessSession to insert millions of rows : it works great and without using much memory. But I've just seen that with a jdbc batch size of 50 for example (<property name="hibernate.jdbc.batch_size" value="0"/> in my persistence.xml) the last round of inserts aren't flushed to the database. For example, with 70 insert, only the first 50 are sent to the database. I've searched a lot about this issues and on this thread (https://forum.hibernate.org/viewtopic.php?f=1&t=987882&start=0), the only solution found is to set the batch_size to 1, which is really a shame. I've tried to flush the session, close the jdbc connection, etc etc ... no luck. I'd be fine with a way to set the batch_size to 1 only for this method, pro grammatically, but I've not found any way to do that. If you don't pay attention, it's a easy way to lose data. -- 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

15 years, 9 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HV-327) Update TCK runner dependecies to not depend on the JBoss deprecated repo

by Hardy Ferentschik (JIRA)

Update TCK runner dependecies to not depend on the JBoss deprecated repo ------------------------------------------------------------------------ Key: HV-327 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-327 Project: Hibernate Validator Issue Type: Task Components: build, tck Affects Versions: 4.1.0.Beta1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.2.0 The current build for the tck runner module depends (transitively) on dependencies from the JBoss deprecated repository - https://repository.jboss.org/nexus/content/repositories/deprecated/ We should try if possible to avoid the usage of this repository. Not sure how far this is possible since it would require that there are properly configured upstream dependencies. -- 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

15 years, 9 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-524) Migrate unit tests to H2 (instead of HSQLDB) for inclusion in the Hudson train

by Emmanuel Bernard (JIRA)

Migrate unit tests to H2 (instead of HSQLDB) for inclusion in the Hudson train ------------------------------------------------------------------------------ Key: HSEARCH-524 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-524 Project: Hibernate Search Issue Type: Task Components: build Reporter: Emmanuel Bernard Fix For: 3.3.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

15 years, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-424) Update to Lucene 3.0

by Sanne Grinovero (JIRA)

Update to Lucene 3.0 -------------------- Key: HSEARCH-424 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-424 Project: Hibernate Search Issue Type: Improvement Components: analyzer, directory provider, documentation, engine, mapping, query Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0.Beta2 Lucene 3.0 was released, update the dependencies and fix the code to work with the new APIs, to be able to make use of new features later. -- 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

15 years, 9 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2319) StatelessInterceptor

by Max Rydahl Andersen (JIRA)

StatelessInterceptor -------------------- Key: HHH-2319 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2319 Project: Hibernate3 Type: New Feature Components: core Versions: 3.2.1 Reporter: Max Rydahl Andersen It would make sense to have an Interceptor for StatelessSession to solve the following usecases: Log/adjust SQL: onPrepareStatement Proper entityname handling: instantiate/getEntity Maybe also tx interaction: afterTransationBegin/beforeTransactionCompletion/afterTransactionCompletion Technically it could be solved by just allowing to pass in a normal interceptor to a StatelessSession and just document that the state oriented callbacks will not be called. Alternatively we can create a StatelessInterceptor that only implement the releavant methods and wrap that instance into an internal Interceptor. -- 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

15 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4563) Maven repository uses proprietary JTA as transitive dependency

by Karel Piwko (JIRA)

Maven repository uses proprietary JTA as transitive dependency -------------------------------------------------------------- Key: HHH-4563 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4563 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.6 Reporter: Karel Piwko Transitive dependency javax.transaction:jta:jar:1.0.1B was removed from jboss reposories and it is to be replaced with jboss-transaction-api. <dependency> <groupId>org.jboss.javaee</groupId> <artifactId>jboss-transaction-api</artifactId> </dependency> Logs: Missing: ---------- 1) javax.transaction:jta:jar:1.0.1B Try downloading the file manually from: http://java.sun.com/products/jta Then, install it using the command: mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.transaction -DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.jboss.weld.integration:weld-jboss-int-jboss-ejb:jar:5.2.0-SNAPSHOT 2) org.jboss.ejb3:jboss-ejb3-endpoint-deployer:jar:0.1.3 3) org.jboss.ejb3:jboss-ejb3-core:jar:1.1.5 4) org.hibernate:hibernate:jar:3.2.6.ga 5) javax.transaction:jta:jar:1.0.1B ---------- 1 required artifact is missing. for artifact: org.jboss.weld.integration:weld-jboss-int-jboss-ejb:jar:5.2.0-SNAPSHOT from the specified remote repositories: apiviz.release (http://apiviz.googlecode.com/svn/site/repo/mvn/release), snapshots.jboss.org (http://snapshots.jboss.org/maven2), oss.sonatype.org/jboss-snapshots (http://oss.sonatype.org/content/repositories/jboss-snapshots), central (http://repo1.maven.org/maven2), repository.jboss.org (http://repository.jboss.org/maven2) This breaks a lot of builds. -- 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

15 years, 9 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2007) Hibernate doesn't support optional one-to-one associations

by Andrei Iltchenko (JIRA)

Hibernate doesn't support optional one-to-one associations ---------------------------------------------------------- Key: HHH-2007 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2007 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2 Reporter: Andrei Iltchenko Hibernate doesn't properly support optional one-to-one associations, e.g. Person (0..1) -- (0..1) Passport. The Hibernate books and reference all talk of two ways of mapping one-to-one associations: 1. using a many-to-one fk association with a unique constraint on the fk; 2. using a pk association. the trouble with both of them is that they enforce the mandatory property of an association end, which sometimes is not desirable. The first way enforces the mandatory property with the uniqueness constraint on the fk, the other by using the fact that one table's pk is its fk. I tried to see if I could adapt the 1st way of representing one-to-ones to support optional association ends. What I did was simply remove the unique and not null constrains from DDL generated (without removing it it would be impossible to have a Person record that doesn't reference a Passport record): from CREATE TABLE Person ( PassUniqueId VARCHAR (32) NOT NULL, version INTEGER NOT NULL, uniqueId VARCHAR (32) NOT NULL, name VARCHAR (40) NULL, PRIMARY KEY (uniqueId), UNIQUE(PassUniqueId), FOREIGN KEY (PassUniqueId) REFERENCES Passport (uniqueId) ); to CREATE TABLE Person ( PassUniqueId VARCHAR (32) NULL, version INTEGER NOT NULL, uniqueId VARCHAR (32) NOT NULL, name VARCHAR (40) NULL, PRIMARY KEY (uniqueId), FOREIGN KEY (PassUniqueId) REFERENCES Passport (uniqueId) ); but leave the uniqueness attribute in the mapping file: <many-to-one name="pass" class="application.business.logic.Passport" cascade="save-update,merge" unique="true" > <column name="PassUniqueId"/> </many-to-one> The resulting solution worked fine and I was able to create instances of Person not linked to a Passport. However Hibernate didn't succed in keeping the association from degrading into a many-to-one. It enabled me to create two Persons linked with the same Passport: PASSUNIQUEID | VIRSION | UNIQUEID | Name ================================================ 0d8b3919fffff | 1 | 0d5fb1dcfff | John 0d8b3919fffff | 0 | 10fd07bdfff | Sam A subsequent attempt at retrieving such Persons with Hibernate failed: org.hibernate.HibernateException: More than one row with the given identifier was found: 0d8b3919ffffffd60151e135b6da0164, for class: application.business.logic.Passport. Hibernate should be able to impose the single end property of such associations without relying on the underlying RDBMS engine and never allow them to degrade to many-to-ones. -- 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

15 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-24) Improve the default message of InvalidStateException

by Mike Quilleash (JIRA)

Improve the default message of InvalidStateException ---------------------------------------------------- Key: HV-24 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-24 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 3.0.0.ga Environment: Any Reporter: Mike Quilleash Doing a printStackTrace on InvalidStateException does not give the actual invalid values anywhere. Would greatly improving debugging speed if this was included by default as often this indicates a programming error. Currently I have to run the code again and debug the right place to find out what the InvalidValues are. -- 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

15 years, 9 months

7
14
0 / 0

[Hibernate-JIRA] Created: (HHH-4618) Support pagination: total rows ignore limit

by Dave (JIRA)

Support pagination: total rows ignore limit ------------------------------------------- Key: HHH-4618 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4618 Project: Hibernate Core Issue Type: New Feature Components: core Environment: JBoss 5.1.0GA Reporter: Dave Limit is used for pagination, but total number of rows must be known to calculate page count. Currently we have to use two queries: 1. select * from Student where age<30 limit 20; 2. select count(*) from Student where age<30; For complex query with joins/huge tables, it can be a performance issue. For Criteria API query with group by, there is no way to get row count, for example criteria.setProjection(Projection.projectionList().add(Projections.groupProperty("name")).add(Projections.sum(score))); Currently there is no way to get row count of this query using Criteria API. For MYSQL, SQL_CALC_FOUND_ROWS and FOUND_ROWS() are used to get row count ignoring limit. Pagination is used for all web application. Hibernate should support it in HQL and Criteria API. -- 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

15 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-449) Consider LUCENE-1575 carefully: not scoring by default?

by Sanne Grinovero (JIRA)

Consider LUCENE-1575 carefully: not scoring by default? ------------------------------------------------------- Key: HSEARCH-449 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-449 Project: Hibernate Search Issue Type: Sub-task Reporter: Sanne Grinovero -- 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

15 years, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-528) MassIndexer attempts to index non-indexed subclasses of indexed types

by Sanne Grinovero (JIRA)

MassIndexer attempts to index non-indexed subclasses of indexed types --------------------------------------------------------------------- Key: HSEARCH-528 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-528 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.0.Final, 3.2.0.CR1, 3.2.0.Beta1 Reporter: Sanne Grinovero Fix For: 3.3.0 quoting comments from HSEARCH-526: j nadler : {quote}Sanne, I have @Indexed class Parent, @Indexed class Child1 extends Parent, @Indexed class Child2 extends Parent, unindexed class Child3 extends Parent. I create an indexer fullTextEntityManager.createIndexer(Parent.class), it seems that it then fetches all Parent entities. This includes all Child3 entities but Child3 is not indexed. It seems like the MassIndexer attempts to index them anyway. Best behavior might be to ignore these (explicitly check if the concrete subtype is @Indexed, skip that record if not, possibly log a warning) or as you say it could at least throw an error that makes it clear what the developer (me) did wrong. Thanks! {quote} Emmanuel Bernard : {quote}Ah, right. Sanne, you should use the same algorithm we use in the query building process to check the list of indexed subclasses to create the list of indexes to merge.{quote} -- 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

15 years, 9 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-457) Analyzers in Lucene 3.0 don't have a default constructor

by Sanne Grinovero (JIRA)

Analyzers in Lucene 3.0 don't have a default constructor -------------------------------------------------------- Key: HSEARCH-457 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-457 Project: Hibernate Search Issue Type: Sub-task Components: analyzer Reporter: Sanne Grinovero we're going to need a factory of analyzers or something; could be nice to use "simple" names to embed support for the most common analyzers (the advanced anaylzers are probably most commonly picked from Solr). Analyzers like StopWords where needing parameters anyway to make sense. -- 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

15 years, 9 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-435) New token stream API, is there a benefit, work on our part?

by Emmanuel Bernard (JIRA)

New token stream API, is there a benefit, work on our part? ----------------------------------------------------------- Key: HSEARCH-435 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-435 Project: Hibernate Search Issue Type: Sub-task 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

15 years, 9 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-371) Refactor DocumentBuilder and introduce abstract base class

by Hardy Ferentschik (JIRA)

Refactor DocumentBuilder and introduce abstract base class ---------------------------------------------------------- Key: HSEARCH-371 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-371 Project: Hibernate Search Issue Type: Task Components: engine Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.2.0 Further improvement of the document builder. Introducing a common base class and moving some methods into there and taking care of some not so nice method overriding between the two existing DocumentBuilders will further improve the design of these classes. -- 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

15 years, 9 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4072) ManyToMany with single table inheritance fails when multiple subclasses

by david sinclair (JIRA)

ManyToMany with single table inheritance fails when multiple subclasses ----------------------------------------------------------------------- Key: HHH-4072 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4072 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.3.2 Environment: Windows XP, Java 1.6 Reporter: david sinclair Priority: Critical I have a base entity named BusinessSoftwareMatrixElement declare as such @Entity @Inheritance(strategy = InheritanceType.SINGLE_TABLE) @DiscriminatorColumn(name = "software_type", discriminatorType = DiscriminatorType.STRING) @DiscriminatorValue("Software") @Audited BusinessSoftwareMatrixElement ...{ } I then have a subclass of BusinessSoftwareMatrixElement that is a mapped super class which defines a many to many relationship. @MappedSuperclass @Audited public abstract class BusinessOSProcessServiceMatrixElement extends BusinessSoftwareMatrixElement { private Set<BusinessOSMatrixElement> applicableOperatingSystems = new HashSet<BusinessOSMatrixElement>(); @ManyToMany(fetch = FetchType.LAZY, cascade = {CascadeType.REMOVE, CascadeType.REFRESH }, targetEntity = BusinessOSMatrixElement.class) @JoinTable(name="matrix_elements_procserv_aos", joinColumns=@JoinColumn(name="sw_guid"), inverseJoinColumns = @JoinColumn(name="os_guid")) public Set<BusinessOSMatrixElement> getApplicableOperatingSystems() { return applicableOperatingSystems; } } There are then to subclasses that add no new fields, only different discriminators @Entity @DiscriminatorValue("Database") @Audited public class BusinessDBMatrixElement extends BusinessOSProcessServiceMatrixElement { @Entity @DiscriminatorValue("Application") @Audited public class BusinessAppMatrixElement extends BusinessOSProcessServiceMatrixElement { Running the ant task to create the DDL results in an exception being thrown for that many to many table. Caused by: org.hibernate.DuplicateMappingException: Duplicate class/entity mapping matrix_elements_procserv_aos_AUD at org.hibernate.tool.ant.HibernateToolTask.reportException(HibernateToolTask.java:226) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:189) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:108) ... 24 more Caused by: org.hibernate.DuplicateMappingException: Duplicate class/entity mapping matrix_elements_procserv_aos_AUD at org.hibernate.cfg.Mappings.addClass(Mappings.java:141) at org.hibernate.cfg.HbmBinder.bindRoot(HbmBinder.java:167) at org.hibernate.cfg.Configuration.add(Configuration.java:716) at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:531) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:291) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1162) at org.hibernate.envers.configuration.AuditConfiguration.getFor(AuditConfiguration.java:102) at org.hibernate.envers.ant.AnnotationConfigurationTaskWithEnvers.doConfiguration(AnnotationConfigurationTaskWithEnvers.java:38) at org.hibernate.tool.ant.ConfigurationTask.getConfiguration(ConfigurationTask.java:55) at org.hibernate.tool.ant.HibernateToolTask.getConfiguration(HibernateToolTask.java:302) at org.hibernate.tool.ant.Hbm2DDLExporterTask.createExporter(Hbm2DDLExporterTask.java:51) at org.hibernate.tool.ant.ExporterTask.execute(ExporterTask.java:39) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:186) -- 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

15 years, 9 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2835) Setting org.hibernate.type logging to debug produces no logging

by Jeremy Grodberg (JIRA)

Setting org.hibernate.type logging to debug produces no logging --------------------------------------------------------------- Key: HHH-2835 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2835 Project: Hibernate3 Issue Type: Bug Components: core, documentation Affects Versions: 3.2.5, 3.2.4 Environment: Hibernate 3.2.4.ga and Hibernate 3.2.5.ga with MySQL5Dialect (configured with Hibernate Annotations 3.3.0.ga and Spring 2.0.6) Reporter: Jeremy Grodberg Priority: Minor According to the online documentation (labeled as version 3.2.2 at this moment), Table 3.9 "Hibernate Log Categories", as viewed here today: http://www.hibernate.org/hib_docs/v3/reference/en/html/session-configurat... Setting the log4j category "org.hibernate.type" to debug should "Log all JDBC parameters". However, it produces no output at all. When I go on to set "org.hibernate" to debug, I get output like this: DEBUG: org.hibernate.jdbc.AbstractBatcher - about to open PreparedStatement (open PreparedStatements: 0, globally: 0) DEBUG: org.hibernate.SQL - select count(*) from album where genreID=? DEBUG: org.hibernate.loader.Loader - bindNamedParameters() 126 -> genreId [1] DEBUG: org.hibernate.jdbc.AbstractBatcher - about to open ResultSet (open ResultSets: 0, globally: 0) DEBUG: org.hibernate.loader.Loader - result row: DEBUG: org.hibernate.jdbc.AbstractBatcher - about to close ResultSet (open ResultSets: 1, globally: 1) DEBUG: org.hibernate.jdbc.AbstractBatcher - about to close PreparedStatement (open PreparedStatements: 1, globally: 1) Note that the JDBC parameters are logged under org.hibernate.loader but nothing appears under org.hibernate.type. FYI, genreId is, in this case, a Long. Perhaps this is expected/desired when using annotations? If so, then please update the documentation. If not, please restore the logging. -- 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

15 years, 9 months

10
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2228) ant eg fails - bad release notes quick start

by Brian Brooks (JIRA)

ant eg fails - bad release notes quick start -------------------------------------------- Key: HHH-2228 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2228 Project: Hibernate3 Type: Bug Components: documentation Versions: 3.2.0.ga Environment: hibernate 3.2.0.ga Microsoft Windows XP [Version 5.1.2600] java version "1.5.0_07" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03) Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode) Reporter: Brian Brooks Priority: Minor The hibernate 3.2.0.ga release notes http://sourceforge.net/project/shownotes.php?release_id=455849&group_id=4... read as Get Up And Running Quick ------------------------ Demo: (1) copy your JDBC driver to the lib directory (2) edit etc/hibernate.properties (3) run "ant eg" or "build eg" (4) browse the sourcecode in eg/org/hibernate/auction This directions are incorrect. Below is the ant output if these steps are followed. Also, I had to put junit*.jar and antlr*all*.jar in my ANT_HOME/lib before ant eg would work. C:\hibernate-3.2>ant eg Buildfile: build.xml [taskdef] Could not load definitions from resource clovertasks. It could not b e found. eg: [javac] Compiling 8 source files to C:\hibernate-3.2\build\eg [javac] C:\hibernate-3.2\eg\org\hibernate\auction\Main.java:10: cannot find symbol [javac] symbol : class FetchMode [javac] location: package org.hibernate [javac] import org.hibernate.FetchMode; [javac] ^ [javac] C:\hibernate-3.2\eg\org\hibernate\auction\Main.java:11: cannot find symbol [javac] symbol : class FlushMode [javac] location: package org.hibernate [javac] import org.hibernate.FlushMode; [javac] ^ [javac] C:\hibernate-3.2\eg\org\hibernate\auction\Main.java:12: cannot find symbol [javac] symbol : class LockMode [javac] location: package org.hibernate [javac] import org.hibernate.LockMode; [javac] ^ .... -- 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

15 years, 9 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3778) Select expression results in more than one column having same name when using connected to Sybase

by vijay gudimella (JIRA)

Select expression results in more than one column having same name when using connected to Sybase -------------------------------------------------------------------------------------------------- Key: HHH-3778 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3778 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Environment: Windows XP, Jboss 4.2 GA, JPA Reporter: vijay gudimella The bug described in HB-705 is still a problem. The application runs fine with MySQL and JavaDb but throws the error "Select expression results in more than one column having same name " with Sybase. HB-705 is marked as "Incomplete" , and status as closed, will there be a "fix" or it is considered "fixed" -- 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

15 years, 9 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HV-307) Support @Past/@Future annotations at types from the Joda Time API

by Gunnar Morling (JIRA)

Support @Past/@Future annotations at types from the Joda Time API ----------------------------------------------------------------- Key: HV-307 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-307 Project: Hibernate Validator Issue Type: New Feature Affects Versions: 4.1.0 Reporter: Gunnar Morling Assignee: Hardy Ferentschik Background: =========== The Bean Validation API specifies the annotations @Past and @Future, which are allowed at the JDK types Date and Calendar. Due to several issues and restrictions of these JDK types the open-source Joda Time API (http://joda-time.sourceforge.net/) which provides alternative date/time types became quite popular within the last years. To do: ====== * Hibernate Validator should add support for @Past/@Future for the Joda API date/times types by providing ConstraintValidator implementations for these types. * The Joda Time API should be added as optional dependency to HV. Upon runtime HV should check reflectively if Joda is on the class path. If that's the case, the Joda validators should be registered. * The HV reference guide should mention the additional types at which the @Past/@Future are supported. -- 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

15 years, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3834) Exception: cast() requires two arguments

by Paulo Angelo (JIRA)

Exception: cast() requires two arguments ---------------------------------------- Key: HHH-3834 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3834 Project: Hibernate Core Issue Type: Bug Environment: hibernate3, postgresql 8.3 Reporter: Paulo Angelo Got exaclty the same as in HHH-3285 .: cast() requires two arguments [select f from MenuItem f where ( ( UPPER( TO_ASCII(CAST(convert(f.Menu.Idme, 'UTF8', 'LATIN1') , TEXT),'LATIN1')) LIKE UPPER( TO_ASCII(CAST(convert('M10', 'UTF8', 'LATIN1') , TEXT),'LATIN1')) ) ) order by f.Orde ASC ] But there is not a extra ")" (I think, :) ) -- 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

15 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (METAGEN-28) Custom UserType not supported in Hibernate's static MetaModel generator

by jean-claude cote (JIRA)

Custom UserType not supported in Hibernate's static MetaModel generator ----------------------------------------------------------------------- Key: METAGEN-28 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-28 Project: Hibernate Metamodel Generator Issue Type: Bug Affects Versions: 1.0.0-CR-1 Reporter: jean-claude cote Assignee: Hardy Ferentschik Priority: Minor If an Entity has a custom Hibernate User type @Type it will not get generated in the static MetaModel class "Item_". This seems easy to fix by checking if the element being process has a @Type annotation then process it. AnnotationMetaEntity.isBasicAttribute() ... if(TypeUtils.containsAnnotation(element, Type.class) { return true; } -- 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

15 years, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5230) Regresion! @SequenceGenerator with allocationSize=1 fails Other allocationSizes appear to be decremented by 1

by Mike Youngstrom (JIRA)

Regresion! @SequenceGenerator with allocationSize=1 fails Other allocationSizes appear to be decremented by 1 ------------------------------------------------------------------------------------------------------------- Key: HHH-5230 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5230 Project: Hibernate Core Issue Type: Bug Components: annotations, core Affects Versions: 3.5.2 Reporter: Mike Youngstrom When I attempt to upgrade to 3.5.2 I get an error on startup. If I change my allocationSize to 2 then it starts up fine but debugging into LegacyHiLoAlgorithmOptimizer it appears to be using a value of 1. Caused by: javax.persistence.PersistenceException: [PersistenceUnit: org.lds.stack.stack-pet-store-ws] Unable to build EntityManagerFactory at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:896) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73) at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:225) at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:308) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1469) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1409) ... 38 more Caused by: org.hibernate.MappingException: Could not instantiate id generator [entity-name=org.lds.stack.petstore.model.Animal] at org.hibernate.id.factory.DefaultIdentifierGeneratorFactory.createIdentifierGenerator(DefaultIdentifierGeneratorFactory.java:117) at org.hibernate.mapping.SimpleValue.createIdentifierGenerator(SimpleValue.java:178) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:257) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1385) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:887) ... 43 more Caused by: org.hibernate.HibernateException: increment size cannot be less than 1 at org.hibernate.id.enhanced.OptimizerFactory$LegacyHiLoAlgorithmOptimizer.<init>(OptimizerFactory.java:336) at org.hibernate.id.SequenceHiLoGenerator.configure(SequenceHiLoGenerator.java:64) at org.hibernate.id.factory.DefaultIdentifierGeneratorFactory.createIdentifierGenerator(DefaultIdentifierGeneratorFactory.java:110) ... 48 more -- 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

15 years, 9 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-4969) NullPointerException in FromClause.findIntendedAliasedFromElementBasedOnCrazyJPARequirements due to null alias map key

by Jürgen (JIRA)

NullPointerException in FromClause.findIntendedAliasedFromElementBasedOnCrazyJPARequirements due to null alias map key ---------------------------------------------------------------------------------------------------------------------- Key: HHH-4969 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4969 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Environment: Java version: 1.6.0_16,Sun Microsystems Inc. Java VM: Java HotSpot(TM) 64-Bit Server VM 14.2-b01,Sun Microsystems Inc. OS-System: Linux 2.6.25.14-69.fc8,amd64 Hibernate 3.2.4.sp1 JBosss-4.2.3.GA DB2 v8 / JDBC Driver v4.7.85 Reporter: Jürgen Got a NullPointerException in {{org.hibernate.hql.ast.tree.FromClause.findIntendedAliasedFromElementBasedOnCrazyJPARequirements(String)}} due to fromElementByClassAlias Map key being null. Only for certain HQL query, along the lines of: {code} SELECT c FROM C c, IN(c.t) t, IN(c.k.x) x WHERE c.k.u = 'K' AND t.end >= CURRENT_DATE {code} Removing {{IN(c.k.x) x}} or {{c.k.u = 'K'}} will not result in a NullPointerException, most likely due to no null alias key put into the map. specifiedAlias param was "CURRENT_DATE" when findIntendedAliasedFromElementBasedOnCrazyJPARequirements was called. {code} private FromElement findIntendedAliasedFromElementBasedOnCrazyJPARequirements(String specifiedAlias) { ... if ( alias.equalsIgnoreCase( specifiedAlias ) ) { // alias can be null here .. } {code} {code} java.lang.NullPointerException at org.hibernate.hql.ast.tree.FromClause.findIntendedAliasedFromElementBasedOnCrazyJPARequirements(FromClause.java:120) at org.hibernate.hql.ast.tree.FromClause.containsClassAlias(FromClause.java:247) at org.hibernate.hql.ast.tree.FromClause.isFromElementAlias(FromClause.java:135) at org.hibernate.hql.ast.HqlSqlWalker.isNonQualifiedPropertyRef(HqlSqlWalker.java:467) at org.hibernate.hql.antlr.HqlSqlBaseWalker.addrExpr(HqlSqlBaseWalker.java:4382) at org.hibernate.hql.antlr.HqlSqlBaseWalker.expr(HqlSqlBaseWalker.java:1212) at org.hibernate.hql.antlr.HqlSqlBaseWalker.exprOrSubquery(HqlSqlBaseWalker.java:4041) at org.hibernate.hql.antlr.HqlSqlBaseWalker.comparisonExpr(HqlSqlBaseWalker.java:3648) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1762) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1690) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1687) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1687) at org.hibernate.hql.antlr.HqlSqlBaseWalker.whereClause(HqlSqlBaseWalker.java:776) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:577) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:228) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:160) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:111) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:77) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:56) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:72) at org.hibernate.impl.SessionFactoryImpl.checkNamedQueries(SessionFactoryImpl.java:402) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:352) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:713) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:127) at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:246) at sun.reflect.GeneratedMethodAccessor622.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:103) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.server.jmx.LazyMBeanServer.invoke(LazyMBeanServer.java:291) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) {code} -- 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

15 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2606) CharArrayType allways leads to dirty objects

by Aymeric Levaux (JIRA)

CharArrayType allways leads to dirty objects -------------------------------------------- Key: HHH-2606 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2606 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4 Environment: Hibernate 3.2.4 Postgresql 8.2 or Hsqldb Reporter: Aymeric Levaux Attachments: typechararray.zip When you map a property of type char[], the owning object is always considered as dirty even if untouched. I attached a unit test that reproduce 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

15 years, 9 months

4
5
0 / 0

[Hibernate-JIRA] Created: (METAGEN-32) Update the documentation regarding the usage of the maven-processor-plugin

by Hardy Ferentschik (JIRA)

Update the documentation regarding the usage of the maven-processor-plugin -------------------------------------------------------------------------- Key: METAGEN-32 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-32 Project: Hibernate Metamodel Generator Issue Type: Task Components: build, documentation Affects Versions: 1.0.0.Final Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 1.1.0 The plugin allows now to configure the ap dependency as a plugin dependency instead of a project dependency - http://code.google.com/p/maven-annotation-plugin/issues/detail?id=20 For example: {code} <plugin> <groupId>org.bsc.maven</groupId> <artifactId>maven-processor-plugin</artifactId> <version>1.3.4</version> <executions> <execution> <id>process</id> <goals> <goal>process</goal> </goals> <phase>process-sources</phase> </execution> </executions> <dependencies> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-validator-annotation-processor</artifactId> <version>4.1.0.GA</version> <scope>compile</scope> </dependency> </dependencies> </plugin> {code} -- 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

15 years, 9 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HBX-1068) Hibernate Configurations on Eclipse Ganymede 3.4

by Ricardo M Augusto (JIRA)

Hibernate Configurations on Eclipse Ganymede 3.4 ------------------------------------------------ Key: HBX-1068 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1068 Project: Hibernate Tools Issue Type: Bug Components: eclipse Affects Versions: 3.2.1 Environment: Windows Vista 32bits, hibernate 2.6, eclipse 3.4 (Ganymede) Reporter: Ricardo M Augusto When created hibernate configuration eclipse shows: java.lang.NoClassDefFoundError: org/eclipse/ui/internal/util/SWTResourceUtil at org.hibernate.eclipse.console.workbench.xpl.AnyAdaptableLabelProvider.getImage(AnyAdaptableLabelProvider.java:166) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.getImage(WrappedViewerLabelProvider.java:117) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:165) at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:145) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:932) at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:102) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1012) at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:466) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2041) at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:827) at org.eclipse.jface.viewers.AbstractTreeViewer.createAddedElements(AbstractTreeViewer.java:340) at org.eclipse.jface.viewers.AbstractTreeViewer.internalAdd(AbstractTreeViewer.java:270) at org.eclipse.jface.viewers.TreeViewer.internalAdd(TreeViewer.java:652) at org.hibernate.eclipse.console.viewers.xpl.MTreeViewer.add(MTreeViewer.java:106) at org.eclipse.ui.progress.DeferredTreeContentManager$3.runInUIThread(DeferredTreeContentManager.java:353) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) -- 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

15 years, 9 months

7
6
0 / 0

[Hibernate-JIRA] Created: (METAGEN-7) Try to find a way to be able to use @SupportedAnnotationTypes("javax.persistence.Entity") in JPAMetaModelEntityProcessor

by Hardy Ferentschik (JIRA)

Try to find a way to be able to use @SupportedAnnotationTypes("javax.persistence.Entity") in JPAMetaModelEntityProcessor ------------------------------------------------------------------------------------------------------------------------ Key: METAGEN-7 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-7 Project: Hibernate StaticMetamodel Generator Issue Type: Task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik At the moment we use @SupportedAnnotationTypes("*"). Better would be to explicitly specify @SupportedAnnotationTypes("javax.persistence.Entity"). Then the processor would only be called if there are any entities annotated with @Entity. However, this also means that the processor is not getting called at all if there is no @Entity which could be the case if all configuration is done via xml. We would need a way to make sure that the processor is called at least once to ensure xml is parsed. Other than that only entities annotated with @Entity should be passed to the processor. At the moment I don't see how we can make this happen :( -- 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

15 years, 9 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-5190) Provide annotation support for <discriminator>'s force insert and type features

by Emmanuel Bernard (JIRA)

Provide annotation support for <discriminator>'s force insert and type features ------------------------------------------------------------------------------- Key: HHH-5190 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5190 Project: Hibernate Core Issue Type: New Feature Components: annotations Reporter: Emmanuel Bernard Fix For: 3.6 -- 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

15 years, 9 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HHH-4075) UnsupportedOperationException when assigning an alias to an indexed collection

by Robert Wruck (JIRA)

UnsupportedOperationException when assigning an alias to an indexed collection ------------------------------------------------------------------------------ Key: HHH-4075 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4075 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.2 Environment: Hibernate 3.3.2.GA, MySQL5InnoDBDialect Reporter: Robert Wruck This works: select count(*) from Order o left join o.orderAttributes oa, Attribute a where a.id = 1 and index(oa) = a but accessing elements throws an exception: select count(*) from Order o left join o.orderAttributes oa, Attribute a where a.id = 1 and oa[a] is null or oa[a] = '2' Replacing oa[a] with o.orderAttributes[a] does not throw an exception but also does an inner join, so it's not a workaround. Stack trace: java.lang.UnsupportedOperationException at org.hibernate.hql.ast.tree.IdentNode.resolveIndex(IdentNode.java:66) at org.hibernate.hql.ast.tree.IndexNode.resolve(IndexNode.java:94) at org.hibernate.hql.ast.tree.FromReferenceNode.resolve(FromReferenceNode.java:117) at org.hibernate.hql.ast.tree.FromReferenceNode.resolve(FromReferenceNode.java:113) at org.hibernate.hql.ast.HqlSqlWalker.processIndex(HqlSqlWalker.java:956) at org.hibernate.hql.antlr.HqlSqlBaseWalker.addrExpr(HqlSqlBaseWalker.java:4576) at org.hibernate.hql.antlr.HqlSqlBaseWalker.expr(HqlSqlBaseWalker.java:1289) at org.hibernate.hql.antlr.HqlSqlBaseWalker.exprOrSubquery(HqlSqlBaseWalker.java:4243) at org.hibernate.hql.antlr.HqlSqlBaseWalker.comparisonExpr(HqlSqlBaseWalker.java:4084) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1864) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1792) at org.hibernate.hql.antlr.HqlSqlBaseWalker.whereClause(HqlSqlBaseWalker.java:818) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:604) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:288) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:231) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:254) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:185) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:136) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:101) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:94) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1651) -- 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

15 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3096) Count operator with idenfication variable w/ composite primary key produces bad sql

by Bob Tiernay (JIRA)

Count operator with idenfication variable w/ composite primary key produces bad sql ------------------------------------------------------------------------------------ Key: HHH-3096 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3096 Project: Hibernate3 Issue Type: Bug Reporter: Bob Tiernay @EmbeddedId private Id id; @Embeddable public static class Id implements Serializable { private static final long serialVersionUID = 6475618094377929936L; @Column(name="TG_ID", nullable = false) private Integer groupId; @Column(name="MBR_ID", nullable = false) private Integer memberId; public Id() { // Empty } public Id(Integer groupId, Integer memberId) { super(); this.groupId = groupId; this.memberId = memberId; } @Override public boolean equals(Object other) { if (other == this) { return true; } else if (other instanceof Id) { return groupId.equals(((Id) other).groupId) && memberId.equals(((Id) other).memberId); } return false; } @Override public int hashCode() { return groupId.hashCode() ^ memberId.hashCode(); } } @NamedQuery(name = "GroupMember.getCountByGroup", query = "SELECT COUNT(gm) FROM GroupMember gm WHERE gm.id.groupId = :groupId") produces Hibernate: /* named HQL query GroupMember.getCountByGroup */ select count((groupmembe0_.TG_ID, groupmembe0_.MBR_ID)) as col_0_0_ from GROUP_MEMBER groupmembe0_ where groupmembe0_.TG_ID=? and the following hibernate exception Caused by: java.sql.SQLException: ORA-00907: missing right parenthesis at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216) at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:810) at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1039) at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:850) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1134) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3339) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3384) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:93) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:186) at org.hibernate.loader.Loader.getResultSet(Loader.java:1787) at org.hibernate.loader.Loader.doQuery(Loader.java:674) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader Which is consistent with what Oracle produces by manual query execution. The problem is the extra set of parenthesis around the composite primary key columns which appear to be invalid (at least for Oracle) The recommend fix would be to use COUNT(*) or count(groupmembe0_.TG_ID, groupmembe0_.MBR_ID) in yhis case -- 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

15 years, 9 months

7
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3187) Issue with Hibernate3.0 and weblogic8.1 while setting transaction is marked to setRollbackOnly... (AppSetRollbackOnlyException)

by Anjan Deb (JIRA)

Issue with Hibernate3.0 and weblogic8.1 while setting transaction is marked to setRollbackOnly... (AppSetRollbackOnlyException) ------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3187 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3187 Project: Hibernate3 Issue Type: Task Affects Versions: 3.0 final Environment: hibernate3.0, weblogic8.1, oracle9.1 Reporter: Anjan Deb I am using Hibernate 3.0 with JTA (Weblogic 8.1 SP4). Basically, I am trying to handle transaction/hibernate exceptions in my application. I am managing transactions with UserTransaction. I start a transaction at the begining of the request and after that I am doing some operations on that transaction. And if some exception comes I log it, rollback the transaction and throw the exception. UserTransaction.commit() throws RollbackException if anything goes wrong with the operation, but, it does not return what exactly went wrong, like, exceptions related to SQL Exception or hibernate Exception. It basically dumps all that information to the logs internally and throws RollbackException with the following trace (see below). But this trace has no such information which I can send back to the user. As, information of what went wrong has already been dumped to the server console. I will appreciate if you can tell if there is anyway I can recieve the actual exception trace or am I doing anything wrong with the hibernate configuration?? Thanks in Advance, Anjan ------------------------------------------------------------------------------------------------------------------------------ Actual Exception which transaction dumps to the server console/log ERROR - ORA-00001: unique constraint (NOVATXN.UQ_BROKERS) violated ERROR - ORA-00001: unique constraint (NOVATXN.UQ_BROKERS) violated ERROR - Could not synchronize database state with session org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:69) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:202) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:230) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:296) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:980) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:353) at org.hibernate.transaction.CacheSynchronization.beforeCompletion(CacheSynchronization.java:59) at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010) at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115) at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1216) at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1990) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:275) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:246) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:303) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:296) at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:31) at com.ebw.nova.common.invoker.TransactionalAction.doAction(TransactionalAction.java:47) at com.ebw.nova.common.invoker.ActionInvoker.invokeAction(ActionInvoker.java:21) at com.ebw.nova.server.handler.AbstractRequestHandler.process(AbstractRequestHandler.java:73) at com.ebw.nova.server.communication.jms.MessageProcessor.processRequest(MessageProcessor.java:44) at com.ebw.ejb.mdb.MQManager.onMessage(MQManager.java:70) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) Caused by: java.sql.BatchUpdateException: ORA-00001: unique constraint (NOVATXN.UQ_BROKERS) violated at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:367) at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:8726) at weblogic.jdbc.wrapper.PreparedStatement.executeBatch(PreparedStatement.java:169) at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:58) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:195) ... 27 more RollbackException Trace: 03/17/2008 08:50:09 [EROR] JTATransactionalAction weblogic.transaction.RollbackException: Unknown reason - with nested exception: [weblogic.transaction.internal.AppSetRollbackOnlyException] 03/17/2008 08:50:09 [EROR] JTATransactionalAction com.novarum.nova.application.OperationException: Transaction does not exist 03/17/2008 08:50:09 [DBUG] MessageProcessor Unknown reason java.lang.RuntimeException: Unknown reason at com.ebw.nova.common.invoker.TransactionalAction.doAction(TransactionalAction.java:54) at com.ebw.nova.common.invoker.ActionInvoker.invokeAction(ActionInvoker.java:21) at com.ebw.nova.server.handler.AbstractRequestHandler.process(AbstractRequestHandler.java:73) at com.ebw.nova.server.communication.jms.MessageProcessor.processRequest(MessageProcessor.java:44) at com.ebw.ejb.mdb.MQManager.onMessage(MQManager.java:70) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) Caused by: com.novarum.nova.application.OperationException: Unknown reason at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:35) at com.ebw.nova.common.invoker.TransactionalAction.doAction(TransactionalAction.java:47) ... 10 more Caused by: weblogic.transaction.RollbackException: Unknown reason - with nested exception: [weblogic.transaction.internal.AppSetRollbackOnlyException] at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1683) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:325) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:246) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:303) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:296) at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:31) ... 11 more getCause(): com.novarum.nova.application.OperationException: Unknown reason at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:35) at com.ebw.nova.common.invoker.TransactionalAction.doAction(TransactionalAction.java:47) at com.ebw.nova.common.invoker.ActionInvoker.invokeAction(ActionInvoker.java:21) at com.ebw.nova.server.handler.AbstractRequestHandler.process(AbstractRequestHandler.java:73) at com.ebw.nova.server.communication.jms.MessageProcessor.processRequest(MessageProcessor.java:44) at com.ebw.ejb.mdb.MQManager.onMessage(MQManager.java:70) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) Caused by: weblogic.transaction.RollbackException: Unknown reason - with nested exception: [weblogic.transaction.internal.AppSetRollbackOnlyException] at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1683) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:325) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:246) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:303) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:296) at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:31) ... 11 more getCause(): weblogic.transaction.internal.AppSetRollbackOnlyException at weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImpl.java:504) at org.hibernate.transaction.CacheSynchronization.setRollbackOnly(CacheSynchronization.java:73) at org.hibernate.transaction.CacheSynchronization.beforeCompletion(CacheSynchronization.java:63) at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010) at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115) at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1216) at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1990) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:275) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:246) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:303) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:296) at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:31) at com.ebw.nova.common.invoker.TransactionalAction.doAction(TransactionalAction.java:47) at com.ebw.nova.common.invoker.ActionInvoker.invokeAction(ActionInvoker.java:21) at com.ebw.nova.server.handler.AbstractRequestHandler.process(AbstractRequestHandler.java:73) at com.ebw.nova.server.communication.jms.MessageProcessor.processRequest(MessageProcessor.java:44) at com.ebw.ejb.mdb.MQManager.onMessage(MQManager.java:70) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) --------------- nested within: ------------------ weblogic.transaction.RollbackException: Unknown reason - with nested exception: [weblogic.transaction.internal.AppSetRollbackOnlyException] at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1683) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:325) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:246) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:303) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:296) at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:31) at com.ebw.nova.common.invoker.TransactionalAction.doAction(TransactionalAction.java:47) at com.ebw.nova.common.invoker.ActionInvoker.invokeAction(ActionInvoker.java:21) at com.ebw.nova.server.handler.AbstractRequestHandler.process(AbstractRequestHandler.java:73) at com.ebw.nova.server.communication.jms.MessageProcessor.processRequest(MessageProcessor.java:44) at com.ebw.ejb.mdb.MQManager.onMessage(MQManager.java:70) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) getNested(): weblogic.transaction.internal.AppSetRollbackOnlyException at weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImpl.java:504) at org.hibernate.transaction.CacheSynchronization.setRollbackOnly(CacheSynchronization.java:73) at org.hibernate.transaction.CacheSynchronization.beforeCompletion(CacheSynchronization.java:63) at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010) at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:115) at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1216) at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1990) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:275) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:246) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:303) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:296) at com.ebw.nova.common.invoker.JTATransactionalAction.commit(JTATransactionalAction.java:31) at com.ebw.nova.common.invoker.TransactionalAction.doAction(TransactionalAction.java:47) at com.ebw.nova.common.invoker.ActionInvoker.invokeAction(ActionInvoker.java:21) at com.ebw.nova.server.handler.AbstractRequestHandler.process(AbstractRequestHandler.java:73) at com.ebw.nova.server.communication.jms.MessageProcessor.processRequest(MessageProcessor.java:44) at com.ebw.ejb.mdb.MQManager.onMessage(MQManager.java:70) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178) Following is the hibernate.cfg.xml <session-factory>  <property name="connection.datasource">jdbc/novaJDBCDataSource</property> <property name="transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property> <property name="transaction.manager_lookup_class">org.hibernate.transaction.WeblogicTransactionManagerLookup</property> <property name="dialect">org.hibernate.dialect.OracleDialect</property> <property name="current_session_context_class">jta</property> <property name="show_sql">false</property> <property name="format_sql">true</property> <property name="hibernate.default_schema">novatxn</property> <property name="jdbc.batch_size">30</property>  <property name="jdbc.batch_versioned_data">false</property> <property name="jdbc.use_streams_for_binary">true</property>  <property name="max_fetch_depth">1</property> <property name="query.substitutions">true 1, false 0, yes 'Y', no 'N'</property>   <property name="query.factory_class">org.hibernate.hql.classic.ClassicQueryTranslatorFactory</property> </session-factory> -- 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

15 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3900) Do not attempt to register Synchronization when Transaction is in STATUS_MARKED_ROLLBACK

by Chris Bredesen (JIRA)

Do not attempt to register Synchronization when Transaction is in STATUS_MARKED_ROLLBACK ---------------------------------------------------------------------------------------- Key: HHH-3900 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3900 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1, 3.2.6 Reporter: Chris Bredesen Priority: Minor In JTASessionContext.currentSession(), a CleanupSync is built and registered. The transaction is verified to be in progress using JTAHelper.isInProgress() which checks for STATUS_ACTIVE or STATUS_MARKED_ROLLBACK. JBossTS (based on the OTS standard) disallows the registration of Synchronizations in STATUS_MARKED_ROLLBACK and so in such cases, JTASessionContext.currentSession() will fail. The stack trace looks something like this (note no wrapped root cause): Caused by: org.hibernate.HibernateException: Unable to register cleanup Synchronization with TransactionManager at org.hibernate.context.JTASessionContext.currentSession(JTASessionContext.java:92) at org.hibernate.impl.SessionFactoryImpl.getCurrentSession(SessionFactoryImpl.java:544) A possible fix is to check only for STATUS_ACTIVE and do any needed cleanup work proactively if the Transaction is in STATUS_MARKED_ROLLBACK rather than relying on CleanupSync. -- 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

15 years, 9 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3690) Sybase - FumTest.testCompositeKeyPathExpressions() fails due to subquery with more than one column in select list

by Gail Badner (JIRA)

Sybase - FumTest.testCompositeKeyPathExpressions() fails due to subquery with more than one column in select list ----------------------------------------------------------------------------------------------------------------- Key: HHH-3690 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3690 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Gail Badner Sybase only allows one column in a subquery select list. The only exception is that a subquery in an EXISTS() predicate can have '*' as the select list. This is documented at: http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc32300.150... FumTest.testCompositeKeyPathExpressions() fails with "SybSQLException: Incorrect syntax near ','." The HQL that fails is: "from Fum fum1 where exists elements(fum1.friends)". It fails becuase the elements have a composite ID. The fix described in HHH-3032 should fix this issue since the subquery is used in an EXISTS() predicate.. -- 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

15 years, 9 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5205) Add support for source="db" for timestamp versions

by Emmanuel Bernard (JIRA)

Add support for source="db" for timestamp versions -------------------------------------------------- Key: HHH-5205 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5205 Project: Hibernate Core Issue Type: New Feature Components: annotations Reporter: Emmanuel Bernard Fix For: 3.6 See documentation of <timestamp source=""/> -- 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

15 years, 9 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4510) Add column-level read/write support (HHH-4440) to annotations

by Steve Ebersole (JIRA)

Add column-level read/write support (HHH-4440) to annotations ------------------------------------------------------------- Key: HHH-4510 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4510 Project: Hibernate Core Issue Type: Bug Components: annotations Reporter: Steve Ebersole See HHH-4440 for details -- 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

15 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (METAGEN-30) @Target

by jean-claude cote (JIRA)

@Target ------- Key: METAGEN-30 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-30 Project: Hibernate Metamodel Generator Issue Type: Bug Components: processor Reporter: jean-claude cote Assignee: Hardy Ferentschik The jpamodelgen does not produce output for fields mapped using the @Embedded/@Target tags. ex: @Entity class House { @Embedded @Target(acme.AddressImpl.class) private Address address; } It only works when the field is of type AddressImpl. Are there plans to support the hiberbate specific annotations? Any plans to support entity mapped using classic hbm.xml files? thanks jean-claude -- 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

15 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2917) arithmatic of subselect throws NPE

by John Aylward (JIRA)

arithmatic of subselect throws NPE ---------------------------------- Key: HHH-2917 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2917 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.5 Environment: Hibernate 3.2.5 Annotation 3.3.0 VAlidator 3.0.0 MySQL 5.0.44 Reporter: John Aylward Exception Stack: java.lang.NullPointerException at org.hibernate.hql.ast.tree.BinaryArithmeticOperatorNode.getRightHandOperand(BinaryArithmeticOperatorNode.java:185) at org.hibernate.hql.ast.tree.BinaryArithmeticOperatorNode.initialize(BinaryArithmeticOperatorNode.java:20) at org.hibernate.hql.ast.HqlSqlWalker.prepareArithmeticOperator(HqlSqlWalker.java:1011) at org.hibernate.hql.antlr.HqlSqlBaseWalker.arithmeticExpr(HqlSqlBaseWalker.java:2729) at org.hibernate.hql.antlr.HqlSqlBaseWalker.expr(HqlSqlBaseWalker.java:1278) at org.hibernate.hql.antlr.HqlSqlBaseWalker.exprOrSubquery(HqlSqlBaseWalker.java:4041) at org.hibernate.hql.antlr.HqlSqlBaseWalker.comparisonExpr(HqlSqlBaseWalker.java:3600) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1762) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1690) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1687) at org.hibernate.hql.antlr.HqlSqlBaseWalker.whereClause(HqlSqlBaseWalker.java:776) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:577) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:228) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:160) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:111) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:77) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:56) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:72) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:133) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:112) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1623) HQL: [SELECT DISTINCT pi.billingAccount.consolidatedBillingAccount.bankAccount FROM com.cicat.bedrock.billing.model.ProviderInvoice AS pi WHERE pi.readyForPayment=true AND (SELECT piad.total FROM com.cicat.bedrock.billing.model.ProviderInvoiceAccountData AS piad WHERE piad.invoice = pi AND piad.providerBillingAccount = pi.billingAccount) > ((SELECT COALESCE(SUM(amount),0) FROM com.cicat.bedrock.billing.model.BankAccountTransaction AS bat1 WHERE bat1.deleted=false AND bat1.providerInvoice = pi) + (SELECT COALESCE(SUM(amount),0) FROM com.cicat.bedrock.billing.model.BankAccountTransactionSplit AS bats1 WHERE bats1.deleted=false AND bats1.bankAccountTransaction.deleted=false AND bats1.providerInvoice = pi)) ] Representative SQL of HQL call: SELECT DISTINCT ba.* from ProviderInvoice AS pi INNER JOIN ProviderBillingAccount AS pba ON pi.billingAccount_id=pba.id INNER JOIN ConsolidatedBillingAccount AS cba ON pba.consolidatedBillingAccount_id=cba.id INNER JOIN BankAccount AS ba ON cba.bankAccount_id=ba.id WHERE pi.readyForPayment=true AND (SELECT piad.total FROM ProviderInvoiceAccountData AS piad WHERE piad.invoice_id = pi.id AND piad.providerBillingAccount_id = pi.billingAccount_id) > ((SELECT COALESCE(SUM(bat1.amount),0) FROM BankAccountTransaction AS bat1 WHERE bat1.deleted=false AND bat1.providerInvoice_id = pi.id) + (SELECT COALESCE(SUM(bats1.amount),0) FROM BankAccountTransactionSplit AS bats1 INNER JOIN BankAccountTransaction bat2 ON bats1.bankAccountTransaction_id=bat2.id WHERE bats1.deleted=false AND bat2.deleted=false AND bats1.providerInvoice_id = pi.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

15 years, 9 months

4
15
0 / 0

[Hibernate-JIRA] Created: (HBX-849) Tools does not insert @Type in POJOs for user types defined in reveng.xml

by Zeljko Trogrlic (JIRA)

Tools does not insert @Type in POJOs for user types defined in reveng.xml ------------------------------------------------------------------------- Key: HBX-849 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-849 Project: Hibernate Tools Type: Bug Components: hbm2java, reverse-engineer Environment: jboss-seam-1.1.0.GA, MySQL Reporter: Zeljko Trogrlic I have created reveng.xml file: <hibernate-reverse-engineering> <table catalog="configuration" name="userdb_domain_acl"> <column name="enabled" type="com.siemens.msm.model.mapping.BooleanEnumType" exclude="false"/> </table> </hibernate-reverse-engineering> and included it in build.xml: <jdbcconfiguration propertyfile="build.properties" packagename="${model.package}" revengfile="${project.home}/reveng.xml"/> Generated POJO attribute has proper type, but user type information is missing: @Column(name = "enabled") @Length(max = 42) public Boolean getEnabled() { .... so Hibernate reports error: 3:49:31,397 INFO [TableMetadata] table found: configuration.userdb_domain_acl 13:49:31,397 INFO [TableMetadata] columns: [id, enabled, tablename, domain] 13:49:31,397 WARN [ServiceController] Problem starting service persistence.units:ear=msmgui.ear,unitName=msmgui javax.persistence.PersistenceException: org.hibernate.HibernateException: Wrong column type: enabled, expected: varchar( 2) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:698) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:127) at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:264) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Annotations should look like this: @Column(name = "enabled") @Type(type="booleanEnum") public Boolean getEnabled() { ... -- 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

15 years, 9 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3227) Oracle's connect by syntax is mishandled when used with Filter

by Kyrill Alyoshin (JIRA)

Oracle's connect by syntax is mishandled when used with Filter -------------------------------------------------------------- Key: HHH-3227 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3227 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.5 Environment: Hibernaet 3.2.5.GA, Oracle 10g. Reporter: Kyrill Alyoshin Basically, I have a filter definition on a class (via annotation), here it is: @Filter(name = "limitInvoicesByAccountHolderHierarchy", condition = "CHRG_ACCT_ID in (" + "select ca1.chrg_acct_id from cv_chrg_acct ca1 " + "inner join cv_org_unit og1 on ca1.acct_hldr_id = og1.org_unit_id " + "where og1.org_unit_id in (" + "select og2.org_unit_id from cv_org_unit og2 " + "start with og2.org_unit_id = :root " + " connect by prior og2.org_unit_id = og2.hier_par_org_unit_id" + ')' + ')' It contains Oracle's "connect by" clause. Here is the SQL statement that Hibernate generates when trying to query invoices with the filter enabled: Hibernate: /* from Invoice */ select invoice0_.inv_id as inv1_31_, ...... from CV_INV invoice0_ where invoice0_.CHRG_ACCT_ID in ( select ca1.chrg_acct_id from cv_chrg_acct ca1 inner join cv_org_unit og1 on ca1.acct_hldr_id = og1.org_unit_id where og1.org_unit_id in ( select og2.org_unit_id from cv_org_unit og2 invoice0_.start invoice0_.with og2.org_unit_id = ? invoice0_.connect by invoice0_.prior og2.org_unit_id = og2.hier_par_org_unit_id ) ) Even though the documentation states that the condition of the filter is pure SQL (which is great!), it still does not pass SQL verbatim but is actually trying to pre-process the following words: start, with, connect, prior. Is there an easy work around to make Oracle10gDialect recognize these words? Thanks a lot for looking into 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

15 years, 9 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2402) HQL generates inner join when selecting a specific attribute that is linked to another entity

by Peter Mutsaers (JIRA)

HQL generates inner join when selecting a specific attribute that is linked to another entity --------------------------------------------------------------------------------------------- Key: HHH-2402 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2402 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.2 Environment: Oracle 9i, affects ONLY version 3.2.2, was still working OK in version 3.2.1 and before. Reporter: Peter Mutsaers Priority: Critical Mapping (note the lazy='false', it is essential to cause the problem): <class name='Currency' lazy='false'> .... </class> <class name='Asset'> <id name='id' ... </id> <many-to-one name='currency' class='Currency' fetch='select'/> </class> The following HQL query: "select a.id, a.currency from Asset a" used to generate a query on the Asset table, and subsequently generates separate queries on the Currency table. Since version 3.2.2, this generates an inner join on Asset with Currency. Now many Assets may have a NULL currency, so we do not get all records anymore! This breaks logic and queries all over the place for us. We can't go back to 3.2.1 due to other bugs that had been solved in 3.2.2. The query "from Asset a" still works OK and as before, i.e. it makes the select only on the Asset table and afterwards fetches the Currency with individual selects. I fear that an optimization has been made that has this negative side effect. -- 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

15 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3510) Sybase - Timestamp not being translated to the built-in database function

by Juraci Paixao Krohling (JIRA)

Sybase - Timestamp not being translated to the built-in database function ------------------------------------------------------------------------- Key: HHH-3510 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3510 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Environment: Branch_3_2_4_SP1_CP and Sybase 15 Reporter: Juraci Paixao Krohling Test Case: ComponentTest#testComponentQueries Hibernate query "from Employee e where e.person = ('steve', current_timestamp)" should have translated "current_timestamp" to "getdate()" [1]: 14:49:11,087 DEBUG SQL:424 - select employee0_.ID as ID1_, employee0_.HIRE_DATE as HIRE2_1_, employee0_.name as name1_, employee0_.dob as dob1_, employee0_.value1 as value5_1_, employee0_.value2 as value6_1_ from T_EMP employee0_ where employee0_.name='steve' and employee0_.dob=current_timestamp 14:49:11,535 WARN JDBCExceptionReporter:77 - SQL Error: 207, SQLState: ZZZZZ 14:49:11,536 ERROR JDBCExceptionReporter:78 - Invalid column name 'current_timestamp'. [1] SybaseDialect, line 58: registerFunction( "current_timestamp", new NoArgSQLFunction("getdate", Hibernate.TIMESTAMP) ); -- 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

15 years, 10 months

4
8
0 / 0

[Hibernate-JIRA] Created: (BVTCK-5) Provide separate signature files for Java 5 and Java 6

by Hardy Ferentschik (JIRA)

Provide separate signature files for Java 5 and Java 6 ------------------------------------------------------- Key: BVTCK-5 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVTCK-5 Project: Bean Validation TCK Issue Type: Task Affects Versions: 1.0.2.GA Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 1.0.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

15 years, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (ANN-592) @TableGenerator realisation does not respect initialValue

by Christoph Schönfeld (JIRA)

@TableGenerator realisation does not respect initialValue --------------------------------------------------------- Key: ANN-592 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-592 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.0.ga Reporter: Christoph Schönfeld Priority: Minor I would like to have generated IDs for a certain entity type start at the value of 1000. Consider the following example. @TableGenerator(name = "employee", table = "SEQUENCES", pkColumnName = "name", valueColumnName = "value", pkColumnValue = "employee", allocationSize = 10, initialValue = 1000) Hibernate generates the SEQUENCES table correctly but it always returns 1 as the first generated key. In the source code of AnnotationBinder.java which seems to be responsible for binding the @TableGenerator annotation to a MultipleHiLoPerTableGenerator instance the initialValue property is ignored. -- 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

15 years, 10 months

6
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4690) Consider adding a flag for legacy/new generators

by Emmanuel Bernard (JIRA)

Consider adding a flag for legacy/new generators ------------------------------------------------ Key: HHH-4690 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4690 Project: Hibernate Core Issue Type: Sub-task 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

15 years, 10 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3018) Configuration element to tell Hibernate to have just one insert to flush an entity and not both an insert and an update.

by Nicolas Cazottes (JIRA)

Configuration element to tell Hibernate to have just one insert to flush an entity and not both an insert and an update. ------------------------------------------------------------------------------------------------------------------------ Key: HHH-3018 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3018 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.5 Reporter: Nicolas Cazottes Attachments: testXMLTypeUpdates.zip While analyzing the SQL queries Hibernate generates to persist objects, I fall on a behaviour, that I first found strange, which is that in one flush of one transaction, there may be both an insert and an update for a given entity. My first expectation was to have only one insert and no update. After a few search, I discover that conversation (http://forum.hibernate.org/viewtopic.php?p=2191664&sid=c571096bda4a6b636e...) that explains it is normal in the case of a save with modifications after save. I discover (cf the classes of my zip showing it) that this behaviour is also present in the case of a relation that is managed by cascade. What I noticed is that the insert of the related entity is planned when the first hql query is executed after the relation has been established. So if the related entity is modified after the query execution (for exemple depending on the result of the query), an update will be executed. This behaviour is understandable but in my case, the update is really expensive (because it acts on an XMLType column) and unless I set a FlushMode to COMMIT (which I found really not a good solution), I can not control that Hibernate will generate both an insert and an update or only an insert. I know I could also set the relation just before the commit in order to avoid insert+update but this solution is not possible in my case and I find it not elegant (it would break the semantic of the cascade of the relation). I suggest to introduce a new configuration element (similar to the flushmode) in Hibernate in order to be able to have control whether Hibernate generates an insert containing the data of the entity at the first save or an insert containing the data of the entity at the flushing time. Note : The attached files (which is the smallest extraction of what does my application) shows that behaviour both for the save call and the cascade declenched by a query. Note2 : I found an issue in jira number 2621 submited by someone else that is related to this subject in think. -- 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

15 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2426) Misleading logging messages when using ThreadLocalSessionContext

by Don Smith (JIRA)

Misleading logging messages when using ThreadLocalSessionContext ---------------------------------------------------------------- Key: HHH-2426 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2426 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.0.ga Reporter: Don Smith Priority: Minor The log messages printed out by TransactionFactoryFactory and SettingsFactory are misleading when using ThreadLocalSessionContext: 2007-02-09 21:49:58,581 INFO [org.hibernate.transaction.TransactionFactoryFactory:info] Using default transaction strategy (direct JDBC transactions) 2007-02-09 21:49:58,588 INFO [org.hibernate.transaction.TransactionManagerLookupFactory:info] No TransactionManagerLookup Configured (in JTA environment, use of read-write or transactional second-level cache is not recommended) 2007-02-09 21:49:58,590 INFO [org.hibernate.cfg.SettingsFactory:info] Automatic flush during beforeCompletion(): disabled 2007-02-09 21:49:58,591 INFO [org.hibernate.cfg.SettingsFactory:info] Automatic session close at end of transaction: disabled This does not indicate that sessions will be closed after commit, which is the behavior when using ThreadLocalSessionContext. -- 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

15 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-682) @ForeignKey override of @MappedSuperclass

by Christian Bauer (JIRA)

@ForeignKey override of @MappedSuperclass ----------------------------------------- Key: ANN-682 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-682 Project: Hibernate Annotations Issue Type: New Feature Components: binder Reporter: Christian Bauer Put this @ManyToOne in a @MappedSuperclass: @ManyToOne(fetch = FetchType.LAZY) @JoinColumn(name = "CREATED_BY_USER_ID", nullable = false) // Ideally this foreign key should be ON DELETE SET NULL, however... // Hibernate can't rename these so subclasses would get the same FK constraint name. This doesn't // work, so we need to let Hibernate create a random identifier for these. We could fix this in the // DatabaseObjects.hbm.xml file but we can't even address it because the name is random. This sucks. // So we do a manual SET NULL|DEFAULT when userHome.remove() is called. // @org.hibernate.annotations.ForeignKey(name = "FK_WIKI_NODE_CREATED_BY_USER_ID") protected User createdBy; Now all subclasses get that foreign key constraint name in the database catalog, which isn't possible - constraint names have to be unique. -- 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

15 years, 10 months

6
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-527) Hibernate Search Not giving any errror when @DocumentId not mentioned, but hangs at configuration.buildSessionFactory()

by Kiran Narasareddy (JIRA)

Hibernate Search Not giving any errror when @DocumentId not mentioned, but hangs at configuration.buildSessionFactory() ----------------------------------------------------------------------------------------------------------------------- Key: HSEARCH-527 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-527 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.0.GA Environment: Hibernate core : 3.3.1 GA, Hibernate Annotations : 3.4.0.GA, Hibernate commons Annotations : 3.1.0 GA, Lucene core 2.4.1 Mysql Community 5.0.41 Reporter: Kiran Narasareddy Priority: Minor Consider a case in which primary key is associated with only Base class, with no primary key in any other subclasses marked for Lucene's document id. Now, if this attribute is not annotated with @DocumentId, hibernate engine shows no errors, but it hangs up at configuration.buildSessionFactory(); and doesn't move forward. The moment the annotation is added, the SessionFactory gets built and the application works. Example Model : Aobject.java : long id; (this is the intended field to be taken as documentID for lucene ) MyObject extends Aobject (This class is to be indexed.It has no id field of its own, the same id from AObject acts as PK for MyObject Also) -- 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

15 years, 10 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3976) NPE when eager fetching joined component with native SQL query

by Franz Allan Valencia See (JIRA)

NPE when eager fetching joined component with native SQL query -------------------------------------------------------------- Key: HHH-3976 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3976 Project: Hibernate Core Issue Type: Bug Components: query-sql Affects Versions: 3.2.0.ga Reporter: Franz Allan Valencia See Priority: Critical Given a Hibernate Mapping with formula and named sql query, When accessing named sql query, NPE is thrown. This is basically a duplicae of HHH-2225. But since I cannot edit that to change it's Priority, I created a dupe. Feel free to close this if HHH-2225 has been edited to a higher priority. IMHO, it should be of a higher priority because AFAIK there are no decent workaround for 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

15 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3339) Query cache stops working after object save

by Alex Oleynikov (JIRA)

Query cache stops working after object save ------------------------------------------- Key: HHH-3339 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3339 Project: Hibernate3 Issue Type: Bug Components: caching (L2) Affects Versions: 3.2.6 Environment: Hibernate 3.2.6, MS SQL 2005 Database. Windows XP SP2 Reporter: Alex Oleynikov It seems like HB Query cache stops working as soon as given object type is being saved (it does not matter if it was save to existing object or insert of new object instance). The code looks like this. Where User is just a primitive POJO with couple of properties. // #1 query = session.createQuery("from User where userID = :id"); query.setCacheable(true); query.setParameter("id", 10); user = (User) query.list().get(0); // #2 query = session.createQuery("from User where userID = :id"); query.setCacheable(true); query.setParameter("id", 10); user = (User) query.list().get(0); // insert new User object user = new User(); user.setUserID((int)(Math.random() * Integer.MAX_VALUE)); user.setUserName("Ten"); session.beginTransaction(); session.save(user); session.getTransaction().commit(); // #3 query = session.createQuery("from User where userID = :id"); query.setCacheable(true); query.setParameter("id", 10); user = (User) query.list().get(0); // #4 query = session.createQuery("from User where userID = :id"); query.setCacheable(true); query.setParameter("id", 10); user = (User) query.list().get(0); >From MS SQL Profiler I can clearly see that no queries is executed for #2 (e.g. it hit the cache), but queries are executed for #3 and #4. From HB debug log I see following: For #2 Query (cache is hit) - correct: 06:54:25,337 DEBUG StandardQueryCache:102 - checking cached query results in region: org.hibernate.cache.StandardQueryCache 06:54:25,337 DEBUG StandardQueryCache:156 - Checking query spaces for up-to-dateness: [USERS] 06:54:25,337 DEBUG StandardQueryCache:117 - returning cached query results During User insert: 06:54:25,368 DEBUG UpdateTimestampsCache:65 - Invalidating space [USERS], timestamp: 4967466866147328 For #3 Query: 06:54:25,368 DEBUG StandardQueryCache:156 - Checking query spaces for up-to-dateness: [USERS] 06:54:25,368 DEBUG UpdateTimestampsCache:86 - [USERS] last update timestamp: 4967466866147328, result set timestamp: 4967466865061888 06:54:25,368 DEBUG StandardQueryCache:113 - cached query results were not up to date For #4 Query (or any subsequent query for this matter): 06:54:25,368 DEBUG StandardQueryCache:156 - Checking query spaces for up-to-dateness: [USERS] 06:54:25,368 DEBUG UpdateTimestampsCache:86 - [USERS] last update timestamp: 4967466866147328, result set timestamp: 4967466865061888 06:54:25,368 DEBUG StandardQueryCache:113 - cached query results were not up to date Please note the timestamp numbers for #4 query - even though I would expect query to be re-cached in #3, it still shows old timestamp. So I may think that when re-caching a query it does not update cache entry timestamp which is not up-to-date due to save(). -- 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

15 years, 10 months

5
8
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 2010