December 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3950) org.hibernate.MappingException: Type not supported for auditing: org.hibernate.type.IdentifierBagType

by David Coleman (JIRA)

org.hibernate.MappingException: Type not supported for auditing: org.hibernate.type.IdentifierBagType ----------------------------------------------------------------------------------------------------- Key: HHH-3950 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3950 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.3.0.GA Environment: JBoss Envers: jboss-envers-1.2.0.GA-hibernate-3.3 from org.jboss.envers (not on 3.5 of hibernate core yet) Hibernate Core: hibernate-core-3.3.0.SP1.jar JBoss + Seam Reporter: David Coleman Attachments: TypeIdentifierBagTypeNotSupportedTrace.txt Hi, I currenty have a problem with auditing a many-many relation in the entity show below. Initially I had the exact same problem as ´http://opensource.atlassian.com/projects/hibernate/browse/HHH-3843´' but on reading the documentation and releazing that the list contains duplicate elements, I add (as suggested) a @CollectionId annotation to get bag semantics. Hoewever, the seam application fails to start-up due to the error being thrown from the envers module: "type not supported for auditing: org.hibernate.type.IdentifierBagType, on entity com.baratz.absys2.core.model.api.User, property 'roles'." (stack trace attached) <snippet> @Entity @Audited @Table(name = "USER_ABSYS") public class User { @UserRoles @ManyToMany @JoinTable(name = "USER_ROLE", joinColumns = @JoinColumn(name = "UUNSEQ",unique=false) , inverseJoinColumns = @JoinColumn(name = "ROLE_ID",unique=false)) @TableGenerator(name = "UserRolesGen", table = "ABSYS_SEQUENCE", pkColumnName = "ID_NAME", valueColumnName = "NEXT_VAL", pkColumnValue = "USER_ROLE_ID_GEN", allocationSize=1) @CollectionId( columns = @Column(name="USER_ROLE_IDX"), type=@Type(type="long"), generator="UserRolesGen" ) public List<Role> getRoles() { return roles; } ... } </snippet> Regards, Dave -- 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

11 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5869) Add suport for nationalized character mappings

by Steve Ebersole (JIRA)

Add suport for nationalized character mappings ---------------------------------------------- Key: HHH-5869 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5869 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Fix For: 4.0.0.Alpha1 Since Hibernate 4 will rely on JDBC 4 (JDK 1.6) we should add support for the JDBC 4 nationalized character types: * {{Types#NCHAR}} * {{Types#NVARCHAR}} * {{Types#NCLOB} * {{Types#LONGNVARCHAR}} -- 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

11 years, 10 months

5
23
0 / 0

[Hibernate-JIRA] Created: (ANN-819) @Any mapping fails during configuration: "@Any requires an explicit @JoinColumn(s)"

by Noah Miller (JIRA)

@Any mapping fails during configuration: "@Any requires an explicit @JoinColumn(s)" ----------------------------------------------------------------------------------- Key: ANN-819 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-819 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.GA, 3.4.0.CR2, 3.4.0.CR1, 3.3.1.GA Environment: Hibernate core 3.2.4.sp1 (reported in 3.3.1.GA as well) Hibernate annotations 3.3.1.GA (reported in 3.4.0.GA as well) Hibernate entity manager 3.3.1.ga MySQL 5.0.45 Reporter: Noah Miller When I try to apply the @Any annotation, I get the following exception: ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=persistence.units:jar=test-build.jar,unitName=blueserve state=Create org.hibernate.AnnotationException: @Any requires an explicit @JoinColumn(s): com.builderadius.blueserve.model.Note.noteOwner at org.hibernate.cfg.AnnotationBinder.processElementAnnotations(AnnotationBinder.java:1201) at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:739) at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:501) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:282) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1115) at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1195) at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:149) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:814) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:412) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:126) at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:259) See the forum posting http://forum.hibernate.org/viewtopic.php?p=2403045 for another description of this problem. That thread suggests the problem is with EJB3OverridenAnnotationReader not adding properties annotated with @JoinColumn if xml mapping files exist. My code is: @Any(metaColumn = @Column(name = "RelatedRecType")) @AnyMetaDef(idType = "integer", metaType = "string", metaValues = { @MetaValue(targetEntity = Approval.class, value = "approval"), @MetaValue(targetEntity = ZoningPermit.class, value = "zoningpermit") }) @JoinColumn(name = "RelatedRecNum", nullable = false) public BlueserveEntity getNoteOwner() { return this.noteOwner; } An orm.xml file (auto-generated by seam-gen) exists in this project, though it has no entity mappings and there are no other hbm.xml files. When I remove this file, I no longer receive the exception (that's not a long-term solution). -- 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

11 years, 10 months

5
5
0 / 0

[Hibernate-JIRA] Created: (BVTCK-11) Wrong usage of context classloader to discover resources in META-INF/services

by Hardy Ferentschik (JIRA)

Wrong usage of context classloader to discover resources in META-INF/services ----------------------------------------------------------------------------- Key: BVTCK-11 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVTCK-11 Project: Bean Validation TCK Issue Type: Bug Components: TCK Appeal Affects Versions: 1.0.4.GA Reporter: Hardy Ferentschik Assignee: Emmanuel Bernard *Problem Description*: The test uses the context classloader to discover all META-INF/services/javax.validation.spi.ValidationProvider resources and checks whether one of the resource files contains the ValidationProvider currently under the test. This method of checking for ValidationProvider might not work on all containers. Especially on containers with constrained classloaders (e.g. OSGi). The Bean Validation specification in section 4.4.4.1 talks about this exact problem. That's why the test should be using ValidationProviderResolver API to check for right provider instead of looking for the resource files. *Tests affected*: org.hibernate.jsr303.tck.tests.bootstrap.ValidationProviderResolverTest#testServiceFileExists() -- 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

11 years, 10 months

5
22
0 / 0

[Hibernate-JIRA] Created: (HHH-3238) impossible to get the rowcount for a criteria that has projections

by hbMailingList (JIRA)

impossible to get the rowcount for a criteria that has projections ------------------------------------------------------------------ Key: HHH-3238 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3238 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Environment: hibernate 3.2.6, oracle 10g Reporter: hbMailingList Projections.rowCount correctly returns the NUMBER_OF_ROWS for the criteria's resultset. However if the criteria already has a projection then rowcount no longer returns the NUMBER_OF_ROWS in the result set. For example: Criteria c=session.CreateCriteria(Cat.class); ProjectionList pl = ...; .... pl.add(Projections.groupProperty("color")); pl.add(Projections.rowCount()); c.setProjections(pl); c.list(); will result in the following query: select color, count(*) from cats group by color I would expect it to result in: select count(*) from (select color from cats group by color) after all if I wanted the count by color I could have simply done: Projections.count(...) I really need this feature for my project...if you don't think this will make the release, would you please give me a hint and I'll submit a patch. Thanks for all the hard work. -- 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

11 years, 10 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2218) java.util.ConcurrentModificationException at org.hibernate.pretty.Printer.toString(Printer.java:90)

by rm (JIRA)

java.util.ConcurrentModificationException at org.hibernate.pretty.Printer.toString(Printer.java:90) --------------------------------------------------------------------------------------------------- Key: HHH-2218 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2218 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: Hibernate 3.1.3, spring 2.1.8 on Jboss 4.0.2 with Oracle 10g Reporter: rm Similar issues have been logged since May 2005 and have been marked as 'Fixed' by Gavin especially for Session.toString() related cases. However, I am also facing similar issues in Printer.toString()... The saving grace is that when I set the debug level to INFO, the problem goes away... Am copy/pasting the relevent stacktrace...I have also debugged this on eclipse and the exact location is the call to "new Printer(....)" in AbstractFlushingEventListener.java java.util.ConcurrentModificationException 10:07:28,421 INFO [STDOUT] at java.util.HashMap$HashIterator.nextEntry(HashMap.java:787) 10:07:28,421 INFO [STDOUT] at java.util.HashMap$ValueIterator.next(HashMap.java:817) 10:07:28,421 INFO [STDOUT] at org.hibernate.pretty.Printer.toString(Printer.java:90) 10:07:28,421 INFO [STDOUT] at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:97) 10:07:28,421 INFO [STDOUT] at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:35) 10:07:28,421 INFO [STDOUT] at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:954) 10:07:28,421 INFO [STDOUT] at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1099) 10:07:28,421 INFO [STDOUT] at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) PS: This is my first attempt at logging issues at JIRA. Kindly point out any deficiencies or irregularities in this attempt. -- 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

11 years, 10 months

6
9
0 / 0

[Hibernate-JIRA] Created: (ANN-784) MapBinder.createFormulatedValue() does not honor DB schema name when creating query

by Sven Panko (JIRA)

MapBinder.createFormulatedValue() does not honor DB schema name when creating query ----------------------------------------------------------------------------------- Key: ANN-784 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-784 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.4.0.GA Environment: Hibernate 3.3.0.SP1, PostgresQL 8.3 Reporter: Sven Panko I detected a problem with a ManyToMany mapping using a Map in the following setup: @Entity @Table(name = "entitya", schema = "myschema") class EntityA { ... @ManyToMany(cascade = { CascadeType.PERSIST, CascadeType.MERGE }) @MapKey(name = "identifier") @JoinTable(name = "entitya_entityb", schema="myschema", joinColumns = @JoinColumn(name = "entitya_pk"), inverseJoinColumns = @JoinColumn(name = "entityb_pk")) @Cascade( { org.hibernate.annotations.CascadeType.SAVE_UPDATE, org.hibernate.annotations.CascadeType.DELETE_ORPHAN }) @Cache(usage = CacheConcurrencyStrategy.READ_WRITE) private Map<String, EntityB> entityBMap = new HashMap<String, EntityB>(); } @Entity @Table(name = "entityb", schema = "myschema") class EntityB { ... } The SQL generated to load the entityBMap collection contains a subquery in the select clause, which looks like this: select a8.identifier from entityb a8 where a8.pk=entityb0_.entityb_pk (entityb0_.entityb_pk comes from the outer select clause) The problem here is, that entityb in the from clause is not prepended by the schema name "myschema" (the outer query is correctly doing this in the join clause, however). I tracked this down to the createFormulatedValue() method in the MapBinder class; the responsible code snippet is contained in lines 292 - 296: StringBuilder fromAndWhereSb = new StringBuilder( " from " ) .append( associatedClass.getTable().getName() ) //.append(" as ") //Oracle doesn't support it in subqueries .append( " " ) .append( alias ).append( " where " ); associatedClass.getTable().getName() does not return the fully qualified table name, so I think this should look something like this: StringBuilder fromAndWhereSb = new StringBuilder( " from " ); if (associatedClass.getTable().getSchema() != null) { fromAndWhereSb.append(associatedClass.getTable().getSchema()).append('.'); } fromAndWhereSb.append( associatedClass.getTable().getName() ) //.append(" as ") //Oracle doesn't support it in subqueries .append( " " ) .append( alias ).append( " where " ); -- 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

11 years, 10 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-6736) Support for SELECT ... FOR UPDATE SKIP LOCKED / read past locking

by Aleksander Blomskøld (JIRA)

Support for SELECT ... FOR UPDATE SKIP LOCKED / read past locking ----------------------------------------------------------------- Key: HHH-6736 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6736 Project: Hibernate Core Issue Type: New Feature Components: core Reporter: Aleksander Blomskøld Hibernate does currently not support SKIP-LOCKED locking. Skip locked-semantics is useful in when having queue tables with several concurrent consumers. It is supported by Oracle (after 10g, documented in 11g), SQL Server (with the readpast hint), Sybase and possibly others. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HV-373) Investigate XML-based configuration of method-level constraints

by Gunnar Morling (JIRA)

Investigate XML-based configuration of method-level constraints --------------------------------------------------------------- Key: HV-373 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-373 Project: Hibernate Validator Issue Type: Sub-task Components: engine Reporter: Gunnar Morling Assignee: Gunnar Morling Fix For: 4.2.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

11 years, 10 months

2
11
0 / 0

[Hibernate-JIRA] Created: (BVAL-199) New convenience methods on Validator: void assertValid(Object o)/assertValidProperty(...)/assertValidValue(...) which throw a runtime ValidationException

by Geoffrey De Smet (JIRA)

New convenience methods on Validator: void assertValid(Object o)/assertValidProperty(...)/assertValidValue(...) which throw a runtime ValidationException --------------------------------------------------------------------------------------------------------------------------------------------------------- Key: BVAL-199 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-199 Project: Bean Validation Issue Type: New Feature Components: spec-general Affects Versions: 1.0 final Reporter: Geoffrey De Smet 90% of the time we want to do: {code} Set<ConstraintViolation<Car>> constraintViolations = validator.validate(car); if (constraintViolations.size() > 0) { throw new MyValidationException(decentErrorMessage); } {code} >From http://docs.jboss.org/hibernate/stable/validator/reference/en/html_single... So why not supply a facade method to make it easy for us developers (especially those migrating from hibernate validator 3)? {code} validator.assertValid(car); {code} That allows the bean validation to standarize the Exception too: a ValidationException (or InvalidStateException or whatever you call it), which is of course a runtime exception. That in turn, allows the front-end frameworks to deal with that exception more cleanly (give the user a clue why the business method failed when it imported that address without a street from an import addresses file). Give special care to the message of that exception. It should clearly state at least 1 of the validations that failed (in english, not i18n) so when we find such an exception in the log we can easily see what caused it. -- 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

11 years, 10 months

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2011