Massive.
On Wed, Mar 18, 2015 at 12:44 PM, Scott Marlow <smarlow(a)redhat.com> wrote:
On 03/18/2015 01:05 PM, Steve Ebersole wrote:
> Well I should also clarify that currently we are not using Jandex. That
> was all work done as part of the mapping/metamodel redesign which we
> decided to push to 6.0.
>
I assume you mean the master (5.0) code base doesn't use Jandex but it
looks like [2] in 4.3, is building/using the Jandex index.
How big of a change would it be to use Jandex (via
"hibernate.jandex_index") in ORM 4.3/5.0 mapping? Would be nice to have a
comparison of how long it takes to deploy a large application with and
without Jandex.
Scott
[2]
https://github.com/hibernate/hibernate-orm/blob/4.3/
hibernate-entitymanager/src/main/java/org/hibernate/jpa/boot/internal/
EntityManagerFactoryBuilderImpl.java
> On Wed, Mar 18, 2015 at 10:22 AM, Steve Ebersole <steve(a)hibernate.org
> <mailto:steve@hibernate.org>> wrote:
>
> I don't *think* we do, but it sounds like something we definitely
> need to make sure we aren't doing.
>
> On Mar 17, 2015 8:41 AM, "Scott Marlow" <smarlow(a)redhat.com
> <mailto:smarlow@redhat.com>> wrote:
>
> Steve,
>
> Wildfly-dev [1] brings up a change expected for WildFly 10, to not
> reference the Jandex indexes after deployment completes. I'm
> curious if
> our current/planned ORM 5.0 jandex using code, keeps a reference
> to the
> passed in "hibernate.jandex_index"?
>
> How how hard would it be for ORM, to only reference the
> composite Jandex
> index during application deployment time? Deployment time ends
> when
> PersistenceProvider.createContainerEntityManagerFactory()
> returns.
>
> Scott
>
> [1]
>
http://lists.jboss.org/pipermail/wildfly-dev/2015-
> March/003679.html
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org <mailto:hibernate-dev@lists.
> jboss.org>
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>
>