FWIW, those hooks in Hibernate 5 already exist, based on Jandex 1, of
We are not currently using Jandex. That was work happening under the
metamodel redesign, which we had to push to 6.0.
When we do start using Jandex, the plan is to use the provided Jandex as a
base. But the problem always has been that Hibernate needs to augment that
information from orm.xml. Also we do have to manage cases outside of
WildFly, so we'd have to build the Index manually. Also, I want to look at
the building of an index as a build-time step, storing some representation
of that index into the artifact. We can then locate that representation at
runtime and load it via resource lookup, depending on what that saves/gains
us perf wise (tbd). Again this along with the passed Jandex index serve as
the base index. We at least still need to do that augmentation as Jandex
does not handle that at all.
What is "end of deployment"? Is that the end of phase-2 in our 2-phase JPA
bootstrap design? If so, that should be fine.
On Tue, May 5, 2015 at 10:54 AM, Scott Marlow <smarlow(a)redhat.com> wrote:
Best to talk with Jason but I heard that the Jandex indexes will soon
larger (as part of the Java 8 changes). As a result of the size
changes, Jandex indexes should only be accessed during the WildFly
I'm not sure how Hibernate would use Jandex2 without creating its own
instances of the indexes, which would be expensive memory wise.
There is also the Hibernate 5.0 release, that we want to integrate with
WildFly. I think that is where we might tightly couple Hibernate ORM
with Jandex, by passing a composite index into Hibernate. The Jandex
reference will need to be cleared by the end of deployment. Would that
On 05/04/2015 01:53 PM, Sanne Grinovero wrote:
> Is it possible for our other projects (like Hibernate) to start using
> Jandex2 sooner rather than later, w/o banning our users from WildFly
> We're in an innovation paradox ;-)
> On 4 May 2015 at 15:07, Jason T. Greene <jason.greene(a)redhat.com> wrote:
>> Yes that's correct. We need to make some deployer changes to prevent
holding on to indexes.
>> Sent from my iPhone
>>> On May 4, 2015, at 6:25 AM, Jozef Hartinger <jharting(a)redhat.com>
>>> Congrats on the release!
>>> It seems that Jandex upgrade to 2.0 has not been done yet. Is my
understanding correct that it has been postponed till WF10?
>>>> On 05/01/2015 10:38 PM, Jason Greene wrote:
>>>> Hello Everyone,
>>>> I am happy to announce the first candidate release of WildFly 9!
WildFly 9 builds off of WildFly 8’s Java EE7 support, and adds many new
capabilities, including intelligent load balancing, HTTP/2 support, a new
offline CLI mode, graceful single node shutdown, and a new Servlet-only
>>>> For more details, check out the release notes:
>>>> As always, you can download it here:
>>>> Jason T. Greene
>>>> WildFly Lead / JBoss EAP Platform Architect
>>>> JBoss, a division of Red Hat
>>>> wildfly-dev mailing list
>> wildfly-dev mailing list
> wildfly-dev mailing list
wildfly-dev mailing list