December 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HV-396) Build for hibernate-validator module fails using Maven 3 due to problem with shade plugin

by Hardy Ferentschik (JIRA)

Build for hibernate-validator module fails using Maven 3 due to problem with shade plugin ----------------------------------------------------------------------------------------- Key: HV-396 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-396 Project: Hibernate Validator Issue Type: Bug Components: build Affects Versions: 4.1.0.Final Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.2.0.Beta1 {noformat} [INFO] Replacing /Users/hardy/work/hibernate/git/validator/hibernate-validator/target/hibernate-validator-4.2.0-SNAPSHOT.jar with /Users/hardy/work/hibernate/git/validator/hibernate-validator/target/hibernate-validator-4.2.0-SNAPSHOT-shaded.jar Downloading: http://repo1.maven.org/maven2/org/jboss/maven/plugins/maven-jdocbook-plug... [WARNING] The POM for org.jboss.maven.plugins:maven-jdocbook-plugin:jar:2.2.3 is missing, no dependency information available Downloading: http://repo1.maven.org/maven2/org/jboss/maven/plugins/maven-jdocbook-plug... Downloading: http://repo1.maven.org/maven2/org/hibernate/hibernate-jdocbook-style/2.0.... Downloading: http://repo1.maven.org/maven2/org/jboss/jbossorg-docbook-xslt/1.1.0/jboss... Downloading: http://repo1.maven.org/maven2/org/jboss/docs/highlight/1.0.0/highlight-1.... Downloading: http://repo1.maven.org/maven2/org/jboss/jbossorg-jdocbook-style/1.1.0/jbo... Downloading: http://repo1.maven.org/maven2/org/richfaces/docs/highlight/3.1.4.GA/highl... Downloading: http://repo1.maven.org/maven2/org/jboss/jbossorg-fonts/1.0.0/jbossorg-fon... [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 18.139s [INFO] Finished at: Wed Nov 17 12:04:13 CET 2010 [INFO] Final Memory: 12M/81M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:1.4:shade (default) on project hibernate-validator: Error creating shaded jar: 1 problem was encountered while building the effective model for org.hibernate:hibernate-validator:4.2.0-SNAPSHOT [ERROR] [ERROR] Unresolveable build extension: Plugin org.jboss.maven.plugins:maven-jdocbook-plugin:2.2.3 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.jboss.maven.plugins:maven-jdocbook-plugin:jar:2.2.3, org.hibernate:hibernate-jdocbook-style:jdocbook-style:2.0.1, org.jboss:jbossorg-jdocbook-style:jdocbook-style:1.1.0, org.jboss:jbossorg-docbook-xslt:jar:1.1.0, net.sf.docbook:docbook:jar:1.72.0, org.jboss.docs:highlight:jar:1.0.0, org.richfaces.docs:highlight:jar:3.1.4.GA, org.jboss:jbossorg-fonts:jdocbook-style:1.0.0: Could not find artifact org.jboss.maven.plugins:maven-jdocbook-plugin:jar:2.2.3 in central (http://repo1.maven.org/maven2) @ [ERROR] for project org.hibernate:hibernate-validator:4.2.0-SNAPSHOT at /Users/hardy/work/hibernate/git/validator/hibernate-validator/dependency-reduced-pom.xml for project org.hibernate:hibernate-validator:4.2.0-SNAPSHOT at /Users/hardy/work/hibernate/git/validator/hibernate-validator/dependency-reduced-pom.xml [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException {noformat} See also the Hudson build environment. The problem does not occur with Beta1 of Maven 3. Looking at the error message it seems that when the shading plugin tries to resolve the dependency maven-jdocbook-plugin it uses the wrong remote repository. -- 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

13 years, 4 months

1
7
0 / 0

[Hibernate-JIRA] Created: (HV-401) Ensure that the default validation provider is Hibernate Validator in LazyValidatorFactory

by Emmanuel Bernard (JIRA)

Ensure that the default validation provider is Hibernate Validator in LazyValidatorFactory ------------------------------------------------------------------------------------------ Key: HV-401 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-401 Project: Hibernate Validator Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard Assignee: 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

13 years, 4 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5773) Session grows with long running transactions, even when flushing and clearing regularly

by Emond Papegaaij (JIRA)

Session grows with long running transactions, even when flushing and clearing regularly --------------------------------------------------------------------------------------- Key: HHH-5773 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5773 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0 Reporter: Emond Papegaaij The session keeps track of all changes to entities in the 'actionQueue'. This ActionQueue contains a AfterTransactionCompletionProcessQueue, which grows rapidly with every change/insert/delete of entities. There seems to be no way to clear this queue, other than to commit or rollback. I can understand that Hibernate needs to keep track of changes in a transaction, but this list should not hold references to entities. Perhaps references can be replaced by lazy proxies? In our case, we are trying to import many (millions) records into the database. This needs to be performed in a single transaction. These records reference entities in a complex (and large) data-structure. The entities in this structure are not modified, but as the ActionQueue contains all newly inserted records, which in turn reference the entities in this structure, the entire structure ends up in the session. Flushing and clearing 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

13 years, 4 months

2
4
0 / 0

[Hibernate-JIRA] Commented: (HBX-120) Cannot Edit Existing Hibernate Console Configuration

by Stevo Slavic (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-120?page=co... ] Stevo Slavic commented on HBX-120: ---------------------------------- Maybe a view could be opened, if not already open, on first console configuration creation. > Cannot Edit Existing Hibernate Console Configuration > ---------------------------------------------------- > > Key: HBX-120 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-120 > Project: Hibernate Tools > Issue Type: Improvement > Components: eclipse > Affects Versions: 3.0alpha > Environment: Eclipse 3.1m4, Hibernate Tools 3.0 Alpha 1 > Reporter: Troy Harris > > I do not see a way to alter a console configuration which has already been created. This would be very useful. A user is currently has to select one by one, all of the hbm files needed for the particular configuration. If you need to add another directory to the classpath for that configuration once it has been created you must create an entirely different console configuration with a different name and reselect ALL of the hbm files again. This can be frustrating for a system with an extreme amount of tables. -- 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

13 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-546) Generate ant build file

by Vitali Yemialyanchyk (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-546?page=co... ] Vitali Yemialyanchyk commented on HBX-546: ------------------------------------------ now it is possible to generate ant build file in eclipse from hibernate codegen launch configuration. so the issue fixed. > Generate ant build file > ----------------------- > > Key: HBX-546 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-546 > Project: Hibernate Tools > Issue Type: New Feature > Components: eclipse > Reporter: George Lindholm > Priority: Minor > > It would be nice if an ant build file based on the eclipse settings could be generated > so that the generation process could be run from the command line. -- 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

13 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4539) Make UPPER and LOWER work on MS SQL Server text and ntext columns

by Sergiu Dumitriu (JIRA)

Make UPPER and LOWER work on MS SQL Server text and ntext columns ----------------------------------------------------------------- Key: HHH-4539 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4539 Project: Hibernate Core Issue Type: Improvement Components: query-sql Affects Versions: 3.3.2 Environment: MS SQL Server Reporter: Sergiu Dumitriu Trying to use UPPER or LOWER on a text column results in: ERROR util.JDBCExceptionReporter - Argument data type text is invalid for argument 1 of upper function. http://databases.aspfaq.com/database/why-do-i-get-argument-data-type-text... suggests a workaround, which I think should be automatically used by Hibernate, so that the HQL query can work with other dialects. -- 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

13 years, 4 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5726) SqlServerDialect should support variable limit

by Yoryos Valotassios (JIRA)

SqlServerDialect should support variable limit ---------------------------------------------- Key: HHH-5726 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5726 Project: Hibernate Core Issue Type: Bug Reporter: Yoryos Valotassios The SqlServerDialect using the row_number function can support variable limit. At the end of the query, instead of binding the limit and offset to the between statement just use ? -- 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

13 years, 4 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5725) SqlServerDialect should support SQL 2000 which does not support the row_number function

by Yoryos Valotassios (JIRA)

SqlServerDialect should support SQL 2000 which does not support the row_number function --------------------------------------------------------------------------------------- Key: HHH-5725 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5725 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0 Reporter: Yoryos Valotassios As a fix to HHH-2655 a patch has been applied to SQLServerDialect that make use of the row_number function for paged results. As I can see from the comments of SQLServerDialect, this dialect should be fine for sql server 2000, but sql server 2000 does not support row_number function. There should be a new dialect that extends the SQLServerDialect one which will add support for paged results throw the row_number function. -- 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

13 years, 4 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3965) Expose the ability to use varchar(max) or nvarchar(max)

by Ido Ran (JIRA)

Expose the ability to use varchar(max) or nvarchar(max) ------------------------------------------------------- Key: HHH-3965 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3965 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.4.0GA as provider for JPA 1.0 - SQL Server 2005 Database Reporter: Ido Ran Priority: Blocker I have an entity which needs to store long text field (at least 30,000 characters). I use SQL Server 2005 as back-end database. SQL Server varchar support up-to 8,000 characters in length of a field, or the reserved word MAX which indicate that the field length will be 2^31-1. I think that the class SQLServerDialect should be changed to have the following line in it's ctor: registerColumnType( Types.VARCHAR, 8001, "varchar(MAX)" ); this way, all String fields with length above 8000 will have varchar(MAX) as column type. -- 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

13 years, 4 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-517) ThreadLocal in ContextHolder causes memory leak when deployed in a web container

by Vojtěch Krása (JIRA)

ThreadLocal in ContextHolder causes memory leak when deployed in a web container -------------------------------------------------------------------------------- Key: HSEARCH-517 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-517 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.2.0.CR1, 3.2.0.Beta1, 3.1.1.GA, 3.1.0.GA, 3.1.0.CR1, 3.1.0.Beta2, 3.1.0.Beta1, 3.0.1.GA, 3.0.0.GA Environment: Hibernate 3.4.0.GA/3.5.1-Final, Tomcat 6.0.26, Spring 2.5.6/3.0.1, Sun JDK 1.6; Hibernate 3.3.1.GA Tomcat 6.0.18 Spring 2.5.6 Java OpenJDK 1.6 Reporter: Vojtěch Krása Priority: Critical Attachments: dump.zip, testCase.zip The SearchFactory has a static ThreadLocal variables which holds a reference to the SearchFactoryImpl. The ThreadLocal is not cleared when the application is undeployed, causing a memory leak. http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-314 -- 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

13 years, 4 months

4
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2010