yes. This is another solution I have in mind, which is better to discover
these components in CDI integration code. I had hoped there is a nice API
in Weld allowing me to differentiate the JavaEE component classes.
On Fri, May 29, 2015 at 7:30 AM, Jozef Hartinger <jharting(a)redhat.com>
I suppose you already must have code capable of identifying those
components - i.e. the Servlet container must be able to discover Servlets
in a web application. Therefore, the best way probably is to hook into
these "Java EE component supporting" pieces of code instead of discovering
the EE components yourself in the CDI integration code.
We do exactly this in WildFly where we let the other subsystems identify
EE components and then override the factories for these components to
actually use InjectionTargets (and fire PIT, PIP in the process).
On 05/28/2015 11:42 AM, Emily Jiang wrote:
I need to fire events for each JavaEE component class (e.g. process
injectionTarget, injectionPoint etc) during Weld bootstrap phase. At the
moment, I am think to go through all bdas per deployment and process all
classes in the bda and fire events for each JavaEE component classes as
Weld leaves it to be handled by the integrator. What is the best way to
find out which class is JavaEE component class? I don't like to idea of
building a long hardcoded list from the EE.5-1 table of the JavaEE7 spec.