Re: [hibernate-dev] Question in relation to Hibernate4.0 Final
Hi Mr. Andersen, >>Problem is that it seems 4.1 will cause similar disjunct API The "Redesigned metamodel" goal, which was planned for 4.1, surely would have caused lots of disjunct API's again, but now I saw on the hibernate roadmap, that in meantime the "Redesigned metamodel" goal has been shifted to Hibernate 5.0. So im asking, if nevertheless 4.1 will still cause similar disjunct API ? Exists there a roadmap for Hibernate-Tools? Can hibernate-tools users hope to can switch to Hibernate4 or will they must wait until Hibernate5 ? Best regards Günther Demetz Würth Phoenix S.r.l. Günther Demetz Product Development (CIS) Via Kravogl 4 I-39100 Bolzano Direct: +39 0471 564 061 Fax: +39 0471 564 122 E-Mail: guenther.dem...@wuerth-phoenix.com Website: www.wuerth-phoenix.com -Original Message- From: Max Rydahl Andersen [mailto:max.ander...@redhat.com] Sent: Wednesday, December 21, 2011 11:05 AM To: Strong Liu Cc: Demetz, Guenther; Hibernate hibernate-dev Subject: Re: Question in relation to Hibernate4.0 Final JBoss Tools M5 have an experimental version of the eclipse plugins that works against both 3.6 and 4.0. We'll get that merged into hibernate tools in the new year. Problem is that it seems 4.1 will cause similar disjunct API so the problem is just getting worse to keep up and keep a stable API/access for hibernate tools users :( /max On Dec 19, 2011, at 14:11, Strong Liu wrote: > Max? > > - > Best Regards, > > Strong Liu > http://about.me/stliu/bio > > On Dec 19, 2011, at 8:59 PM, Guenther Demetz wrote: > >> Hi Strong Liu, >> >> do you know, when it is planned a Hibernate-Tools release compatible to >> Hibernate-Core 4.0 Final ? >> >> Me and probably many other hibernate users cannot switch to >> Hibernate-Core 4.0 as long there no compatible hibernate-tools version >> available. >> >> best regards >> Guenther Demetz >> >> On 09/07/2011 02:10 PM, Strong Liu wrote: >>> that just because of we don't have enough resource working on >>> hibernate-tools :( meanwhile, you can use hibernate-tools with >>> hibernate-core 3.6 to generate schemas >>> >>> and thanks for the patches i'm working on it >>> >>> --- >>> Strong Liu >>> http://hibernate.org >>> http://github.com/stliu >>> >>> On Sep 7, 2011, at 8:09 PM, Guenther Demetz wrote: >>> Hi Strong Liu, as requested I attached a testcase to HHH-6635. I have another question regarding Hibernate4: Till now I used hbm2ddl ant-target of hibernate-tools to create new database schemas. but I noticed that so far all Hibernate4 prereleases were provided without a compatible version of hibernate-tools. -hibernate-tools3.2.4.GA still makes reference to org.hibernate.util.StringHelper which in hibernate4 has been moved to package org.hibernate.internal.util -method org.hibernate.tool.hbm2ddl.ManagedProviderConnectionHelper#prepare( ) in Hiberante-core 4.0.0CR2 has an unimplemented body, so no connection is provided for the hbm2ddl tool So my question is:will hibernate-tools still be supported with hibernate4 or has this module become deprecated ? best regards Guenther Demetz -- Würth Phoenix S.r.l. Günther Demetz Product Development (CIS) Via Kravogl 4 I-39100 Bolzano Direct: +39 0471 564 061 Fax:+39 0471 564 122 E-Mail: guenther.dem...@wuerth-phoenix.com Website: www.wuerth-phoenix.com >>> >> >> >> -- >> Würth Phoenix S.r.l. >> Günther Demetz >> Product Development (CIS) >> Via Kravogl 4 >> I-39100 Bolzano >> Direct: +39 0471 564 061 >> Fax:+39 0471 564 122 >> E-Mail: guenther.dem...@wuerth-phoenix.com >> Website: www.wuerth-phoenix.com > /max http://about.me/maxandersen ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Test failures after pull
Everyone else seeing these after pulling master? Test org.hibernate.test.cascade.circle.MultiPathCircleCascadeCheckNullibilityFalseTest FAILED Test org.hibernate.test.cascade.circle.MultiPathCircleCascadeTest FAILED Test org.hibernate.test.cascade.circle.MultiPathCircleCascadeCheckNullTrueDelayedInsertTest FAILED Test org.hibernate.test.cascade.circle.MultiPathCircleCascadeCheckNullibilityTrueTest FAILED Test org.hibernate.test.annotations.cascade.circle.identity.CascadeCircleIdentityIdTest FAILED Test org.hibernate.test.annotations.cascade.circle.sequence.CascadeCircleSequenceIdTest FAILED -- st...@hibernate.org http://hibernate.org ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Question in relation to Hibernate4.0 Final
we got a hibernate4 compatible fork in hibernate tools eclipse plugin now. anyone want to contribute and help make the now three releases that is needed? (3.2-3.5, 3.6 and 4.0?) output of hibernate tools work with all versions, its only if you do queries or need something specific from hibernate 3.6 or 4.0 metamodel you need to run with the exact same version. /max On Jan 20, 2012, at 09:30, Demetz, Guenther wrote: > Hi Mr. Andersen, > >>> Problem is that it seems 4.1 will cause similar disjunct API > > The "Redesigned metamodel" goal, which was planned for 4.1, surely would > have caused lots of disjunct API's again, > but now I saw on the hibernate roadmap, that in meantime the "Redesigned > metamodel" goal has been shifted to Hibernate 5.0. > So im asking, if nevertheless 4.1 will still cause similar disjunct API ? > > Exists there a roadmap for Hibernate-Tools? > Can hibernate-tools users hope to can switch to Hibernate4 or will they must > wait until Hibernate5 ? > > Best regards > Günther Demetz > > Würth Phoenix S.r.l. > Günther Demetz > Product Development (CIS) > Via Kravogl 4 > I-39100 Bolzano > Direct: +39 0471 564 061 > Fax:+39 0471 564 122 > E-Mail: guenther.dem...@wuerth-phoenix.com > Website: www.wuerth-phoenix.com > > -Original Message- > From: Max Rydahl Andersen [mailto:max.ander...@redhat.com] > Sent: Wednesday, December 21, 2011 11:05 AM > To: Strong Liu > Cc: Demetz, Guenther; Hibernate hibernate-dev > Subject: Re: Question in relation to Hibernate4.0 Final > > JBoss Tools M5 have an experimental version of the eclipse plugins that works > against both 3.6 and 4.0. > > We'll get that merged into hibernate tools in the new year. > > Problem is that it seems 4.1 will cause similar disjunct API so the problem > is just getting worse to keep up and keep a stable API/access for hibernate > tools users :( > > /max > > On Dec 19, 2011, at 14:11, Strong Liu wrote: > >> Max? >> >> - >> Best Regards, >> >> Strong Liu >> http://about.me/stliu/bio >> >> On Dec 19, 2011, at 8:59 PM, Guenther Demetz wrote: >> >>> Hi Strong Liu, >>> >>> do you know, when it is planned a Hibernate-Tools release compatible to >>> Hibernate-Core 4.0 Final ? >>> >>> Me and probably many other hibernate users cannot switch to >>> Hibernate-Core 4.0 as long there no compatible hibernate-tools version >>> available. >>> >>> best regards >>> Guenther Demetz >>> >>> On 09/07/2011 02:10 PM, Strong Liu wrote: that just because of we don't have enough resource working on hibernate-tools :( meanwhile, you can use hibernate-tools with hibernate-core 3.6 to generate schemas and thanks for the patches i'm working on it --- Strong Liu http://hibernate.org http://github.com/stliu On Sep 7, 2011, at 8:09 PM, Guenther Demetz wrote: > Hi Strong Liu, > > as requested I attached a testcase to HHH-6635. > > I have another question regarding Hibernate4: > > Till now I used hbm2ddl ant-target of hibernate-tools to create new > database schemas. > but I noticed that so far all Hibernate4 prereleases were provided > without a compatible version of hibernate-tools. > > -hibernate-tools3.2.4.GA still makes reference to > org.hibernate.util.StringHelper which in hibernate4 has been moved > to package org.hibernate.internal.util > > -method > org.hibernate.tool.hbm2ddl.ManagedProviderConnectionHelper#prepare( > ) in Hiberante-core 4.0.0CR2 has an unimplemented body, so no > connection is provided for the hbm2ddl tool > > So my question is:will hibernate-tools still be supported with hibernate4 > or has this module become deprecated ? > > best regards > Guenther Demetz > > -- > Würth Phoenix S.r.l. > Günther Demetz > Product Development (CIS) > Via Kravogl 4 > I-39100 Bolzano > Direct: +39 0471 564 061 > Fax:+39 0471 564 122 > E-Mail: guenther.dem...@wuerth-phoenix.com > Website: www.wuerth-phoenix.com > > > > >>> >>> >>> -- >>> Würth Phoenix S.r.l. >>> Günther Demetz >>> Product Development (CIS) >>> Via Kravogl 4 >>> I-39100 Bolzano >>> Direct: +39 0471 564 061 >>> Fax:+39 0471 564 122 >>> E-Mail: guenther.dem...@wuerth-phoenix.com >>> Website: www.wuerth-phoenix.com >> > > /max > http://about.me/maxandersen > > > /max http://about.me/maxandersen ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Test failures after pull
nm, clean and then test worked On 01/20/2012 11:30 AM, Steve Ebersole wrote: > Everyone else seeing these after pulling master? > > > Test > org.hibernate.test.cascade.circle.MultiPathCircleCascadeCheckNullibilityFalseTest > FAILED > Test org.hibernate.test.cascade.circle.MultiPathCircleCascadeTest FAILED > Test > org.hibernate.test.cascade.circle.MultiPathCircleCascadeCheckNullTrueDelayedInsertTest > FAILED > Test > org.hibernate.test.cascade.circle.MultiPathCircleCascadeCheckNullibilityTrueTest > FAILED > Test > org.hibernate.test.annotations.cascade.circle.identity.CascadeCircleIdentityIdTest > FAILED > Test > org.hibernate.test.annotations.cascade.circle.sequence.CascadeCircleSequenceIdTest > FAILED > > -- st...@hibernate.org http://hibernate.org ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] natural-id to primary key cache
Historically natural-id look ups were accomplished by leveraging Criteria queries. Caching was handled through the second level query cache. One of the new things in 4.1 is the dedicated natural-id loading API. So the caching will be quite different here. I am a little leery about making a breaking changes in 4.1 after all the changes in 4.0 if we can avoid it. If we can't we can't. One thought for this was to use a SessionFactory scoped "cache" for this in 4.1 and then add a new second level cache Region construct for this in 5.0. The *only* benefit is to keep the second level cache SPI the same between 4.0 and 4.1. Is that worth it? Any thoughts? -- st...@hibernate.org http://hibernate.org ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
