May 2010 - hibernate-issues - Jboss List Archives

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

by Strong Liu (JIRA)

Update pom to use the new distributationManagement information -------------------------------------------------------------- Key: HHH-5145 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5145 Project: Hibernate Core Issue Type: Task Components: build Reporter: Strong Liu Assignee: Strong Liu Priority: Minor Fix For: 3.5.x 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, 6 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5115) Migrate Annotations and EntityManager documentation system to jdocbook's maven plugin (like core)

by Emmanuel Bernard (JIRA)

Migrate Annotations and EntityManager documentation system to jdocbook's maven plugin (like core) ------------------------------------------------------------------------------------------------- Key: HHH-5115 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5115 Project: Hibernate Core Issue Type: Task Components: annotations, entity-manager Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik -- 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, 6 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5149) Move mapping documentation from Annotations to Core

by Emmanuel Bernard (JIRA)

Move mapping documentation from Annotations to Core --------------------------------------------------- Key: HHH-5149 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5149 Project: Hibernate Core Issue Type: Sub-task Components: documentation Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 3.6 -- 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, 6 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5150) Update settings section to reflect merge from Annotations and Core documentation

by Emmanuel Bernard (JIRA)

Update settings section to reflect merge from Annotations and Core documentation -------------------------------------------------------------------------------- Key: HHH-5150 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5150 Project: Hibernate Core Issue Type: Sub-task Reporter: 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

14 years, 6 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5094) PersistenceUtilHelper cannot access non-public fields/methods (it should be able to)

by Philip Clay (JIRA)

PersistenceUtilHelper cannot access non-public fields/methods (it should be able to) ------------------------------------------------------------------------------------ Key: HHH-5094 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5094 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Final Environment: 3.5.0-Final. Any environment Reporter: Philip Clay Attachments: hibernate-entitymanager-bugreproduction.tgz PersistenceUtilHelper is only able to access public fields and public methods. As it is written, it cannot access non-public members. Internally, it incorrectly uses Class.getField(...) and Class.getMethod(...). It should use Class.getDeclaredField(...) and Class.getDeclaredMethod(...), so that it can see non-public members. I believe the use of getField and getMethod is not indented, because setAccessibility is the next call after that. Here is the code... {code} private static Object get(Object proxy, String property) { final Class<?> clazz = proxy.getClass(); try { try { final Field field = clazz.getField( property ); // only retrieves public fields!!! setAccessibility( field ); // if you really only wanted public fields, this call is unnecessary! return field.get( proxy ); } catch ( NoSuchFieldException e ) { final Method method = getMethod( clazz, property ); if (method != null) { setAccessibility( method ); // if you really only wanted public methods, this call is unnecessary! return method.invoke( proxy ); } ... } private static Method getMethod(Class<?> clazz, String methodName) { try { char string[] = methodName.toCharArray(); string[0] = Character.toUpperCase( string[0] ); methodName = new String( string ); try { return clazz.getMethod( "get" + methodName ); // only retrieves public methods!!! } catch ( NoSuchMethodException e ) { return clazz.getMethod( "is" + methodName ); // only retrieves public methods!!! } ... } private static void setAccessibility(Member member) { if ( !Modifier.isPublic( member.getModifiers() ) ) { //Sun's ease of use, sigh... ( ( AccessibleObject ) member ).setAccessible( true ); // This is dead code! The input member will always be public } } {code} Notice the call to setAccessibility. The call to setAccessibility shows that one assumes that the field retrieved from getField() (or method from getMethod()) could be non-public, which in fact it can't. All fields returned from getField will always be public (same for getMethod()). So, essentially the code inside the if statement in setAccessibility is dead code. I have attached a tarball containing a failing testcase that shows the incorrect behavior. Explode the tarball and run "mvn test" to reproduce the incorrect behavior. Also, within the tarball, I have included an svn diff for a proposed patch. See the README.txt file within the tarball for more info. I first noticed this problem when using hibernate validator to validate some protected members, but I narrowed it down to a problem in PersistenceUtilHelper. -- 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, 6 months

5
9
0 / 0

[Hibernate-JIRA] Created: (HHH-4945) Replace all usages of EJB3TestCase with org.hibernate.ejb.test.TestCase

by Hardy Ferentschik (JIRA)

Replace all usages of EJB3TestCase with org.hibernate.ejb.test.TestCase ----------------------------------------------------------------------- Key: HHH-4945 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4945 Project: Hibernate Core Issue Type: Improvement Components: entity-manager Affects Versions: 3.5.0-CR-1 Reporter: Hardy Ferentschik Fix For: 3.5.x The setup in EJB3TestCase is really strange and we really want to have as many test as possible to derive from your main test base class. -- 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, 6 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3765) Fill the "end revision" column with appropriate data in add/mod/del/collection work units

by Adam Warski (JIRA)

Fill the "end revision" column with appropriate data in add/mod/del/collection work units ----------------------------------------------------------------------------------------- Key: HHH-3765 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3765 Project: Hibernate Core Issue Type: Sub-task Components: envers Reporter: Adam Warski Assignee: Adam Warski In case of modifications, not only the "end revision" column should be set on new data, but also modified on existing data. -- 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, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3764) Add the "end-revision" column when generating metadata

by Adam Warski (JIRA)

Add the "end-revision" column when generating metadata ------------------------------------------------------ Key: HHH-3764 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3764 Project: Hibernate Core Issue Type: Sub-task Components: envers Reporter: Adam Warski Assignee: Adam Warski The column would only be added if the necessary setting is set to true. The column will have the same type as the revision number, but will be nullable. -- 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, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5260) Tweak for query-cache via hibernate.hbm.xml needed

by Galder Zamarreno (JIRA)

Tweak for query-cache via hibernate.hbm.xml needed -------------------------------------------------- Key: HHH-5260 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5260 Project: Hibernate Core Issue Type: New Feature Components: caching (L2) Reporter: Galder Zamarreno Assignee: Galder Zamarreno >From Niktia Koksharov in https://jira.jboss.org/browse/ISPN-458: "In current implementation of hibernate-infinispan we can tune only entity and collection settings via hibernate.xml.cfg. But tuning in same way for queries needed too. In current version there are always the same cache region for all queries (look at org.hibernate.cache.infinispan.InfinispanRegionFactory.buildQueryResultsRegion) and it's incorrect. In org.hibernate.cache.infinispan.InfinispanRegionFactory.buildQueryResultsRegion Replace those lines: String cacheName = typeOverrides.get(QUERY_KEY).getCacheName(); CacheAdapter cacheAdapter = CacheAdapterImpl.newInstance(manager.getCache(cacheName)); To: Cache cache = getCache(regionName, QUERY_KEY, properties); CacheAdapter cacheAdapter = CacheAdapterImpl.newInstance(cache); " -- 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, 6 months

3
13
0 / 0

[Hibernate-JIRA] Created: (HHH-4568) Sybase - Test "BatchTest" fails due to "unexpected row count from update"

by Strong Liu (JIRA)

Sybase - Test "BatchTest" fails due to "unexpected row count from update" ------------------------------------------------------------------------- Key: HHH-4568 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4568 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-2, 3.5.0.Beta-1, 3.3.2, 3.2.4.sp1 Environment: Sybase Reporter: Strong Liu Assignee: Strong Liu Fix For: 3.2.x, 3.3.x, 3.5, 3.3.0.GA, 3.2.4.sp1 The test "BatchTest" fails due to "org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1". The database server seems configured properly, as the "BatchUpdates" sample from jConnect 6 works correctly. The problem specifically occurs with a table that has a numeric column with precision (e.g. numeric(10,4)) Sybase does not thrown any SQLException when you try and persist a numeric value whose scale exceeds that defined on the column. Instead, it returns an updateCount of zero -- 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, 6 months

3
9
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2010