January 2011 - hibernate-dev - Jboss List Archives

Hibernate Validator 4.2.0 Beta1 with tons of new features

by Hardy Ferentschik

All you need to know on in.relation.to: http://in.relation.to/18074.lace --Hardy

13 years, 3 months

1
0
0 / 0

Re: [hibernate-dev] Pull request sent for HHH-3551

by Sanne Grinovero

hi Laird, sorry I just noticed that our thread fell of the mailing list, please keep everyone in CC as I'm not the most expert on these aspects. Did you get any results? Regards, Sanne 2011/1/6 Laird Nelson <ljnelson(a)gmail.com>: > This page shows the available drivers: > > http://www14.software.ibm.com/webapp/download/search.jsp?go=y&rs=ifxjdbc > > So it looks like I might be able to test this against 2.21JC4, but no > earlier. > > (Offhand, will Hibernate 3.6 even work with such an old JDBC driver?) > > L > > On Wed, Jan 5, 2011 at 7:49 PM, Laird Nelson <ljnelson(a)gmail.com> wrote: >> >> On Wed, Jan 5, 2011 at 7:07 PM, Sanne Grinovero >> <sanne.grinovero(a)gmail.com> wrote: >>> >>> Hi Laird, >>> thanks a lot for the patch. >>> I can't merge your patch right away as we need to check bits about >>> backwards compatibility; from the javadocs in InformixDialect I see >>> this dialect was initially created using Informix JDBC driver version >>> 2.21JC3: would it be possible for you to check if your patched Dialect >>> would still work using that older driver? >> >> Oof; I'll dig around, but that might be a bit hard to come by. >> >>> >>> That would greatly help as I don't have an Informix database at hand >>> right now. >> >> Me neither, actually. :-) But my colleagues do. >> >> Best, >> Laird > >

13 years, 3 months

2
1
0 / 0

PersistenceUtilHelper causing AccessControlException under SecurityManager

by Gunnar Morling

Hello, while running some tests of HV with a Java security manager enabled I stumbled upon a java.security.AccessControlException caused by org.hibernate.ejb.util.PersistenceUtilHelper#setAccessibility() due to a missing ReflectPermission. I think the call to setAccessible() should be executed using a PrivilegedAction similar to the implementation in org.hibernate.validator.util.ReflectionHelper#setAccessibility(). Should I add a JIRA ticket for this? Gunnar

13 years, 3 months

2
2
0 / 0

HHH-3551: Closed and rejected, but possibly still valid?

by Laird Nelson

Hello. We're running into http://opensource.atlassian.com/projects/hibernate/browse/HHH-3551. The original poster requested that this (ancient) bug be closed (which it was), because, apparently, a JDBC driver upgrade solved the problem. But I'm not sure. We seem to be running into the same issue using Hibernate 3.5.0 and the latest Informix JDBC driver (3.70.JC1). The analysis posted by the original poster seems also to be correct. Is this bug worth reopening? Is there a particular reason the InformixDialect does not return "t" and/or "f" for boolean string values? Thanks, Laird

13 years, 3 months

2
2
0 / 0

Executing Stored procdure through Hibernate

by karthick.gunasekaran＠wipro.com

Hi All, I want to execute the stored procedure throug hibernate, my stored procedure have two in parameter and one out parameter, any body help me please Thanks and Regards, Karthick G Mobile:9944369712 Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

13 years, 3 months

2
1
0 / 0

Pull request sent for HHH-3551

by Laird Nelson

Not sure whether it is appropriate to note it here, but in the interest of transparency: as part of my campaign to get http://opensource.atlassian.com/projects/hibernate/browse/HHH-3551 reopened and fixed, I've sent a github pull request with a patch that fixes the problem. Please kindly advise if I've either left something out or if there's another series of steps I need to go to to get HHH-3551 fixed. Thanks, Laird

13 years, 3 months

2
2
0 / 0

Review of HSEARCH-361 (don't index entity change

by Emmanuel Bernard

Hey guys to warm up in 2011, I've reviewed HSEARCH-361. I have two remarks Can you add a unit test that checks mutable properties. I think it's covered but let's plan for a later bug :) FullTextIndexEventListener compute the list of dirty properties by calling EntityPersister.findDirty(). I don't think that's entirely accurate. If you look when findDirty is called in Core, you'll see that we need to handle interceptors. Also in some cases we call findModified. The good news is that core computes and caches the list of dirty properties (in FlushEntityEvent.getDirtyProperties()). Now the even we receive in Hibernate Search is PostUpdateEvent. I think we can enhance Core to pass along the list of dirty properties. EntityUpdateAction.postUpdate / postCommitUpdate do create PostUpdateEvents and has the info (dirtyFields). Basically we could keep the existing half working impl in HSearch until Hibernate Core 3.6.1 and use the new exposed property of PostUpdateEvent if available (reflection call). To minimize the reflection call, we should ahve a strategy (ie pre 3.6.1 and post 3.6.1) and at startup time instantiate the correct one. WDYT?

13 years, 3 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-dev January 2011