May 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6962) java.util.zip.ZipException: error in opening zip file

by Jakub Białek (JIRA)

java.util.zip.ZipException: error in opening zip file ----------------------------------------------------- Key: HHH-6962 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6962 Project: Hibernate ORM Issue Type: Bug Components: entity-manager Affects Versions: 3.6.9 Environment: hibernate 3.6.9, spring 3.0.7.RELEASE, jboss 5.1, java 1.6.0_30 (sun), debian 64 bit Reporter: Jakub Białek Priority: Minor After moving from hibernate 3.6.8 to 3.6.9 below stacktrace has appeared in logs when application is deployed: {code} WARN [org.hibernate.ejb.packaging.FileZippedJarVisitor] (HDScanner) Unable to find file (ignored): vfszip:/srv/jboss-5.1.0.GA/server/debugprfile/deploy/mywar.war/WEB-INF/lib/domain.jar/ java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:127) at java.util.jar.JarFile.<init>(JarFile.java:135) at java.util.jar.JarFile.<init>(JarFile.java:72) at org.hibernate.ejb.packaging.FileZippedJarVisitor.doProcessElements(FileZippedJarVisitor.java:65) at org.hibernate.ejb.packaging.AbstractJarVisitor.getMatchingEntries(AbstractJarVisitor.java:146) at org.hibernate.ejb.packaging.NativeScanner.getFilesInJar(NativeScanner.java:192) at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:497) at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:851) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:594) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73) at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:225) ...... {code} Application deploys correctly but this error didn't appear in 3.6.8. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-7107) org.hibernate.test.locking.LockModeTest hangs on Sybase 15.5 and DB2-97

by Zbyněk Roubalík (JIRA)

org.hibernate.test.locking.LockModeTest hangs on Sybase 15.5 and DB2-97 ----------------------------------------------------------------------- Key: HHH-7107 URL: https://hibernate.onjira.com/browse/HHH-7107 Project: Hibernate ORM Issue Type: Bug Affects Versions: 4.0.1 Environment: Hibernate 4.0.1.Final-redhat-1, Sybase 15.5, DB2-97 Reporter: Zbyněk Roubalík When running Hibernate testsuite on Sybase 15.5 and DB2-97, it hangs in org.hibernate.test.locking.LockModeTest. Mostly testQuery() or testLoading() test. It is new test in 4.0.1 (HHH-5275). Red Hat internal lab: https://hudson.qa.jboss.com/hudson/view/Hibernate/view/Hibernate%20QA/job... https://hudson.qa.jboss.com/hudson/view/Hibernate/view/Hibernate%20QA/job... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3958) Superfluous generated updates cause Violation of UNIQUE KEY constraint

by Guenther Demetz (JIRA)

Superfluous generated updates cause Violation of UNIQUE KEY constraint ---------------------------------------------------------------------- Key: HHH-3958 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3958 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: 3.3.1 GA, SQLServer 2008 Reporter: Guenther Demetz Priority: Minor Attachments: Testcase.jar When deleting a entire closure of objects associated over @ManyToOne within one single transaction, then on commit the FlushEventListener creates update statements on objects which are going to be deleted anyway. These update statements seems not only be useless, in certain scenarios they lead to Constraint Violation Exceptions, see the example here: @Entity public class A { public A() { } @Id @GeneratedValue private long oid; } @Entity @Table(uniqueConstraints = {@UniqueConstraint(columnNames={"assA_oid"})}) public class B { public B() {}; @Id @GeneratedValue private long oid; @javax.persistence.ManyToOne protected A assA = null; } A a1 = new A(); em.persist(a1); A a2 = new A(); em.persist(a2); B b1 = new B(); b1.assA = a1; // set unique association B b2 = new B(); b2.assA = a2; // set unique association em.persist(b1); em.persist(b2); em.getTransaction().commit(); em.getTransaction().begin(); em.remove(a1); em.remove(a2); em.remove(b1); em.remove(b2); em.getTransaction().commit(); // p6spy report: // update B set assA_oid='',version=0 where oid=1 and version=0 // update B set assA_oid='',version=0 where oid=2 and version=0 --> this raises "Violation of UNIQUE KEY constraint on all DB's which don't allow multiple null values in a unique index See testcase in attachment -- 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

12 years, 1 month

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-578) Remove remaining references to slf4j

by Gunnar Morling (JIRA)

Remove remaining references to slf4j ------------------------------------ Key: HV-578 URL: https://hibernate.onjira.com/browse/HV-578 Project: Hibernate Validator Issue Type: Task Components: documentation, engine Affects Versions: 4.3.0.Beta1 Reporter: Gunnar Morling Assignee: Gunnar Morling Fix For: 4.3.0.CR1 With HV-481 we migrated to the JBoss Logging API. There are still some references to slf4j which should be removed now. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
9
0 / 0

[Hibernate-JIRA] Created: (HV-580) Remove deprecation of package org.hibernate.validator.group

by Gunnar Morling (JIRA)

Remove deprecation of package org.hibernate.validator.group ----------------------------------------------------------- Key: HV-580 URL: https://hibernate.onjira.com/browse/HV-580 Project: Hibernate Validator Issue Type: Task Components: engine Affects Versions: 4.3.0.CR1 Reporter: Gunnar Morling Assignee: Gunnar Morling Fix For: 4.3.0.Final The JavaDoc of the package {{org.hibernate.validator.group}} says that this package is deprecated and will be removed in the future. That's actually not correct as only the interface {{DefaultGroupSequenceProvider}} will be moved to the package {{org.hibernate.validator.spi.group}}, while the annotation type {{GroupSequenceProvider}} shall stay in {{org.hibernate.validator.group}}. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HV-568) Perform a profiling of the annotation processor code and make use of caching where appropriate

by Gunnar Morling (JIRA)

Perform a profiling of the annotation processor code and make use of caching where appropriate ---------------------------------------------------------------------------------------------- Key: HV-568 URL: https://hibernate.onjira.com/browse/HV-568 Project: Hibernate Validator Issue Type: Improvement Components: annotation-processor Reporter: Gunnar Morling Fix For: 4.3.0.CR1 Currently there is no caching in place in {{org.hibernate.validator.ap.util.ConstraintHelper}}. The AP would likely benefit from this as information such as supported data types, composing constraints etc. is retrieved repeatedly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
6
0 / 0

[Hibernate-JIRA] Created: (HV-577) Include javadoc jar in Maven repo

by Ben McCann (JIRA)

Include javadoc jar in Maven repo --------------------------------- Key: HV-577 URL: https://hibernate.onjira.com/browse/HV-577 Project: Hibernate Validator Issue Type: Improvement Reporter: Ben McCann Priority: Minor Please include the javadoc jar in the Maven repo. Most other projects do this (e.g. http://search.maven.org/#browse%7C-2106241761) Some IDEs provide better support with the javadoc jars present. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-1120) Create and provide a JBoss AS 7 module to use Hibernate Search in applications

by Emmanuel Bernard (JIRA)

Create and provide a JBoss AS 7 module to use Hibernate Search in applications ------------------------------------------------------------------------------ Key: HSEARCH-1120 URL: https://hibernate.onjira.com/browse/HSEARCH-1120 Project: Hibernate Search Issue Type: New Feature Reporter: Emmanuel Bernard -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-1123) referencedColumnName is being ignored for OneToOne mapping

by farhad ch (JIRA)

referencedColumnName is being ignored for OneToOne mapping ---------------------------------------------------------- Key: HSEARCH-1123 URL: https://hibernate.onjira.com/browse/HSEARCH-1123 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 4.1.0.Final Reporter: farhad ch Priority: Critical Using a soft key instead of FK is necessary for legacy DB's and currently 4.1.2 has issues with this. I am using: @OneToOne(fetch = FetchType.LAZY) @NotFound(action = NotFoundAction.IGNORE) @JoinColumns({ @JoinColumn(name = "id", referencedColumnName="houseId", nullable = true, insertable = false, updatable = false) }) public Child getChild(){ return this.child; } but SQL shows join is based on PK and not Soft Key "houseId" @OneToOne mapping will force a FK-PK relationship and ignores values for "referencedColumnName" attributes: Inspecting code from AnnotationBinder and OneToOne shows few FIXME and TODO tags like: //FIXME referencedColumnName ignored -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
3
0 / 0

[Hibernate-JIRA] Created: (HBX-1194) hibernate.hbm2ddl.auto=update works with multiple oracle schemas

by Vyacheslav (JIRA)

hibernate.hbm2ddl.auto=update works with multiple oracle schemas ---------------------------------------------------------------- Key: HBX-1194 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1194 Project: Hibernate Tools Issue Type: Bug Environment: <org.hibernate.core.version>3.6.8.Final</org.hibernate.core.version> <org.hibernate.entitymanager.version>3.6.8.Final</org.hibernate.entitymanager.version> <org.hibernate.validator.version>4.0.2.GA</org.hibernate.validator.version> Reporter: Vyacheslav if privileges are set hbm2ddl schema update searches for created tables in all db schemas which can be accessed, not only in current one. Don't create tables needed in current schema and fails to alter them. http://community.jboss.org/thread/175353?tstart=0 info level log viewing says during schema update that: table found: REALTY.DATA_EXCH_LOG table found: REALTY_NEW.FILES_AUD table found: SYSTEM.PROPERTIES_AUD table found: SYSTEM.REVISIONS Script see different database schemas and creating AUD tables in one schema scanning others: table found: REALTY.REF_RSR_ORDER_TYPES table found: REALTY_NEW.REF_RSR_ORDER_TYPES_AUD After hbm2ddl cannot find tables created in other schemas: Unsuccessful: alter table PROPERTIES_AUD add BASE_TYPE_ID number(10,0) not null Current schema is REALTY_NEW Very strange behaviour. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2012