April 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (BVAL-194) Invalid license info

by Stevo Slavic (JIRA)

Invalid license info -------------------- Key: BVAL-194 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-194 Project: Bean Validation Issue Type: Bug Affects Versions: 1.0 final Reporter: Stevo Slavic Priority: Minor validation-api-1.0.0.GA.pom declares Apache 2 as license but with invalid URL and license name is not standard. Please adjust license info in the pom to be as in [apache parent pom|http://repo1.maven.org/maven2/org/apache/apache/6/apache-6.pom] as this will improve how dependency to this project artifact is treated by all sorts of maven plug-ins and tools, like project info dependency report plugin, maven jboss license plugin, etc. So instead: {code} <licenses> <license> <name>Apache License, Version 2.0</name> <url>license.txt</url> </license> </licenses> {code} should be: {code} <licenses> <license> <name>The Apache Software License, Version 2.0</name> <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url> <distribution>repo</distribution> </license> </licenses> {code} -- 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

14 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (HV-280) Missing </code> element in Javadocs for ConstraintValidatorContext.ConstraintViolationBuilder.NodeContextBuilder

by Ed Burns (JIRA)

Missing </code> element in Javadocs for ConstraintValidatorContext.ConstraintViolationBuilder.NodeContextBuilder ---------------------------------------------------------------------------------------------------------------- Key: HV-280 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-280 Project: Hibernate Validator Issue Type: Bug Components: documentation Affects Versions: 4.0.2.GA Reporter: Ed Burns Assignee: Hardy Ferentschik Priority: Trivial ConstraintValidatorContext.ConstraintViolationBuilder.NodeContextBuilder - Interface in javax.validation Represent refinement choices for a node which is in an Iterator or Map. -- 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

14 years, 1 month

3
4
0 / 0

[Hibernate-JIRA] Created: (BVAL-206) Update pom to use the new distributationManagement information

by Hardy Ferentschik (JIRA)

Update pom to use the new distributationManagement information -------------------------------------------------------------- Key: BVAL-206 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-206 Project: Bean Validation Issue Type: Task Affects Versions: 1.0 final Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 1.1 This is just a build issue - http://community.jboss.org/wiki/MavenGettingStarted-Developers -- 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

14 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-212) Wrong closing </code> element in javadocs of BeanDescriptor

by Hardy Ferentschik (JIRA)

Wrong closing </code> element in javadocs of BeanDescriptor ----------------------------------------------------------- Key: BVAL-212 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-212 Project: Bean Validation Issue Type: Bug Components: spec-general Affects Versions: 1.0 final Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 1.1 -- 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

14 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-201) Fix typo in spec, chapter 4.4.3

by Gunnar Morling (JIRA)

Fix typo in spec, chapter 4.4.3 ------------------------------- Key: BVAL-201 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-201 Project: Bean Validation Issue Type: Improvement Components: spec-general Affects Versions: 1.0 final Reporter: Gunnar Morling Priority: Trivial In chapter 4.4.3 (http://people.redhat.com/~ebernard/validation/#d0e4480), fourth paragraph, it should be "Such an implementation is useful to let a custom ConstraintValidatorFactory delegate to the standard ConstraintValidatorFactory." instead of "Such an implementation is useful to let a custom ConstraintValidatorFactory delegate to the standard TraversableResolver." -- 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

14 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-550) Using Programamtic API, the document ID is not inherited

by Chaffotte (JIRA)

Using Programamtic API, the document ID is not inherited -------------------------------------------------------- Key: HSEARCH-550 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-550 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.2.0.Final Environment: Hibernate 3.5.1, hsqldb 1.8.0.7 Reporter: Chaffotte Priority: Minor Attachments: search.zip If the document id is not defined in the child class (which is persisted) but in the parent class, the following exception occurs: org.hibernate.HibernateException: could not init listeners at org.hibernate.event.EventListeners.initializeListeners(EventListeners.java:205) ... Caused by: org.hibernate.search.SearchException: No document id in: org.mycompany.hibernate.search.MySubClass ... I attached a simple example. It is a maven project which the test fails until the document id in the MySubClass class is not uncommented. -- 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

14 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5775) Support session filters in DML statements

by Jason Clawson (JIRA)

Support session filters in DML statements ----------------------------------------- Key: HHH-5775 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5775 Project: Hibernate Core Issue Type: Improvement Components: core, query-hql Reporter: Jason Clawson We are using filters to support multi-tenency, an approach alluded to in this recent blog post: http://in.relation.to/Bloggers/MultitenancyInHibernate. It works create for HQL selects but doesn't work for Updates / Deletes. Looking through the source code, this seems to have been a conscious choice as some comments indicate. If filters are meant to be used for multitenency, this seems to be the wrong choice. I would like to see session filters affect updates and deletes. This seems very logical because if I run the select: SELECT * FROM User which is affected by a filter and returns 2 users, and then execute DELETE FROM User which deletes all the users in the system--- thats not what I would expect to happen. I believe this will require modifications to HqlSqlWalker and the ANTLR script sql-gen.g. I am looking into what other modifications are necessary, but I would appreciate it if the Hibernate folks could take a look since they would be most familiar with the code and the decisions behind it. Thanks! -- 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

14 years, 1 month

3
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-471) Ability to "filter" entities from the search indexes

by Dobes Vandermeer (JIRA)

Ability to "filter" entities from the search indexes ---------------------------------------------------- Key: HSEARCH-471 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-471 Project: Hibernate Search Issue Type: New Feature Components: mapping Affects Versions: 3.1.1.GA Reporter: Dobes Vandermeer Priority: Minor In our system we have entities that are searched but not all of them are available for search - some of them are flagged as "removed". It would improve the efficiency of our search subsystem if we could implement a kind of "filter" that blocked these entities from being added to the search index, since we wouldn't have to make that a search term and our indexes would be somewhat smaller. -- 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

14 years, 1 month

5
31
0 / 0

[Hibernate-JIRA] Created: (HHH-5299) Multi-Level cascading of unsaved instances with bidirectional associations fails with TransientObjectException

by Carl-Eric Menzel (JIRA)

Multi-Level cascading of unsaved instances with bidirectional associations fails with TransientObjectException -------------------------------------------------------------------------------------------------------------- Key: HHH-5299 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5299 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: Tested with OracleXE and H2DB, Hibernate Core 3.3.2, Hibernate Entity Manager 3.4.0 Reporter: Carl-Eric Menzel Priority: Critical Attachments: 0001-fixed-no-cascading-check-to-also-accept-entities-wit.patch, cascadetest.zip Given the following classes (pseudocode, full source in the attached zipfile): Top { @OneToMany(cascade = { CascadeType.ALL }, mappedBy = "top") List<Middle> middles } Middle { @ManyToOne Top top @OneToOne(cascade = { CascadeType.ALL }) @JoinColumn(name = "BOTTOM_ID") Bottom bottom } Bottom { @OneToOne(mappedBy = "bottom") Middle middle } The following code fails on the second flush with a TransientObjectException: Top top = new Top(); em.persist(top); em.flush(); // top is now attached, status MANAGED Middle middle = new Middle(1l); middle.setBottom(new Bottom()); top.addMiddle(middle); Middle middle2 = new Middle(2l); middle2.setBottom(new Bottom()); top.addMiddle(middle2); // both middles and bottoms are transient but should be saved by cascade em.flush(); // boom! The relevant part of the error is: org.hibernate.TransientObjectException: object references an unsaved transient instance - save the transient instance before flushing: test.Bottom.middle -> test.Middle at org.hibernate.engine.CascadingAction$9.noCascade(CascadingAction.java:376) at org.hibernate.engine.Cascade.cascade(Cascade.java:163) The same code works without exception when using EclipseLink instead of Hibernate EntityManager, so I am assuming that the test code is valid. Some debugging revealed that CascadingAction.PERSIST_ON_FLUSH.noCascade() checks the inverse association from Bottom to Middle. It then calls a private method isInManagedState to verify that this association does not reference an unsaved instance. It does this by checking the entities EntityEntry.getStatus() value, which it expects to be MANAGED or READ_ONLY. At this time, however, the Middle instance is in the middle (no pun intended) of its own cascading save cycle and therefore its status is SAVING. This, to me, seems to be a valid session-attached status, so isInManagedState() should also accept this state. The attached patch against Hibernate Core 3.3.2 implements just that, and this change makes the above example code work as expected. The Hibernate test suite did not complain, so I am reasonably sure I did not break anything else. See also the attached cascadetest.zip for a ready-to-use testcase that demonstrates the error with Hibernate Core 3.3.2. Change the dependency in the supplied pom.xml to a patched version of Hibernate Core, and the test will no longer fail. Carl-Eric Menzel C1 SetCon GmbH -- 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

14 years, 1 month

6
18
0 / 0

[Hibernate-JIRA] Created: (HHH-4870) Cannot determine java-type from given member [null]

by Marcial Atienzar (JIRA)

Cannot determine java-type from given member [null] --------------------------------------------------- Key: HHH-4870 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4870 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Beta-4 Environment: jdk 6u18 glassfishv3 Reporter: Marcial Atienzar Attachments: eclipse.debug, Empre.java, Prcontra.java I've tested to migrate from hibernate 3.3.2 to 3.5.0 Beta4. I've remove all hibernate*.jar from classpath and add only de hibernate3.jar I've downloaded the source off hibernate-entitymanager to debug from eclipse. I've reached the class that has the error, but I don't know what can I do to resolve it. I'm doing something wrong? I attatch the sources of the classes that takes part on eclipse debug. I don't know how to attach a testcase. The project has more than 200 entities. I've post previously in hibernate forums: https://forum.hibernate.org/viewtopic.php?f=1&t=1002363&p=2424419#p2424419 -- 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

14 years, 1 month

9
60
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 April 2011