March 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6007) Constraint violation when re-adding an entity to a one-to-many association in a recursive data structure (tree)

by Horst Sdun (JIRA)

Constraint violation when re-adding an entity to a one-to-many association in a recursive data structure (tree) --------------------------------------------------------------------------------------------------------------- Key: HHH-6007 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6007 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.2 Environment: Hibernate 3.6.2, JVM 1.6.0_23, Testet with Derby 10.7.1.1, Derby 10.6.2.1, HSQLDB 1.8.0.1 Reporter: Horst Sdun Priority: Minor Attachments: hibernate-test.zip i got an exception from the database when removing an unidirectional associated one-to-many entity and re-add it to another entity (of the same class as removed from) the attached example reproduces this. please execute org.sdun.hibernate.test.tree.TreeTest. ich have not found any contraindication for this case in the jpa 2.0 spec. (and i expected pojo behaviour :-) -- 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, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-408) c3p0 not working with hibernate-entitymanager 3.4.0.GA

by Marcelo Romulo Fernandes (JIRA)

c3p0 not working with hibernate-entitymanager 3.4.0.GA ------------------------------------------------------ Key: EJB-408 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-408 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.4.0.GA Environment: windows xp sp2; java sun 1.6.0_10; tomcat 6.0.18; maven 2.0.9 Reporter: Marcelo Romulo Fernandes Priority: Minor I was using hibernate-entitymanager 3.2.6.GA and c3p0 well, but I cannot run c3p0 with hibernate-entitymanager 3.4.0.GA. c3p0 is never called!!! Below, follows persistence.xml, maven dependencies working with hibernate-entitymanager 3.2.6.GA, maven dependencies not woking with hibernate-entitymanager 3.4.0.GA persistence.xml: <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="SystemDDD" transaction-type="RESOURCE_LOCAL"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <properties>  <property name="hibernate.connection.username" value="DDD"/> <property name="hibernate.connection.password" value="DDD"/> <property name="hibernate.default_schema" value="DDD"/> <property name="hibernate.connection.url" value="jdbc:oracle:thin:@//YYY:1521/ZZZ"/> <property name="hibernate.connection.driver_class" value="oracle.jdbc.OracleDriver"/> <property name="hibernate.dialect" value="org.hibernate.dialect.OracleDialect"/>  <property name="hibernate.c3p0.min_size" value="1"/> <property name="hibernate.c3p0.max_size" value="10"/> <property name="hibernate.c3p0.timeout" value="5000"/> <property name="hibernate.c3p0.max_statements" value="50"/> <property name="hibernate.c3p0.idle_test_period" value="60000"/>  <property name="hibernate.cache.use_second_level_cache" value="true"/> <property name="hibernate.cache.provider_class" value="org.hibernate.cache.EhCacheProvider"/>  <property name="hibernate.show_sql" value="true"/> <property name="hibernate.format_sql" value="true"/> <property name="hibernate.archive.autodetection" value="class, hbm"/> <property name="hibernate.hbm2ddl.auto" value="none"/> </properties> </persistence-unit> </persistence> maven dependencies working with hibernate-entitymanager 3.2.6.GA <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-entitymanager</artifactId> <version>3.3.2.GA</version> <type>jar</type> <scope>compile</scope> </dependency> <dependency> <groupId>c3p0</groupId> <artifactId>c3p0</artifactId> <version>0.9.1.2</version> <type>jar</type> <scope>compile</scope> </dependency> maven dependencies not woking with hibernate-entitymanager 3.4.0.GA <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-entitymanager</artifactId> <version>3.4.0.GA</version> <type>jar</type> <scope>compile</scope> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-ehcache</artifactId> <version>3.3.0.SP1</version> <type>jar</type> <scope>runtime</scope> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <version>1.5.2</version> <type>jar</type> <scope>runtime</scope> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-c3p0</artifactId> <version>3.3.0.SP1</version> <type>jar</type> <scope>runtime</scope> </dependency> What is wrong or missing? -- 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, 2 months

7
9
0 / 0

[Hibernate-JIRA] Created: (HHH-3572) Create versioned entities groups

by Adam Warski (JIRA)

Create versioned entities groups -------------------------------- Key: HHH-3572 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3572 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Adam Warski http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136878 Each group would have its own versions table. This could speed up the system when there are a lot of versioned entities, as the versions tables would be less contested. However, if two versioned entities are connected by a (versioned) relation, they would have to be in the same group. So groups could minimally be strongly connected components of the relations graphs. -- 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, 2 months

2
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1123) Cannot put more than 1000 elements in a InExpression

by Frank Klein Koerkamp (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1123?page=c... ] Frank Klein Koerkamp commented on HHH-1123: ------------------------------------------- Is it not possible to create a temporary table of al in's and join on that? > Cannot put more than 1000 elements in a InExpression > ---------------------------------------------------- > > Key: HHH-1123 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1123 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Affects Versions: 3.1 rc2, 3.2.0.alpha1 > Environment: Oracle 9i > Reporter: Alexis Seigneurin > Assignee: Strong Liu > Attachments: Animal.hbm.xml, hibernate-inexpression-oracle-3.2.patch, HQLHelper.java, LongInElementsTest.java, patch.txt > > Original Estimate: 1h > Remaining Estimate: 1h > > The number of elements that we can put in a "in" expression is limited to a certain amount (1000 for Oracle, for instance). When creating a criteria query, the org.hibernate.criterion.InExpression class should split the expression into several smaller ones. > Attached is a patch which splits the expression by slices of 500 elements. For example, if we have 1001 elements to put in the "in" expression, the result would be : > (entity.field in (?, ?, ?...) or entity.field in (?, ?, ?...) or entity.field in (?)) > The surrounding parantheses are useful to avoid problems with other conditions (a "and" condition taking over the one of the "or" conditions). -- 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, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-6004) StructuredCacheEntry shall pass correct expected map size and loadFactor for HashMap constructor

by Sergey Vladimirov (JIRA)

StructuredCacheEntry shall pass correct expected map size and loadFactor for HashMap constructor ------------------------------------------------------------------------------------------------ Key: HHH-6004 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6004 Project: Hibernate Core Issue Type: Improvement Components: caching (L2) Affects Versions: 3.6.0 Reporter: Sergey Vladimirov There is a code in StructuredCacheEntry::structure that supposed to optimize usage of HashMap and not allow resizing of HashMap. But it doesn't work. To check put a breakpoint at hashmap::resize and call for StructuredCacheEntry::structure method: at java.util.HashMap.resize(HashMap.java:462) at java.util.HashMap.addEntry(HashMap.java:755) at java.util.HashMap.put(HashMap.java:385) at org.hibernate.cache.entry.StructuredCacheEntry.structure(StructuredCacheEntry.java:67) at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:195) at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:982) I believe the line Map map = new HashMap(names.length+2); shall be rewritten as Map map = new HashMap(names.length+3, 1.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

13 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-695) Remove deprecated constructor form DocumentExtractor

by Sanne Grinovero (JIRA)

Remove deprecated constructor form DocumentExtractor ---------------------------------------------------- Key: HSEARCH-695 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-695 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Trivial Fix For: 3.4.0.Beta1 Basically, revert HSEARCH-694 (and check Infinispan Query build fine) -- 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, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-407) Update "Presentation layer validation" section

by Daniel Teleginski Camargo (JIRA)

Update "Presentation layer validation" section ---------------------------------------------- Key: HV-407 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-407 Project: Hibernate Validator Issue Type: Improvement Components: documentation Affects Versions: 4.1.0.Final Environment: not important Reporter: Daniel Teleginski Camargo Priority: Minor Hi, I believe that would be important to update the section "6.4. Presentation layer validation" letting it mention that the key: javax.faces.validator.BeanValidator.MESSAGE={0} {1} Can be placed inside the Message Bundle file to improve the way that messages will be displayed for JSF2. {0} is the message acquired from the Validator. {1} is the label of the field with validation error. This could also be done by adding a TIP to section 6.4. Thank you and congratulations for this amazing tool. -- 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, 2 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HV-449) Remove interface check in BeanMetaDataImpl#newGroupSequenceProviderInstance()

by Kevin Pollet (JIRA)

Remove interface check in BeanMetaDataImpl#newGroupSequenceProviderInstance() ----------------------------------------------------------------------------- Key: HV-449 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-449 Project: Hibernate Validator Issue Type: Improvement Affects Versions: 4.2.0.Beta2 Reporter: Kevin Pollet Priority: Trivial Fix For: 4.2.0.CR1 By removing the interface check in {{BeanMetaDataImpl#newGroupSequenceProviderInstance()}}, the behavior will be consistent. Consequently, an invocation of this method will throw an {{InstantiationException}} if the provider class (not limited to this case): * is an {{interface}} * is an {{abstract}} class * doesn't provide a default constructor -- 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, 2 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5767) Add running test information to Infinispan 2LC build

by Galder Zamarreno (JIRA)

Add running test information to Infinispan 2LC build ---------------------------------------------------- Key: HHH-5767 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5767 Project: Hibernate Core Issue Type: Task Components: build Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.Alpha1 Add some logging to Infinispan gradle build to show tests being executed, i.e. test { afterTest { desc, result -> println "Executing test ${desc.name} [${desc.className}] with result: ${result.resultType}" } } -- 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, 2 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HV-448) Regression in beta2

by David J. M. Karlsen (JIRA)

Regression in beta2 ------------------- Key: HV-448 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-448 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.2.0.Beta2 Reporter: David J. M. Karlsen Attachments: DummyBean.java, DummyServiceImpl.java, ValidationAspectTest.java The attached test and aspect used to pass just fine - but now fails with beta2. -- 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, 2 months

3
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2011