October 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HBX-893) "Can't create session factory" if any @NamedQuery annotations on entities have errors in them

by Joseph Marques (JIRA)

"Can't create session factory" if any @NamedQuery annotations on entities have errors in them --------------------------------------------------------------------------------------------- Key: HBX-893 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-893 Project: Hibernate Tools Type: Bug Versions: 3.2beta8 Reporter: Joseph Marques This seems to be a pretty big restriction - especially if you want to be able to cater to those that try to adopt Hibernate Tools part of the way through development, where some annotations may already have errors in them. Instead, it should be much more user-friendly to expand the session factory anyway, but just not load those entities - perhaps even marking them with a little red 'X' to indicate that the user needs to fix something in them. -- 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
5
0 / 0

[Hibernate-JIRA] Created: (ANN-597) @Index doesn't create multi-column indexes

by Christian Bauer (JIRA)

@Index doesn't create multi-column indexes ------------------------------------------ Key: ANN-597 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-597 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.0.ga Reporter: Christian Bauer Priority: Minor @org.hibernate.annotations.Index(name = "IDX_COMPONENT_PROPERTY_NAME", columnNames = {"COMPONENT_NAME", "PROPERTY_NAME"}) create index IDX_COMPONENT_PROPERTY_NAME on PREFERENCE (PROPERTY_NAME); -- 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

3
3
0 / 0

[Hibernate-JIRA] Created: (HBX-757) Add output file name, delimiter, halt on error, and format options to SchemaUpdate/<hbm2ddl>

by Dan Ports (JIRA)

Add output file name, delimiter, halt on error, and format options to SchemaUpdate/<hbm2ddl> -------------------------------------------------------------------------------------------- Key: HBX-757 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-757 Project: Hibernate Tools Type: Improvement Components: ant Versions: 3.2beta7 Reporter: Dan Ports Priority: Minor The file name, delimiter, halt on error, and format options are provided by SchemaExport/<hbm2ddl> already, so it makes sense to add their functionality to SchemaUpdate as well. I'll submit a patch shortly. (Is this the right place to post this, since SchemaUpdate is in the Hibernate core SVN?) -- 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

3
17
0 / 0

[Hibernate-JIRA] Created: (HHH-2310) LazyInitializationException: Initializing many-to-one and one-to-one associations to a maximum of max-fetch-depth fails when using a SQLProjection on a Criteria generated Query

by Nico De Groote (JIRA)

LazyInitializationException: Initializing many-to-one and one-to-one associations to a maximum of max-fetch-depth fails when using a SQLProjection on a Criteria generated Query -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2310 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2310 Project: Hibernate3 Type: Bug Components: core Versions: 3.0.5 Reporter: Nico De Groote Priority: Critical Initializing many-to-one and one-to-one associations to a maximum of max-fetch-depth fails when using a SQLProjection on a Criteria generated Query Following scenario occurs. I have a max-fetch-depth = default value. I have a the following businessobject having the following associations. BO -> BO2 (One to one) BO -> list of BO3 (one to many) I want to query for BO objects with the where clause containing a condition on one of the properties of the BO3 objects. When I now generate my query via the Criteria API and having the following projection set to retrieve only my BO objects (and none of the outer joinables) Projection projection = Projections.sqlProjection( "{alias}." + primaryKeyColumn + " theObj__", new String[]{"theObj__"}, new Type[]{Hibernate.entity(BO.getClass())}); I get my BO objects but the BO2 object is not initialized, as it should ne because of the max-fetch-depth. When not using the Projection I do get the one-to-one relation (BO2 object) as the max-fetch-depth is default value, but the query takes too much time because of the non required properties for the outerjoinable associations in the select clause. It seams that the fetching of the many-to-one and the one-to-one associations for the max-fetch-depth is disabled when using projections. Or am I missing the point here? -- 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, 11 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HV-42) Reference Documentation: broken example

by Robert Spielmann (JIRA)

Reference Documentation: broken example --------------------------------------- Key: HV-42 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-42 Project: Hibernate Validator Issue Type: Bug Components: documentation Reporter: Robert Spielmann Priority: Trivial The Hibernate Validator Reference Guide (Hibernate Validator 3.0.0.GA) contains examples for writing custom annotations and validators, section 1.4 "writing your own constraints". There, it says that the class CapitalizedValidator implements Validator<Capitalized> and PropertyConstraint. The example class, however, does not implement the "apply" method. Thus, the example class does not compile. Additionally, the class "Capitalize" (containing constants like FIRST) is not defined anywhere. This leaves the example incomplete and thus - unless you quickly implement this class - unsuable for practical experiments. -- 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, 11 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HV-25) Generated DDL ignores Validator annotations on component fields and superclass fields

by Ben Anderson (JIRA)

Generated DDL ignores Validator annotations on component fields and superclass fields ------------------------------------------------------------------------------------- Key: HV-25 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-25 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 3.0.0.ga Environment: Windows XP, Hibernate 3.2.4.sp1, Hibernate Annotations 3.3.0.ga, Postgres, HSQL Reporter: Ben Anderson Attachments: model.zip The DDL generated for entities containing components or superclass properties does not reflect any Validator length restrictions or not-null constraints that have been defined on those component or superclass properties i.e. a component with a property containing the @Length(max = 50) and @NotNull annotation is generated as varchar(255) with nulls permitted (at the database level). I've posted a more detailed example to the forum at http://forum.hibernate.org/viewtopic.php?t=975612 Another example can be found at http://www.ibm.com/developerworks/web/library/j-hibval.html - the SQL generated when this schema is exported is: create table cc (id integer not null, fname varchar(255), mi varchar(255), lname varchar(255), addr1 varchar(255), addr2 varchar(255), city varchar(255), zipcode varchar(255), state_id varchar(255), cvv2 varchar(6) not null, expiration_date timestamp not null, type_id integer not null, num varchar(30) not null, customer_id integer not null, primary key (id)); create table customer (id integer not null, dob timestamp, phone varchar(255), fax varchar(255), email varchar(255), fname varchar(255), mi varchar(255), lname varchar(255), addr1 varchar(255), addr2 varchar(255), city varchar(255), zipcode varchar(255), state_id varchar(255), primary key (id)); The SQL should be: create table cc (id integer not null, fname varchar(30) not null, mi varchar(1), lname varchar(30) not null, addr1 varchar(50) not null, addr2 varchar(50), city varchar(50) not null, zipcode varchar(15) not null, state_id varchar(2) not null, cvv2 varchar(6) not null, expiration_date timestamp not null, type_id integer not null, num varchar(30) not null, customer_id integer not null, primary key (id)); create table customer (id integer not null, dob timestamp, phone varchar(13), fax varchar(13), email varchar(40), fname varchar(30) not null, mi varchar(1), lname varchar(30) not null, addr1 varchar(50) not null, addr2 varchar(50) not null, city varchar(50) not null, zipcode varchar(15) not null, state_id varchar(2) not null, primary key (id)); I've attached the relevant classes from this example. -- 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, 11 months

6
7
0 / 0

[Hibernate-JIRA] Created: (HV-31) Support user defined Locale for the ResourceBundle

by Emmanuel Bernard (JIRA)

Support user defined Locale for the ResourceBundle -------------------------------------------------- Key: HV-31 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-31 Project: Hibernate Validator Issue Type: New Feature Components: engine 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-27) Accessing Public Methods In A Default Access Superclass

by Ilya Kharmatsky (JIRA)

Accessing Public Methods In A Default Access Superclass ------------------------------------------------------- Key: HV-27 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-27 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 3.0.0.ga Environment: pure jdk 5.0 Reporter: Ilya Kharmatsky Attachments: bugs.zip I'm not sure that this project is right place for this bug (probably better place is hibernate.annotations?), but since I've found the bug through hibernate.validator - I'm posting it here. In general, the problem is well-known and already resolved, for example here: http://jakarta.apache.org/commons/beanutils/apidocs/org/apache/commons/be... When I'm using the hibernate.validator on the application level (through test cases) I'm getting following error: java.lang.IllegalStateException: Could not get property value at org.hibernate.validator.ClassValidator.getMemberValue(ClassValidator.java:537) at org.hibernate.validator.ClassValidator.getInvalidValues(ClassValidator.java:383) at org.hibernate.validator.ClassValidator.getInvalidValues(ClassValidator.java:351) at bugs.HibenrateValidatorPackageAccessBug.testMyPojo2(HibenrateValidatorPackageAccessBug.java:47) Please see attached test 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, 11 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HV-22) Provide contextual validation

by Emmanuel Bernard (JIRA)

Provide contextual validation ----------------------------- Key: HV-22 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-22 Project: Hibernate Validator Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard The basic idea is to have a special parameter in annotations named context(s) @NotNull(message="doh", context = {"screen1Input", "screen2Input", "default"}) "default" being a special context, the one applied every time (including in the DDL) no context or an empty context is equivalent to "default" The regular API are running against "default" Override the regular APIs with getInvalidValues(..., String context); Not entirely sure the idea will float, but it sounds like a non invasive way to do it. PS this might require to create @[Name]s annotations ie @NotNulls({@NotNull(message="m1", context="earlyStage"), @NotNull(message="m2")}) -- 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, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HV-32) Provide a way to turn on recursive validation by default without @Valid needed

by Jacques Morel (JIRA)

Provide a way to turn on recursive validation by default without @Valid needed ------------------------------------------------------------------------------ Key: HV-32 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-32 Project: Hibernate Validator Issue Type: Improvement Reporter: Jacques Morel Hibernate validation annotation is a great way to specify declaratively and cohesively the validation rules of a domain model. Unfortunately it can also become very verbose. As any good frameworks, hibernate validator should provide ways to set sensible defaults. In the case of recursive validation, we should have a way to turn it one at the class level or at the ClassValidator level. -- 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, 11 months

4
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2007