May 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HV-571) Align method level validation w/ Bean Validation 1.1

by Hardy Ferentschik (JIRA)

Align method level validation w/ Bean Validation 1.1 ---------------------------------------------------- Key: HV-571 URL: https://hibernate.onjira.com/browse/HV-571 Project: Hibernate Validator Issue Type: Task Components: engine Reporter: Hardy Ferentschik Fix For: 5.x Currently HV offers method level validation via the _MethodValidator_ interface. This has to be aligned with BV 1.1 where the method level validation calls are part of _Validator_. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HV-583) Upgrade JBoss Logging dependency

by Gunnar Morling (JIRA)

Upgrade JBoss Logging dependency -------------------------------- Key: HV-583 URL: https://hibernate.onjira.com/browse/HV-583 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 4.3.0.Final Reporter: Gunnar Morling We should update to _org.jboss.logging:jboss-logging:3.1.1.GA_ and _org.jboss.logging:jboss-logging-processor:1.0.2.Final_ in order to make use of the {{NO_FORMAT}} option introduced with [LOGTOOL-45|https://issues.jboss.org/browse/LOGTOOL-45]. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HV-586) Hibernate validator initializes lazy proxies

by Michael G (JIRA)

Hibernate validator initializes lazy proxies -------------------------------------------- Key: HV-586 URL: https://hibernate.onjira.com/browse/HV-586 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.2.0.Final Environment: CentOs, Glassfish V3 Reporter: Michael G Priority: Critical I use hibernate validator for detached entities, some of them are not initialized. If they are not initialized imho there is no possibility that they could have been changed so that constraints might be broken. Although hibernate validator goes for them and I get LazyLoadingExceptions. Also this is a change to previous versions. Has that been done on purpose? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HV-590) Update copyright year in reference guide

by Gunnar Morling (JIRA)

Update copyright year in reference guide ---------------------------------------- Key: HV-590 URL: https://hibernate.onjira.com/browse/HV-590 Project: Hibernate Validator Issue Type: Bug Components: documentation Affects Versions: 4.3.0.Final Reporter: Gunnar Morling The reference guide still mentions "2009 - 2011" as copyright year. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-6632) Improve exception message when package-info / other file is missing @ metadatasources.buildMetadata()

by Elmer van Chastelet (JIRA)

Improve exception message when package-info / other file is missing @ metadatasources.buildMetadata() ----------------------------------------------------------------------------------------------------- Key: HHH-6632 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6632 Project: Hibernate Core Issue Type: Improvement Components: metamodel Affects Versions: 4.0.0.CR2 Reporter: Elmer van Chastelet While migrating our project to the new Hibernate Core 4.0, I came across an exception which was thrown during metadatasources.buildMetadata(). Emmanuel helped me to find the cause, which were the missing package-info.java files for the packages I add to the MetadataSources object. If possible, improve this exception message to include info about the file that fails to load. {code} Sep 5, 2011 4:17:46 PM org.apache.catalina.core.StandardWrapperValve invoke SEVERE: Allocate exception for servlet mainservlet java.io.IOException: Stream closed at java.io.BufferedInputStream.getInIfOpen(BufferedInputStream.java:151) at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) at java.io.BufferedInputStream.read1(BufferedInputStream.java:275) at java.io.BufferedInputStream.read(BufferedInputStream.java:334) at java.io.DataInputStream.readFully(DataInputStream.java:195) at java.io.DataInputStream.readFully(DataInputStream.java:169) at org.jboss.jandex.Indexer.verifyMagic(Indexer.java:387) at org.jboss.jandex.Indexer.index(Indexer.java:628) at org.hibernate.metamodel.source.annotations.AnnotationMetadataSourceProcessorImpl.indexClass(AnnotationMetadataSourceProcessorImpl.java:159) at org.hibernate.metamodel.source.annotations.AnnotationMetadataSourceProcessorImpl.prepare(AnnotationMetadataSourceProcessorImpl.java:85) at org.hibernate.metamodel.source.internal.MetadataImpl.prepare(MetadataImpl.java:180) at org.hibernate.metamodel.source.internal.MetadataImpl.<init>(MetadataImpl.java:165) at org.hibernate.metamodel.source.internal.MetadataBuilderImpl.buildMetadata(MetadataBuilderImpl.java:83) at org.hibernate.metamodel.MetadataSources.buildMetadata(MetadataSources.java:112) at utils.HibernateUtilConfigured.<clinit>(HibernateUtilConfigured.java:60) at utils.DispatchServlet.tryLoadGlobalsAndPerformInit(DispatchServlet.java:19) at utils.DispatchServlet.init(DispatchServlet.java:39) at javax.servlet.GenericServlet.init(GenericServlet.java:212) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:809) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at java.lang.Thread.run(Thread.java:679) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-7092) Create default name for foreign and unique key constraints

by Gail Badner (JIRA)

Create default name for foreign and unique key constraints ---------------------------------------------------------- Key: HHH-7092 URL: https://hibernate.onjira.com/browse/HHH-7092 Project: Hibernate ORM Issue Type: Task Components: metamodel Reporter: Gail Badner Fix For: 5.0.0 org.hibernate.mapping.Table.uniqueColumnString() generates a unique name based on hash codes. Will this method be used in the new metamodel or will some naming strategy be used as in HHH-3499? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
5
0 / 0

[Hibernate-JIRA] Created: (HHH-6354) Implement natural ID mapping

by Gail Badner (JIRA)

Implement natural ID mapping ---------------------------- Key: HHH-6354 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6354 Project: Hibernate Core Issue Type: Task Components: metamodel Reporter: Gail Badner Fix For: 4.0.0.next -- 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, 6 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4815) Support orphan-removal for one-to-one inside component/@Embeddable

by Steve Ebersole (JIRA)

Support orphan-removal for one-to-one inside component/@Embeddable ------------------------------------------------------------------ Key: HHH-4815 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4815 Project: Hibernate Core Issue Type: New Feature Components: core Reporter: Steve Ebersole Fix For: 3.5 AFAICT this only makes sense for fk-based logical 1-1. See HHH-4726 for more 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

12 years, 6 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HHH-6351) Enum Bug when using OK word inside of a enum being retrieved

by Lucas Arruda (JIRA)

Enum Bug when using OK word inside of a enum being retrieved ------------------------------------------------------------ Key: HHH-6351 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6351 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.6.5, 3.3.0.GA Environment: Hibernate version 3.3.0.GA, 3.6.5.Final with hibernate-annotations 3.4.0.GA. Oracle database. Reporter: Lucas Arruda Priority: Minor I have a class with a field which is an enum, which is mapped by a enum called Status. The class is described (simplified and without all annotations) above: public class A { private Status status; public enum Status { OK, NOK, NAP } @Column(name = "STATUS") @Enumerated(EnumType.STRING) public Status getStatus() { return status; } ... } The thing is. I can store a record from A with status = 'OK', 'NOK' or 'NAP' perfectly. But, when I try to retrieve that record, if status = 'NOK' or 'NAP' it works correctly, but no with status = 'OK', which gives me an exception: java.lang.IllegalArgumentException: Unknown name value for enum class com.a.b.c.d.A$Status: OK at org.hibernate.type.EnumType.nullSafeGet(EnumType.java:113) ... Caused by: java.lang.IllegalArgumentException: No enum const class com.a.b.c.d.A$Status.OK at java.lang.Enum.valueOf(Enum.java:196) at org.hibernate.type.EnumType.nullSafeGet(EnumType.java:110) Reported a StackOverflow [1] and now one could solve this using 'OK' in the Enum. What I did to solve this, since I couldn't get I done with OK, was to change a little bit the enum with this, which works correctly: public enum Status { _OK("OK"), NOK("NOK"), NAP("NAP"); private String desc; public String getDesc() { return desc; } private Status(String desc) { this.desc = desc; } } Since I couldn't make it work with 'OK', I highly suspect it's either a big mistake by my part or a bug, so I'm reporting it. [1] http://stackoverflow.com/questions/6432933/hibernate-jpa-bug-not-recogniz... -- 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, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-764) ClassBridge and DynamicBoost should report affecting properties

by Sanne Grinovero (JIRA)

ClassBridge and DynamicBoost should report affecting properties --------------------------------------------------------------- Key: HSEARCH-764 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-764 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero currently when a ClassBridge or a DynamicBoost many optimizations are disabled (especially dirty checking to skip indexing) as we don't know which properties might affect the index state. If these interfaces could define the properties they are interested in explicitly, we could make some progress in the area of optimizations. -- 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, 6 months

3
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2012