September 2010 - hibernate-issues

[Hibernate-JIRA] Created: (HV-327) Update TCK runner dependecies to not depend on the JBoss deprecated repo

by Hardy Ferentschik (JIRA)

Update TCK runner dependecies to not depend on the JBoss deprecated repo ------------------------------------------------------------------------ Key: HV-327 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-327 Project: Hibernate Validator Issue Type: Task Components: build, tck Affects Versions: 4.1.0.Beta1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.2.0 The current build for the tck runner module depends (transitively) on dependencies from the JBoss deprecated repository - https://repository.jboss.org/nexus/content/repositories/deprecated/ We should try if possible to avoid the usage of this repository. Not sure how far this is possible since it would require that there are properly configured upstream dependencies. -- 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, 5 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HV-363) HV uses Thread's context class loader to load internal implementation classes

by Sanjeeb Sahoo (JIRA)

HV uses Thread's context class loader to load internal implementation classes ----------------------------------------------------------------------------- Key: HV-363 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-363 Project: Hibernate Validator Issue Type: Bug Components: engine Reporter: Sanjeeb Sahoo Assignee: Hardy Ferentschik Priority: Blocker org.hibernate.validator.engine.resolver.DefaultTraversableResolver uses Thread's context class loader to load JPA_AWARE_TRAVERSABLE_RESOLVER_CLASS_NAME, which is org.hibernate.validator.engine.resolver.JPATraversableResolver. Why? Since one implementation class is looking for another implementation class, should it not use getClass().getClassLoader() instead? The relevant code is given below: private void detectJPA() { try { loadClass( PERSISTENCE_UTIL_CLASS_NAME, this.getClass() ); log.debug( "Found {} on classpath.", PERSISTENCE_UTIL_CLASS_NAME ); } catch ( ValidationException e ) { log.debug( "Cannot find {} on classpath. All properties will per default be traversable.", PERSISTENCE_UTIL_CLASS_NAME ); return; } try { @SuppressWarnings( "unchecked" ) Class<? extends TraversableResolver> jpaAwareResolverClass = (Class<? extends TraversableResolver>) loadClass(JPA_AWARE_TRAVERSABLE_RESOLVER_CLASS_NAME, this.getClass() ); NewInstance<? extends TraversableResolver> newInstance = NewInstance.action( jpaAwareResolverClass, "" ); if ( System.getSecurityManager() != null ) { jpaTraversableResolver = AccessController.doPrivileged( newInstance ); } else { jpaTraversableResolver = newInstance.run(); } log.info( "Instantiated an instance of {}.", JPA_AWARE_TRAVERSABLE_RESOLVER_CLASS_NAME ); } catch ( ValidationException e ) { log.info( "Unable to load or instanciate JPA aware resolver {}. All properties will per default be traversable.", JPA_AWARE_TRAVERSABLE_RESOLVER_CLASS_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, 6 months

5
13
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-524) Migrate unit tests to H2 (instead of HSQLDB) for inclusion in the Hudson train

by Emmanuel Bernard (JIRA)

Migrate unit tests to H2 (instead of HSQLDB) for inclusion in the Hudson train ------------------------------------------------------------------------------ Key: HSEARCH-524 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-524 Project: Hibernate Search Issue Type: Task Components: build Reporter: Emmanuel Bernard Fix For: 3.3.0 -- 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, 6 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5579) After upgrading from 3.3.2.GA to 3.5.6.Final receiving numerous ORA-00918: column ambiguously defined Exceptions

by Jeff Schenk (JIRA)

After upgrading from 3.3.2.GA to 3.5.6.Final receiving numerous ORA-00918: column ambiguously defined Exceptions ---------------------------------------------------------------------------------------------------------------- Key: HHH-5579 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5579 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.6 Environment: Hibernate 3.5.6, Spring 3.0.4.RELEASE, Oracle 11g2 Reporter: Jeff Schenk After upgrading from 3.3.2.GA to 3.5.6.Final receiving numerous ORA-00918: column ambiguously defined Exceptions. After research it appears to be linked to: Per HHH-951 setMaxResults causes "ORA-00918: column ambiguously defined" exception http://opensource.atlassian.com/projects/hibernate/browse/HHH-951 I removed the MaxResults projects as per HHH-951 and I was able to get past that one query, but had to back out until this regression is resolved. -- 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, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-424) Update to Lucene 3.0

by Sanne Grinovero (JIRA)

Update to Lucene 3.0 -------------------- Key: HSEARCH-424 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-424 Project: Hibernate Search Issue Type: Improvement Components: analyzer, directory provider, documentation, engine, mapping, query Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0.Beta2 Lucene 3.0 was released, update the dependencies and fix the code to work with the new APIs, to be able to make use of new features later. -- 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, 6 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5440) JPA 2.0 CriteriaBuilder API and CollectionOfElements

by Koen Molkenboer (JIRA)

JPA 2.0 CriteriaBuilder API and CollectionOfElements ---------------------------------------------------- Key: HHH-5440 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5440 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.4 Environment: hibernate-core 3.5.4, hibernate-entitymanager 3.5.4, hsqldb 2.0.0, mac os x 10.6, java 1.6.0_20 Reporter: Koen Molkenboer The situation is as follow: I have an User class which has a collection of elements which is a Set of Role enum values and I want to search for users which have one of more roles. I want to use the CriteriaBuilder, because I have a search form with a lot of fields which are optional. The User class: @Entity @Table(name = "USERS") @Access(AccessType.FIELD) public class User implements Serializable { @Id @GeneratedValue(strategy = GenerationType.AUTO) @Column(name = "ID") private Long id; @Column(name = "USERNAME", unique = true, nullable = false, length = 128) private String username; @ElementCollection @Enumerated(EnumType.STRING) @Column(name = "ROLE") @CollectionTable(name = "USER_ROLES", joinColumns = @JoinColumn(name = "USER_ID")) private Set<Role> roles = new HashSet<Role>(); ... } The enum Role: public enum Role { ROLE_1, ROLE_2, ROLE_3; } Creating the query with the CriteriaBuilder Set<Role> roles = new HashSet<Role>(); roles.add(Role.ROLE_1); roles.add(Role.ROLE_2); CriteriaBuilder criteriaBuilder = entityManager.getCriteriaBuilder(); CriteriaQuery<User> criteriaQuery = criteriaBuilder.createQuery(User.class); Root<User> root = criteriaQuery.from(User.class); criteriaQuery.where(root.join("roles").in(roles)); TypedQuery<User> query = entityManager.createQuery(criteriaQuery); query.getResultList(); This is the exception: java.lang.IllegalArgumentException: Parameter value [ROLE_2] was not matching type [java.util.Set] at org.hibernate.ejb.AbstractQueryImpl.registerParameterBinding(AbstractQueryImpl.java:360) at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:359) at org.hibernate.ejb.criteria.CriteriaQueryCompiler$1$1.bind(CriteriaQueryCompiler.java:194) at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:247) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:437) ... This all works with OpenJPA 2.0.0 -- 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, 6 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HV-365) It is very hard to find the HV annotation processor

by Emmanuel Bernard (JIRA)

It is very hard to find the HV annotation processor --------------------------------------------------- Key: HV-365 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-365 Project: Hibernate Validator Issue Type: Improvement Components: documentation Affects Versions: 4.1.0.Final Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik I was trying to find the HV annotation processor. I went to http://www.hibernate.org/subprojects/validator.html and its subspaces (esp download) where I saw no mention of it. I then went to read the documentation where I saw mention of it but no explanation on how to download it. It was hinted that the jar was inside the HV distribution but that does not seem to be the case. The only solution I've found was to go the the jboss mavne repo and manually dig it out. I think we should: - have a clearer doc on how to get it - bundle it with the distro - have a download link in the website - have a reference to it in the validator's home page -- 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, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2319) StatelessInterceptor

by Max Rydahl Andersen (JIRA)

StatelessInterceptor -------------------- Key: HHH-2319 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2319 Project: Hibernate3 Type: New Feature Components: core Versions: 3.2.1 Reporter: Max Rydahl Andersen It would make sense to have an Interceptor for StatelessSession to solve the following usecases: Log/adjust SQL: onPrepareStatement Proper entityname handling: instantiate/getEntity Maybe also tx interaction: afterTransationBegin/beforeTransactionCompletion/afterTransactionCompletion Technically it could be solved by just allowing to pass in a normal interceptor to a StatelessSession and just document that the state oriented callbacks will not be called. Alternatively we can create a StatelessInterceptor that only implement the releavant methods and wrap that instance into an internal Interceptor. -- 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, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4563) Maven repository uses proprietary JTA as transitive dependency

by Karel Piwko (JIRA)

Maven repository uses proprietary JTA as transitive dependency -------------------------------------------------------------- Key: HHH-4563 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4563 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.6 Reporter: Karel Piwko Transitive dependency javax.transaction:jta:jar:1.0.1B was removed from jboss reposories and it is to be replaced with jboss-transaction-api. <dependency> <groupId>org.jboss.javaee</groupId> <artifactId>jboss-transaction-api</artifactId> </dependency> Logs: Missing: ---------- 1) javax.transaction:jta:jar:1.0.1B Try downloading the file manually from: http://java.sun.com/products/jta Then, install it using the command: mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.transaction -DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.jboss.weld.integration:weld-jboss-int-jboss-ejb:jar:5.2.0-SNAPSHOT 2) org.jboss.ejb3:jboss-ejb3-endpoint-deployer:jar:0.1.3 3) org.jboss.ejb3:jboss-ejb3-core:jar:1.1.5 4) org.hibernate:hibernate:jar:3.2.6.ga 5) javax.transaction:jta:jar:1.0.1B ---------- 1 required artifact is missing. for artifact: org.jboss.weld.integration:weld-jboss-int-jboss-ejb:jar:5.2.0-SNAPSHOT from the specified remote repositories: apiviz.release (http://apiviz.googlecode.com/svn/site/repo/mvn/release), snapshots.jboss.org (http://snapshots.jboss.org/maven2), oss.sonatype.org/jboss-snapshots (http://oss.sonatype.org/content/repositories/jboss-snapshots), central (http://repo1.maven.org/maven2), repository.jboss.org (http://repository.jboss.org/maven2) This breaks a lot of builds. -- 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, 6 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HV-379) Remove obsolete dependecy exlusion from tck-runner pom

by Hardy Ferentschik (JIRA)

Remove obsolete dependecy exlusion from tck-runner pom ------------------------------------------------------ Key: HV-379 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-379 Project: Hibernate Validator Issue Type: Bug Components: tck-runner Affects Versions: 4.1.0.Final Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Priority: Minor Fix For: 4.2.0 {code} <exclusions> <exclusion> <groupId>org.hibernate</groupId> <artifactId>hibernate-entitymanager</artifactId> </exclusion> </exclusions> {code} Exclusion was needed for some earlier version of the jboss test harness -- 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, 6 months

1
2
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 September 2010