February 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (BVAL-99) Implement type-safe ConstraintValidator resolution mechanism

by Emmanuel Bernard (JIRA)

Implement type-safe ConstraintValidator resolution mechanism ------------------------------------------------------------ Key: BVAL-99 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-99 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard I did implement the embryo that determine the type of a given ConstraintValidator See ValidatorTypeHelper class and its test. With this type, the algo needs to find the best matching ConstraintValidator for a given declaration. Here is a proposal: For a given type T when a constaint is applied, List all CV whose type U is such that U.isAssignableFrom(T) is true then for each element U of this list: - if another element in the list is such that U.isAssignableFrom(V), remove U if there is more than one remaining element => raise the AmbiguousException Also when a Constraint is analyzed, if 2 CV target the same type, an exception should be raised. -- 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, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3729) @AuditJoinTable annotation has no effect for embedded concrete subclasses of a MappedSuperClass

by Erik-Berndt Scheper (JIRA)

@AuditJoinTable annotation has no effect for embedded concrete subclasses of a MappedSuperClass ----------------------------------------------------------------------------------------------- Key: HHH-3729 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3729 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.4 Reporter: Erik-Berndt Scheper In the situation where I have a Person entity who has 2 different embedded addresses, like so: @Embedded @org.hibernate.envers.Audited @org.hibernate.envers.AuditJoinTable(name="JB_PSN_CORRESP_ADDRESS_AUD") private final List<CorrespondenceAdress> correspondenceAddresses; @Embedded @org.hibernate.envers.Audited @org.hibernate.envers.AuditJoinTable(name="JB_PSN_RESIDENTIAL_ADDRESS_AUD") private final List<ResidentialAdress> residentialAddresses; Where both CorrespondenceAdress and ResidentialAdress extend Address, which is an abstract MappedSuperclass @MappedSuperclass @org.hibernate.annotations.ForceDiscriminator @org.hibernate.envers.Audited public abstract class Adress I find that the AuditJoinTable annotation has no 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, 3 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3750) Allow dialects to handle difference in how Query.setFirstResult() should be interpreted

by Steve Ebersole (JIRA)

Allow dialects to handle difference in how Query.setFirstResult() should be interpreted --------------------------------------------------------------------------------------- Key: HHH-3750 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3750 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Specifically, it appears that some databases will interpret the number we bind as 0-based, while others interpret it as 1-based. We should allow Dialects to handle this difference. -- 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, 3 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2524) Criteria query with collection of values (Set<java.lang.String>)

by marco molinari (JIRA)

Criteria query with collection of values (Set<java.lang.String>) ---------------------------------------------------------------- Key: HHH-2524 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2524 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.2 Environment: Java VM : 1.5.0_07 DBMS : HSQLDB Hibernate: hibernate-3.2.2.ga Reporter: marco molinari Hi to all, I have a problem with Criteria query on collection of values. Below I wrote a piece of java code and a piece of Person.hbm.xml. I want to search all persons with the email addresses containing character '@'. I obtain an empty list of Person and the SQL created by Criteria seems not correct ( more or less ... WHERE lower(PERSON_ID) ? ). I search information inside Hibernate site and Hibernate book but I didn't found the solution. public class Person { private Long id; private Set<String> emailAddresses = new HashSet(); public Set<String> getEmailAddresses() { return emailAddresses; } public void setEmailAddresses(Set<String> emailAddresses) { this.emailAddresses = emailAddresses; } } public static void main(String[] args) { List<Person> list = session.createCriteria(Person.class) .add( Restrictions.ilike( "emailAddresses", "@", MatchMode.ANYWHERE ) ) .list(); } Piece of Person.hbm.xml: <set name="emailAddresses" table="'PERSON_EMAIL_ADDR'" inverse="true"> <key column="'PERSON_ID'"/> <element column="'EMAIL_ADDR'" type="java.lang.String" not-null="true"/> </set> -- 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, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-410) Current build.xml from v3_2_1_GA_CP have a broken junitsingle target

by Juraci Paixao Krohling (JIRA)

Current build.xml from v3_2_1_GA_CP have a broken junitsingle target -------------------------------------------------------------------- Key: EJB-410 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-410 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: EM-build.xml.diff When trying to run the junitsingle for test org.hibernate.ejb.test.packaging.JarVisitorTest, I figured out that this target was probably copy/paste from junit target, and while the junit target has changed since then, the junitsingle hasn't. So, the attached patch realigns them, making it work properly. Command used to test: ant -Dcommon.dir=../common-v3_2_1_GA_CP -Dhibernate-core.home=../core-Branch_3_2_4_SP1_CP -Dhibernate-core.jar=../core-Branch_3_2_4_SP1_CP/build/hibernate3.jar -lib lib clean junitsingle -Dtestname=org.hibernate.ejb.test.packaging.JarVisitorTest Before the patch: classpath problems, missing directories, and the test is not executed. After the patch: the test is executed. -- 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, 3 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3685) Sybase - SchemaImport cannot create stored procedures in chained transaction mode

by Gail Badner (JIRA)

Sybase - SchemaImport cannot create stored procedures in chained transaction mode --------------------------------------------------------------------------------- Key: HHH-3685 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3685 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Gail Badner In order to create a Sybase stored procedure that can be executed in a transaction (not autocommit), either: 1) the stored procedure needs to be created in a transaction or 2) the system stored procedure, sp_procxmode, has to be called (sp_procxmode <stored-proc-name> 'chained') SchemaExport executes DDL using autocommit, so Sybase stored procedures created with SchemaExport cannot be used in a transaction. It is not possible to run SchemaExport with autocommit=false. This causes the unit tests for Sybase stored procedures to fail with a message like: "Stored procedure 'simpleScalar' may be run only in unchained transaction mode. The 'SET CHAINED OFF' command will cause the current session to use unchained transaction mode.' A workaround is to add a <database-object> tag containing the command to change the stored procedure to chained mode. This tag needs to follow the tag that defines the new stored procedure. For example, adding the following after the definition of paramHandling in the mapping for SybaseCustomSQLTest will change the paramHandling stored procedure so that it can be used in a transaction. <database-object> <create> sp_procxmode paramHandling, 'chained' </create> <drop/> </database-object> -- 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, 3 months

1
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-112) rename @ReportAsViolationFromCompositeConstraint to @ReportAsSingleViolation

by Emmanuel Bernard (JIRA)

rename @ReportAsViolationFromCompositeConstraint to @ReportAsSingleViolation ---------------------------------------------------------------------------- Key: BVAL-112 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-112 Project: Bean Validation Issue Type: Improvement Components: ri-general, spec-general Affects Versions: 1.0 public draft Reporter: Emmanuel Bernard Fix For: 1.0 proposed final draft, 4.0.0.Alpha1 -- 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, 3 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2875) upgrade to cglib 2.2 (which uses the new asm 2 apis)

by Steve Ebersole (JIRA)

upgrade to cglib 2.2 (which uses the new asm 2 apis) ---------------------------------------------------- Key: HHH-2875 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2875 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Gail Badner Priority: Blocker Fix For: 3.2.6, 3.3 upgrade to cglib 2.2 (which uses the new asm 2 apis) -- 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, 3 months

5
13
0 / 0

[Hibernate-JIRA] Created: (HHH-3751) Enable Antlr tree parser tracing for HqlSqlWalker

by Steve Ebersole (JIRA)

Enable Antlr tree parser tracing for HqlSqlWalker ------------------------------------------------- Key: HHH-3751 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3751 Project: Hibernate Core Issue Type: Improvement Components: query-hql Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.2.x, 3.3.x -- 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, 3 months

1
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-28) Types should be determined at runtime

by Emmanuel Bernard (JIRA)

Types should be determined at runtime ------------------------------------- Key: BVAL-28 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-28 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard More specifically Person is a superclass of Customer Customer cust = ...; Validator<Person> personValidator = factory.getValidator(Person.class); personValidator.validate(cust); should return invalid constraints declared on Customer. -- 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, 3 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2009