December 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HV-251) ResourceMessageInterpolater - allow create with map of user resource bundles

by saki (JIRA)

ResourceMessageInterpolater - allow create with map of user resource bundles ----------------------------------------------------------------------------- Key: HV-251 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-251 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 4.0.0.GA Reporter: saki Priority: Minor Allow user to supply to message interpolator constructor map of resource bundles. Use case: supply resource bundles loaded from XML public ResourceBundleMessageInterpolator(Map<Locale, ResourceBundle> userSuppliedBundlesMap) { defaultLocale = Locale.getDefault(); this.userBundlesMap.putAll(userSuppliedBundlesMap); defaultBundlesMap.put( defaultLocale, ResourceBundle.getBundle( DEFAULT_VALIDATION_MESSAGES, defaultLocale ) ); -- 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, 7 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2997) LikeExpression case sensitive not working properly

by Adam Czysciak (JIRA)

LikeExpression case sensitive not working properly -------------------------------------------------- Key: HHH-2997 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2997 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.5 Environment: Hibernate 3.2.5 Reporter: Adam Czysciak Priority: Minor Attachments: LikeExpression.patch LikeExpression doesn't handle ignoreCase flag properly when it's set to false. Uses it to build correct sql "property like ?", but doesn't use the flag inside getTypedValues - produces always lowercase value to bind. Attached a patch for 3.2.5 -- 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, 7 months

6
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3159) Oracle 11g - desupport of oracle.jdbc.driver

by D. S. (JIRA)

Oracle 11g - desupport of oracle.jdbc.driver -------------------------------------------- Key: HHH-3159 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3159 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5GA, Oracle 11.1.0.6.0. Reporter: D. S. With Oracle 11g, the deprecated package oracle.jdbc.driver no longer exists and this causes issues with all OracleDialect classes making it impossible to use Hibernate. This issue affects all of the following classes: Oracle9iDialect.java Oracle9Dialect.java Oracle10gDialect.java The line error in question is: Class types = ReflectHelper.classForName("oracle.jdbc.driver.OracleTypes"); This simply needs to be changed to: Class types = ReflectHelper.classForName("oracle.jdbc.OracleTypes"); >From the Oracle 11g readme.txt "In Oracle JDBC release 9.0.1 customer use of the classes in that package was deprecated. A new package, oracle.jdbc, was introduced and customers were advised to begin using the interfaces and classes defined in oracle.jdbc. In every release since 9.0.1 we have encouraged customers to switch to oracle.jdbc and stated that oracle.jdbc.driver would be desupported. The time has come. Customer code that references oracle.jdbc.driver will not compile and will not execute in this and future releases of the Oracle JDBC drivers. Please use oracle.jdbc instead." 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, 7 months

10
15
0 / 0

[Hibernate-JIRA] Created: (HHH-3682) OracleDialect with oracle 11g

by akash (JIRA)

OracleDialect with oracle 11g ----------------------------- Key: HHH-3682 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3682 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.2.5 Environment: Oracle 10.2, weblogic 10.3 , java 1.6 , spring 2.0 Reporter: akash We are calling sql procedures using Hiberante and I have used OracleDialect9 as my hiberante dialect. These configuration is working fine in weblogic 8.1 but it's failing in weblogic 10.3 with exception "Caused by: java.lang.IllegalAccessException: Class org.hibernate.dialect.Oracle9Dialect can not access a member of class oracle.jdbc.driver.OracleTypes with modifiers "" " . I went through the dialect code and found that here is one line "Class types = ReflectHelper.classForName("oracle.jdbc.driver.OracleTypes");" to load OracleTypes where in oracle 11g they have depricated oracle.jdbc.driver package. Now since weblogic 10.3 internally comes with oracle 11g thin driver, hibernate is not able to find OracleTypes class. So what do u think what i should do to make this work ? Is there any dialect available which can support oracle 11g and solve this problem ? So should i created my own dialect and handle this issue ? -- 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, 7 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4112) HibernateProxy enhanced POJOs lose method annotations

by David Green (JIRA)

HibernateProxy enhanced POJOs lose method annotations ----------------------------------------------------- Key: HHH-4112 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4112 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.0.ga Reporter: David Green Using FetchType.LAZY on an association can result in POJO entities being enhanced via JavassistProxyFactory or CGLIBProxyFactory. The resulting class overrides all declared accessors and mutators (get/set methods) in the original POJO. Those overridden methods lose any annotations that were specified on the original POJO. The result is that unsuspecting code looking for annotations on POJO accessors won't find any annotations. For example, if I have an @Entity POJO called Resident, the following JUnit test will fail for both CGLIBProxyFactory and JavassistProxyFactory: {code:Java} public void testCGLibProxy() throws HibernateException, SecurityException, NoSuchMethodException { doTest(new CGLIBProxyFactory()); } public void testJavassistProxy() throws HibernateException, SecurityException, NoSuchMethodException { doTest(new JavassistProxyFactory()); } private void doTest(ProxyFactory proxyFactory) throws NoSuchMethodException { HashSet proxyInterfaces = new HashSet(); proxyInterfaces.add( HibernateProxy.class ); proxyFactory.postInstantiate("Resident", Resident.class, proxyInterfaces, Resident.class.getDeclaredMethod("getId"), Resident.class.getDeclaredMethod("setId",Long.class), null); HibernateProxy hibernateProxy = proxyFactory.getProxy(resident.getId(), session); assertTrue(hibernateProxy instanceof Resident); System.out.println("Hibernate proxy name: "+hibernateProxy.getClass().getName()); assertNotNull(Resident.class.getDeclaredMethod("getMaritalStatus").getAnnotation(Required.class)); assertNotNull(hibernateProxy.getClass().getDeclaredMethod("getMaritalStatus").getAnnotation(Required.class)); } {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, 8 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2575) Query results are mapped to object array incorrectly when there is column ambiguity and aliases are not used

by Mike Hoeffner (JIRA)

Query results are mapped to object array incorrectly when there is column ambiguity and aliases are not used ------------------------------------------------------------------------------------------------------------ Key: HHH-2575 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2575 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.2 Environment: Hibernate 3.2.2 + MySQL 5.0.22 + MySQL Connector/J 5.0.5. Reproduced with HSQLDB 1.8.0.7. Reporter: Mike Hoeffner Priority: Minor Attachments: ResultsNotEffectedByAliasesTest.java I had a SQL (not HQL) query that basically looked like this: select a.name, a.seq, b.name, b.seq from foo a, foo b; and I noticed that the results obtained through list() -> (Object[]) get(i) -> row[0], row[1], row[2], row[3] did not correspond to what I saw when manually running the query without Hibernate involved. row[2] always had the same values as row[0] and row[3] always had the same values as row[1]. When I tried adding aliases so that it became: select a.name as a_name, a.seq as a_seq, b.name as b_name, b.seq as b_seq from foo a, foo b; then the results matched what I expected. So having aliases in the SQL modified the results that were returned even though I was looking up the value from each column by its index / position instead of by its name / alias. Attached is a test case that will reproduce this. -- 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, 8 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-267) Enhance distribution jar to make it OSGi bundle

by Jaro Kuruc (JIRA)

Enhance distribution jar to make it OSGi bundle ----------------------------------------------- Key: HV-267 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-267 Project: Hibernate Validator Issue Type: Improvement Components: build Affects Versions: 4.0.1.GA Reporter: Jaro Kuruc Hi, please consider enhancing validator's maven build to produce OSGi compliant bundle by adding OSGi specific manifest headers. At the moment, there are 2 options to do that: 1. Felix Bundle Plugin http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html 2. SpringSource Bundlor http://static.springsource.org/s2-bundlor/1.0.x/user-guide/html/ch03s03.html Also, take a look at the bundle which has been produced by SpringSource http://www.springsource.com/repository/app/bundle/version/detail?name=com... -- 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, 8 months

2
10
0 / 0

[Hibernate-JIRA] Created: (ANN-507) @Digits(integerDigits, fractionalDigits)

by Emmanuel Bernard (JIRA)

@Digits(integerDigits, fractionalDigits) ---------------------------------------- Key: ANN-507 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-507 Project: Hibernate Annotations Type: New Feature Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Fix For: 3.2.2 @Digits(integerDigits=8, fractionalDigits=2) ensure that the number can be expressed with integerDigits digits and factionalDigits digits -- 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, 8 months

6
10
0 / 0

[Hibernate-JIRA] Created: (HV-254) Add section about ConstraintValidatorContext to documentation

by Hardy Ferentschik (JIRA)

Add section about ConstraintValidatorContext to documentation ------------------------------------------------------------- Key: HV-254 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-254 Project: Hibernate Validator Issue Type: Task Components: documentation Affects Versions: 4.0.0.GA Reporter: Hardy Ferentschik Fix For: 4.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

14 years, 8 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2661) Second-level cache is used after Session.setCacheMode(CacheMode.IGNORE)

by Anders Wallgren (JIRA)

Second-level cache is used after Session.setCacheMode(CacheMode.IGNORE) ----------------------------------------------------------------------- Key: HHH-2661 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2661 Project: Hibernate3 Issue Type: Bug Components: caching (L2) Affects Versions: 3.2.4.sp1 Environment: Windows Vista MySQL 5.0 Reporter: Anders Wallgren I'm doing some bulk importing and want to disable the L2 cache, so I call Session.setCacheMode(CacheMode.IGNORE) before doing any work. However, the entities I'm creating still end up in the cache. It seems that org.hibernate.action.CollectionAction isn't doing the correct check to determine when to cache -- it only check for the existence of a configured cache, but doesn't check whether caching is enabled in the session. For example, from CollectionAction.beforeExecutions: public final void beforeExecutions() throws CacheException { // we need to obtain the lock before any actions are // executed, since this may be an inverse="true" // bidirectional association and it is one of the // earlier entity actions which actually updates // the database (this action is resposible for // second-level cache invalidation only) if ( persister.hasCache() ) { final CacheKey ck = new CacheKey( key, persister.getKeyType(), persister.getRole(), session.getEntityMode(), session.getFactory() ); lock = persister.getCache().lock(ck, null); } } Shouldn't "if ( persister.hasCache() )" be persistence.hasCache && getSession.getCacheMode.isPutEnabled(), or something along those lines? -- 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, 8 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2009