[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-community] Deprecating EJB in Favor of CDI Services
|
I have clients that still use EJB remoting as well. I suspect the vendors will continue to support these folks even if we ever manage to fully remove EJB from Java EE. I have to say though that I have seen these clients to be a dying breed. Most have moved to REST these days. Is it really worth carrying around the harrowingly complex EJB remoting implementation forward just to satisfy a tiny portion of the overall Java EE target audience?
Could you please elaborate your XML/CDI point a bit more? I can try to guess what the problem is, but it's best to better understand first.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
From: Rudy De Busscher <rdebusscher@xxxxxxxxx>
Date: 10/16/17 1:45 PM (GMT-05:00)
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] Deprecating EJB in Favor of CDI Services
Deprecating @Remote
-> I have a large client with a custom ERP system which uses this. He won't like this!
Another thing which is missing
-> define interceptors in XML on some or all EJB. There are techniques to do this in CDI but nothing defined in the spec.
regards
Rudy