I'm thinking add the interface below, with it, modules like envers can choose
either before or after the metamodel get processed to hook into its own
extending mappings
public interface MetadataContributingIntegrator extends Integrator {
/**
* Allow the integrator to alter the
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
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()
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
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
>
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
Not in the one I looked at. But good point, I'll look at the others.
On Thu 16 Aug 2012 03:18:30 AM CDT, Hardy Ferentschik wrote:
> Does it not do some filtering as well when the copy occurs. That's the only
> thing I can think which would prevent us to use the src/test bundles.
>
> --hardy
>
>
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
Does it not do some filtering as well when the copy occurs. That's the only
thing I can think which would prevent us to use the src/test bundles.
--hardy
On 15 Aug 2012, at 19:50, Steve Ebersole wrote:
> Forgot to mention, the reason I am asking is that the current set up
> makes it more d
