[
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 see. So basically the work that Oracle specification leads did not want to do in JAX-RS? I have to admit I never really understood why they resisted that work so much. There is a certain type of REST client for which this is a very good fit...
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
From: Guillermo González de Agüero <z06.guillermo@xxxxxxxxx>
Date: 10/16/17 2:01 PM (GMT-05:00)
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] Deprecating EJB in Favor of CDI Services
MicroProfile is working on a typesafe REST client which I suspect could cover @Remote and SOAP usecases in the long run.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
_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community