[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-community] Deprecating EJB in Favor of CDI Services
|
Cool. I didn't even know this existed.
I think this particular topic is perfect for moving to the CDI alias as is. Hopefully they have now spun down enough from CDI 2 to start some forward looking threads (more importantly that Red Hat's management has given the engineers the go ahead for the next CDI revision).
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
From: Rudy De Busscher <rdebusscher@xxxxxxxxx>
Date: 10/16/17 2:55 PM (GMT-05:00)
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] Deprecating EJB in Favor of CDI Services
Reza, All,
regarding the
interceptors in XML on some or all EJB
With ejb-jar.xml, you can define that interceptors should be used for EJB's
<assembly-descriptor>
<interceptor-binding>
<ejb-name>*</ejb-name>
<interceptor-class>be.c4j.ee.security.interceptor.OctopusInterceptor</interceptor-class>
</interceptor-binding>
</assembly-descriptor>
and ejb-name allows wildcards so you can assign the interceptor to some of the EJB.
Rudy