Thank you Martin for the info! I saw this statement in Weld release page:
Weld is now capable of using
bytecode-scanning utilities, such as the Jandex tool, to speed up deployment. This is especially notable in extra
large deployments (e.g. 5000+ classes) where we observed up to 20% faster
Hi Emily,
AFAIK WildFly makes use of existing Jandex indexes and if not present a
new one is build on the fly (for deployment and external modules) but
the generated indexes are not persisted.
But in WildFly not only Weld leverages the indexes - all other
annotation-based technologies should
Hi Martin/Matej,
For using Jandex to improve bootstrap performance of CDI application, do you know any application server (e.g. Wildfly) normally requires the index files to be generated before hand or it can generate on the fly and then persist it? Do you know whether there is much
On 01/16/2015 03:27 AM, Jozef Hartinger wrote:
Hi Robert,
the change sounds good to me.
The first one or removing entirely the jar extension check?
As for IcedTea we never got Weld running
with it. Last time we tried we got blocked by
Hi Robert,
the change sounds good to me. As for IcedTea we never got Weld running
with it. Last time we tried we got blocked by
http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=1733 If you can
help us with IcedTea support that would be very appreciated.
Btw did you get better performance
Greetings, I am new to using Weld on an Java SE environment, trying to
optimized the container initialization, I got help on the developer IRC
channel telling me to add jandex as a dependency. I found that jandex
indexes could be embedded on jars so I did that. for some reason I got
worse
