January 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (METAGEN-5) Make the looging output configurable

by Hardy Ferentschik (JIRA)

Make the looging output configurable ------------------------------------ Key: METAGEN-5 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-5 Project: Hibernate StaticMetamodel Generator Issue Type: Task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Pass additional attribute to the processor to turn on/off the printing of debug statements via processingEnv.getMessager() -- 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

16 years, 2 months

2
7
0 / 0

[Hibernate-JIRA] Created: (METAGEN-21) Add @SupportedOptions annotation to annotation processor so that tools can query the processor for supported options

by Hardy Ferentschik (JIRA)

Add @SupportedOptions annotation to annotation processor so that tools can query the processor for supported options -------------------------------------------------------------------------------------------------------------------- Key: METAGEN-21 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-21 Project: Hibernate StaticMetamodel Generator Issue Type: Task Affects Versions: 1.0.0-Beta-2 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 1.0.0-Beta-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

16 years, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4847) In nested id generators, use the context aka idObject for set operation and the raw entity as input for generation

by Emmanuel Bernard (JIRA)

In nested id generators, use the context aka idObject for set operation and the raw entity as input for generation ------------------------------------------------------------------------------------------------------------------ Key: HHH-4847 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4847 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-3 Reporter: Emmanuel Bernard Fix For: 3.5.0-Beta-4 -- 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

16 years, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4843) org.hibernate.ejb.util.LogHelper assumes javax.persistence.spi.PersistenceUnitInfo#getProperties is never null

by Steve Ebersole (JIRA)

org.hibernate.ejb.util.LogHelper assumes javax.persistence.spi.PersistenceUnitInfo#getProperties is never null -------------------------------------------------------------------------------------------------------------- Key: HHH-4843 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4843 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Beta-3 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.0-Beta-4 org.hibernate.ejb.util.LogHelper simply tries to iterate javax.persistence.spi.PersistenceUnitInfo#getProperties without ever checking whether it is null. The spec does not mandate this to be non-null. -- 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

16 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4846) NPE in AbstractIdentifiableType.checkDeclaredVersion

by Scott Marlow (JIRA)

NPE in AbstractIdentifiableType.checkDeclaredVersion ---------------------------------------------------- Key: HHH-4846 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4846 Project: Hibernate Core Issue Type: Bug Components: metamodel Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 3.5.0-Beta-4 JBCTS-946 is about a test that causes NPE in AbstractIdentifiableType.checkDeclaredVersion Test is invoking EntityType.getDeclaredVersion with a parameter of Integer.class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4844) OracleDialect incorrectly maps timestamps and dates to Hibernate Date Type

by Brian (JIRA)

OracleDialect incorrectly maps timestamps and dates to Hibernate Date Type -------------------------------------------------------------------------- Key: HHH-4844 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4844 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-3 Environment: org.hibernate.dialect.OracleDialect Reporter: Brian OracleDialect maps an jdbc timestamp type to a hibernate date type, and maps by default, jdbc date type to hibernate org.hibernate.type.DateType. Hibernate Date Type translation uses ResultSet.getDate which means that time is truncated from the date. This is not what you want, you want to include the time. These should use a hibernate TypeStampType. This is what a java.util.Date mapping uses. Right now, you will get different results if running an sql query on the same table vs. a hibernate hql query, it will map to different types. Propose the OracleDialect class do this: registerColumnType( Types.DATE, Hibernate.TIMESTAMP.getName() ); registerColumnType( Types.TIMESTAMP, Hibernate.TIMESTAMP.getName() ); -- 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

16 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-1074) DelegatingReverseEngineeringStratey.columnToHibernateTypeName reports invalid values

by Joel Schuster (JIRA)

DelegatingReverseEngineeringStratey.columnToHibernateTypeName reports invalid values ------------------------------------------------------------------------------------ Key: HBX-1074 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1074 Project: Hibernate Tools Issue Type: Improvement Components: reverse-engineer Affects Versions: 3.2.1 Environment: MyEclipse w/ Hibernate rev engineering against Oracle 10g Reporter: Joel Schuster When implementing an extention to the [u]DelegatingReverseEngineeringStrategy [/u]the [u]columnToHibernateTypeName [/u]does not report the true value of the [b]precision [/b]and [b]scale [/b]column of the table description/definition. The method signature: [code]@Override public String columnToHibernateTypeName( TableIdentifier table, String columnName, int sqlType, int length, int precision, int scale, boolean nullable, boolean generatedIdentifier) {[/code] The precision and scale parameters are [b]int[/b]. If the values in the definition are [b]null[/b] the values reported here come out as DATA_LENGTH and 0. Not null. These parameters should be [b]Integer[/b] and be set to [b]null [/b]when applicable. -- 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

16 years, 2 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4842) Identifier rollback causes not null constraint violation

by Daniel Jabornig (JIRA)

Identifier rollback causes not null constraint violation -------------------------------------------------------- Key: HHH-4842 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4842 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.3.2 Environment: Hibernate 3.3.2, 3.3.1, Oracle 10.2.x Envers 1.2.2.GA-hibernate-3.3 Reporter: Daniel Jabornig Attachments: testcase.zip If identifier rollback is enabled, envers tries to insert null values in join table for delete cascaded unidirectional associations. config.setProperty("hibernate.use_identifier_rollback", "true"); The bug is reproducable with delete and and delete-orphan on update. See attached testcase. Forum Discussion: http://community.jboss.org/message/522202 -- 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

16 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (METAGEN-16) Code makes use of getAnnotation() instead of getAnnotationMirrors()

by Emmanuel Bernard (JIRA)

Code makes use of getAnnotation() instead of getAnnotationMirrors() ------------------------------------------------------------------- Key: METAGEN-16 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-16 Project: Hibernate StaticMetamodel Generator Issue Type: Bug Affects Versions: 1.0.0-Beta-3 Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik -- 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

16 years, 2 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-4736) Cannot pass ValidatorFactory into PersistenceProvider.createContainerEntityManagerFactory(PersistenceUnitInfo, Map)

by Mike Youngstrom (JIRA)

Cannot pass ValidatorFactory into PersistenceProvider.createContainerEntityManagerFactory(PersistenceUnitInfo, Map) ------------------------------------------------------------------------------------------------------------------- Key: HHH-4736 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4736 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Beta-2 Reporter: Mike Youngstrom The javadocs for PersistenceProvider.createContainerEntityManagerFactory(PersistenceUnitInfo, Map) says: If a Bean Validation provider is present in the classpath, the container must pass the ValidatorFactoryinstance in the map with the key "javax.persistence.validation.factory". However, all non string values are stripped from the provided Map by Ejb3Configuration.configure(PersistenceUnitInfo, Map):463, ConfigurationHelper.overrideProperties() making it impossible to pass a ValidatorFactory using the "map". Passing a ValidatorFactory into PersistenceProvider.createEntityManagerFactory(String, Map) works fine since Ejb3Configuration.configure(String, Map) doesn't strip all non Strings from the map. As a work around it appears a ValidatorFactory can be passed into the properties of the PersistenceUnitInfo. Thanks, Mike -- 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

16 years, 2 months

3
3
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 January 2010