Re: [hibernate-dev] JPA 2.1 progress

>> That's what I have in mind as well. Basically what I tried to outline. > > Ok, but one point is that having this OverrideIndex may not be enough. As > Strong points out, a consideration here is the concept of > . Consider a class with no annotations, that is mapped > via orm.xml… that co

Re: [hibernate-dev] JPA 2.1 progress

On Tue 17 Jul 2012 07:57:02 AM CDT, Hardy Ferentschik wrote: > Thanks for the info. I was missing this info and it gives "composite index" a > different meaning as well. > In the composite index is there a way to only query for annotation of a given > module? Say we get a composite index > and a

Re: [hibernate-dev] JPA 2.1 progress

On Jul 17, 2012, at 2:42 PM, Steve Ebersole wrote: > On 07/17/2012 04:58 AM, Hardy Ferentschik wrote: >> >> On Jul 16, 2012, at 9:06 PM, Steve Ebersole wrote: >> >>> One such point of discussion was a common interface for "Index". >>> Unfortunately the name Index is already taken as in the main

Re: [hibernate-dev] JPA 2.1 progress

As I pointed out in the reply to Hardy, I think there is a confusion here. I am not asking that we simply be able to hand Jandex an XML file and expect it to be able to figure out how to apply overrides. Thats not going to work. Again, what would be needed is some kind of SPI where we could t

Re: [hibernate-dev] JPA 2.1 progress

CompositeIndex *does exist*. But its part of the AS codebase, not Jandex. On Tue 17 Jul 2012 05:13:18 AM CDT, Strong Liu wrote: > > On Jul 17, 2012, at 5:58 PM, Hardy Ferentschik > wrote: > >> >> On Jul 16, 2012, at 9:06 PM, Steve Ebersole wrote: >> >>> Strong, I for

Re: [hibernate-dev] JPA 2.1 progress

On 07/17/2012 04:58 AM, Hardy Ferentschik wrote: > > On Jul 16, 2012, at 9:06 PM, Steve Ebersole wrote: > >> One such point of discussion was a common interface for "Index". >> Unfortunately the name Index is already taken as in the main Jandex >> class. So we came up with some other names. For t

Re: [hibernate-dev] JPA 2.1 progress

On Jul 17, 2012, at 5:58 PM, Hardy Ferentschik wrote: > > On Jul 16, 2012, at 9:06 PM, Steve Ebersole wrote: > >> Strong, I forgot to mention that Jason completely agrees that changes to >> Jandex are needed. I agreed to prototype some of the things he and I >> discussed specifically in thi

Re: [hibernate-dev] JPA 2.1 progress

I don't see there is a general way to integrate xml override into jandex, I think it is a very domain specific issue. and the "override" has lots of different requirements, for example "metadata-complete" org.hibernate.metamodel.internal.source.annotations.xml.mocker.IndexBuilder#mappingMetadata

Re: [hibernate-dev] JPA 2.1 progress

On Jul 16, 2012, at 9:06 PM, Steve Ebersole wrote: > Strong, I forgot to mention that Jason completely agrees that changes to > Jandex are needed. I agreed to prototype some of the things he and I > discussed specifically in this code base and hand them back to him for > integration back into

Re: [hibernate-dev] JPA 2.1 progress

Strong, I forgot to mention that Jason completely agrees that changes to Jandex are needed. I agreed to prototype some of the things he and I discussed specifically in this code base and hand them back to him for integration back into the next rev of Jandex. One such point of discussion was a

Re: [hibernate-dev] JPA 2.1 progress

Not sure what happened. Maybe I just forgot to upload? Anyway, it is there now. On Mon 16 Jul 2012 09:39:04 AM CDT, Steve Ebersole wrote: > Hmmm.. let me check... > > On Mon 16 Jul 2012 08:45:48 AM CDT, Hardy Ferentschik wrote: >> Hi, >> >> >>> It also contains some major refactorings: >>> 1) r

Re: [hibernate-dev] JPA 2.1 progress

Hmmm.. let me check... On Mon 16 Jul 2012 08:45:48 AM CDT, Hardy Ferentschik wrote: > Hi, > > >> It also contains some major refactorings: >> 1) removal of Ejb3Configuration in preference of the new 2-phase >> bootstrap approach of Bootstrap/EntityManagerFactoryBuilder. > > sounds good > >> 2) I r

Re: [hibernate-dev] JPA 2.1 progress

Hi, > It also contains some major refactorings: > 1) removal of Ejb3Configuration in preference of the new 2-phase > bootstrap approach of Bootstrap/EntityManagerFactoryBuilder. sounds good > 2) I renamed o.h.ejb to o.h.jpa. +1 jpa is much more concise > Let me know if you see any problems…

Re: [hibernate-dev] JPA 2.1 progress

Ok, at this point the jpa21 branch is complete for Draft 6. It also contains some major refactorings: 1) removal of Ejb3Configuration in preference of the new 2-phase bootstrap approach of Bootstrap/EntityManagerFactoryBuilder. a) Scott actually plans to present the general approach to the JPA E

Re: [hibernate-dev] JPA 2.1 progress

Should have pointed out that the Hibernate native stored procedure support is defined by org.hibernate.StoredProcedureCall/org.hibernate.internal.StoredProcedureCallImpl On Thu 28 Jun 2012 08:26:24 PM CDT, Steve Ebersole wrote: > Just wanted to let everyone know that implementing JPA 2.1 support