Re: [hibernate-dev] OSGI manifests for hibernate-orm

I found them your side of the conversation in my inbox :) Yes they were comments made on the fork branch which no longer exists :( The discussion centered around cases where HEM defines the same operations differently from CORE. Here it is the notion of persist(); the difference is that CORE

Re: [hibernate-dev] OSGI manifests for hibernate-orm

On 16 Jan 2012, at 12:42 AM, Steve Ebersole wrote: > In fact splitting those purposes alone solves the problem with > org.hibernate.engine.spi.JpaCascadingAction I believe > > As for org.hibernate.engine.spi.JpaCascadeStyle, TBH, I am not sure > exactly why we need this split between persist()

Re: [hibernate-dev] OSGI manifests for hibernate-orm

BTW, on master commons-annotations is in fact still needed so yes we need to account for it. However, just a heads up that on the metamodel branch, we no longer use commons-annotations. Some background that I alluded to before... Master is 4.1 + (ongoing) JPA 2.1 support. There is also a sha

Re: [hibernate-dev] OSGI manifests for hibernate-orm

Guys, lets move this discussion to the Jira. Thats the best way to capture all these points... On Thu 16 Aug 2012 09:25:58 AM CDT, Scott Marlow wrote: > Does the Bundle-Activator really belong in the Hibernate core project? > Or should it be in the external OSGI container? Or perhaps someone >

Re: [hibernate-dev] OSGI manifests for hibernate-orm

Does the Bundle-Activator really belong in the Hibernate core project? Or should it be in the external OSGI container? Or perhaps someone may want to maintain an external project that generates the "ready to be used" Hibernate Bundle-Activator. On 08/16/2012 05:58 AM, mail...@bibbernet.org wr

Re: [hibernate-dev] OSGI manifests for hibernate-orm

Hi Steve, > Not being well-versed in OSGi, could you explain what 'blueprint.xml' > is? > I guess the purpose is the same/similar to > /META-INF/services/javax.persistence.spi.PersistenceProvider defined by > JPA, yet OSGi specific? Ok, to give some background information, I will cite a section o

Re: [hibernate-dev] OSGI manifests for hibernate-orm

er >> (the new guy on Hibernate...) >> >> >> >> On 08/15/2012 06:12 PM, Steve Ebersole wrote: >>> >>> Brett, maybe you could help comment on this overall? >>> >>> >>> Original Message >>> Subje

Re: [hibernate-dev] OSGI manifests for hibernate-orm

e. > > Brett E. Meyer > (the new guy on Hibernate...) > > > > On 08/15/2012 06:12 PM, Steve Ebersole wrote: >> >> Brett, maybe you could help comment on this overall? >> >> >> Original Message >> Subject: [hibernate-dev] OSGI ma

Re: [hibernate-dev] OSGI manifests for hibernate-orm

s much as possible. "import-package" reduces unforeseen symptoms in the dependency tree. Brett E. Meyer (the new guy on Hibernate...) On 08/15/2012 06:12 PM, Steve Ebersole wrote: > Brett, maybe you could help comment on this overall? > > > ---- Original Message ------

Re: [hibernate-dev] OSGI manifests for hibernate-orm

Martin, Totally agree about the org.hibernate.engine.spi bits. Thats always been fugly hack. Both org.hibernate.engine.spi.CascadeStyle and org.hibernate.engine.spi.CascadingAction attempt to combine contracts and enumerations, which I have never been a fan of here. I think its fine when tha

[hibernate-dev] OSGI manifests for hibernate-orm

Hello, because I need clean OSGI bundles for Hibernate and especially Envers, I am working on some patches for the 4.1 branch of hibernate-orm to enable generation of OSGI compatible jar files. During the work I have found the following problems, and need some help and/or feedback. The probl