November 2014 - hibernate-dev - Jboss List Archives

by Sujit.Dhaygude＠sungard.com

Hi , we have a requirement to point a record for which the actual batch flush/commit has failed. Is there a generic way by which hibernate can be hooked up for exception scenario to pull back the actual entity for which DB/Hibernate Error has occurred . Most of the times we could see the hibernate is printing the error in logs which has entity ID but which is not consistent. Currently we are planning to use the Pre and Post (insert/Update/Delete) event handlers to retain the entities in Thread local and display those in case of error, but these listeners will intercept all the DB operation irrespective of success/failure . I am looking for a solution which will not impact the overall application performance and only in case of exception we need the details of entity. Regards, Sujit

11 years, 11 months

3
2
0 / 0

Hibernate invkoing onFlushDirty for umodified objects in Set

by Nitin G. Prabhu

Hi All, I have a object with below relationship public class A { @Id @SequenceGenerator(name = "ID_GENERATOR", sequenceName = "Id_SEQ", allocationSize = 1) @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "ID_GENERATOR") @Column(name = "id") private BigDecimal id; @OneToMany(mappedBy = MST, orphanRemoval = true, cascade = { CascadeType.ALL}) @OrderBy("id DESC") private List<B> b = new ArrayList<B>(); @Column(name = "name") private String name; } When I modify class A'S SAY name attribute and say dao.persist(A) then onFlushDirty()[overridden in my Hibernate interceptor] is also invoked even if B object is not modified I am not understanding why hibernate is treating List<B> objects to be dirty when I am trying to save the parent object A Regards, Nitin MASTEK LTD. In the US, we're called MAJESCOMASTEK ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited, unless specifically indicated to that effect. Mastek Limited does not accept any responsibility or liability for it. This e-mail and attachments (if any) transmitted with it are confidential and/or privileged and solely for the use of the intended person or entity to which it is addressed. Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. This e-mail and its attachments have been scanned for the presence of computer viruses. It is the responsibility of the recipient to run the virus check on e-mails and attachments before opening them. If you have received this e-mail in error, kindly delete this e-mail from desktop and server. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

11 years, 11 months

1
0
0 / 0

Session factory name & clustering

by Galder Zamarreño

Hi all, Re: http://stackoverflow.com/questions/26110918/infinispan-marshalling-error-... Re: https://github.com/hibernate/hibernate-orm/pull/820 Seems like the issue is resolved by making sure Session Factories have the same name. Is this something new? I’ve never had the need to set it in order to get Hibernate 2LC clustered tests working. None of my unit tests set the session factory name. One of my most recent demos uses JPA, and never had to set hibernate.session_factory_name property. Or is this due to the peculiarity of the Entity the user has? I’ve run some tests locally and SessionFactoryImpl.readResolve() does not seem to get called. @Paul/@Scott, have you seen anything similar before? Cheers, -- Galder Zamarreño galder(a)redhat.com twitter.com/galderz

11 years, 11 months

3
2
0 / 0

ORM build - IDE imports

by Steve Ebersole

I have been thinking of ways to make importing ORM into IDE more transparent. My thinking is from the IntelliJ pov and the specific issues I have run into there. I wanted to run my thoughts past y'all to see if they helped with Eclipse and/or other IDEs. ----- The main thing I see is trouble with the generated-src dir. IntelliJ automatically "excludes" the build directory which is actually perfect, generally speaking. However, we put generated-src under the build dir so it gets excluded by extension as well. That's why after import we need to adjust excluded dirs and source dirs. My suggestion here is to move generated-src out from under the build dir, making it on level with src and target. So we'd have: {projectRoot} +- generated-src +- src \- target generated-src and target would both be directories that are created by the build and are git-ignored. The point being that IntelliJ would still exclude target as the main build dir, but generated-src is no longer under that dir and would not be excluded. In my experience the import marks the generated source dirs properly other than them being transitively excluded. ---- A related issue is the execution of source generators. This has already been partially been addressed. Today we have a split between: 1) source generators that generate sources required at compile time (antlr, jaxb, jpa-metamodel-gen, etc) 2) source generators that generate sources required at run time (currently only logging). There is also a concern here between AP-based generators and non-AP-based generators. And unfortunately they split across the compile/run time requirement. I am not really sure of an ideal solution here. And the situation is compounded by the fact that IntelliJ won't let us apply annotation processors to its compile process because of the hibernate-testing module circularity :( To be honest I think I'd alter jpa-metamodel-gen to not be AP-based as the best-case scenario. But that is not likely to happen soon. And coupled with the fact of the IntelliJ limitation due to hibernate-testing circularity, I am not sure it would practically help. It seems to me the only real option currently is to expect a full compile prior to import. Better suggestions? ---- Speaking of the hibernate-testing circularity, I do still want to get rid of that. Currently I have been waiting on Gradle adding support for publishing multiple artifacts from a project (module). The idea being that we'd fold the source from hibernate-testing into hibernate-core and have hibernate-core produce and publish both artifacts. Currently Gradle only supports a single publication from a project. So the hang up really is publishing hibernate-testing to nexus. I think we all agreed last time this was discussed that publishing hibernate-testing to nexus was important enough to hold off on. Do I remember that correctly? Is that still the situation?

11 years, 11 months

2
2
0 / 0

in.relation.to fixed

by Sanne Grinovero

All, the blog platform finally finished its migration to the new servers. If you still see errors, please let us know as that would be a new problem. Sanne

11 years, 11 months

1
0
0 / 0

Re: [hibernate-dev] Jira + pull requests

by Sanne Grinovero

Because the automated integration doesn't work at all if you rebase. I've considered disabling that JIRA plugin.. for now I'm hoping it will improve in future. On 6 November 2014 15:26, Hardy <hibernate(a)ferentschik.de> wrote: > OOI, why do you still add the pull request links manually to Jira. It's > nicely and automatically integrated anyways. > > -- hardy > >

11 years, 11 months

1
0
0 / 0

Was HSearch 4.4.5 ever released to Maven?

by Marc Schipperheyn

I see it in Jira as a version, but in Maven only 4.4.4.Final is available.

11 years, 11 months

2
1
0 / 0

Hibernate ORM 4.3.7.Final and 4.2.15.Final Released

by Gail Badner

For details, see: http://in.relation.to/Bloggers/HibernateORM437FinalAnd4216FinalReleased These were actually released on October 30. The announcement has been delayed because the server hosting the blog is having critical hardware problems and I was not able to post my entry until today. If you have problems with that link, please try again later. Gail Badner Red Hat, Hibernate ORM

11 years, 11 months

1
0
0 / 0

Hibernate Search 5.0.0.Beta1 released!

by Sanne Grinovero

The Beta1 of Hibernate Search 5 is now available! I've described all great reasons to try it out here: http://in.relation.to/Bloggers/HibernateSearchReleases500Beta1TheFinalSpr... One warning though: the server hosting the blog is having some critical hardware problems and is being replaced, it can't currently handle any non-trivial load. If you see errors at the link, please try again later. Sanne

11 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-dev November 2014