[
https://issues.jboss.org/browse/WELD-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12692556#comment-12692556
]
Jozef Hartinger commented on WELD-1135:
---------------------------------------
What I did so far in this area is a preloader that resolves observer methods
for lifecycle events upfront. The performance gain is most noticeable in the SE
environment where a serial classloader is used. While other threads are blocked
on the classloader, preloader threads can resolve observers for
ProcessAnnotatedType<X>, etc. for already loaded classes.
https://github.com/weld/core/blob/2.0/impl/src/main/java/org/jboss/weld/bootstrap/ContainerLifecycleEventPreloader.java
> Investigate faster ways of performing type safe resolution
> ----------------------------------------------------------
>
> Key: WELD-1135
> URL: https://issues.jboss.org/browse/WELD-1135
> Project: Weld
> Issue Type: Bug
> Reporter: Stuart Douglas
> Fix For: 1.2.0.CR1
>
>
> At the moment quite a lot of bootstrap time is spent resolving injection
> points and events. By far the majority of this time is spent resolving
> container events that form part of the portable extensions SPI. As these
> events are parameterised types the resolution cannot be cached (as
> ProcessAnnotatedType<ClassA> can resolve differently to
> ProcessAnnotatedType<ClassB> ).
> We should investigate if there is a faster way to do this, if not in the
> general case then at least for these container events.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
