Re: CDI integration
On Fri, Jun 2, 2017 at 11:32 PM, Sergey Beryozkin <sberyozkin@...> wrote:
Because it's another Java EE spec that had its own DI engine and gave it up for the platform one.
I'm really not sure why the REST API of Java EE should have its own DI engine.
Does Spring MVC also has its own DI engine, separate from the Spring platform's bean container? If not, why should Java EE have that?
And if JAX-RS needs to have its own DI engine, why should JSF not have its own? And then Servlet its own? And JPA its own? Does every spec in Java EE need its own and totally different Di engine?
Imagine how well JAX-RS could do -with- CDI. I absolutely love JAX-RS and so do many people, but I've rarely heard of anyone going for JAX-RS just because of it's fabulous own DI engine.
Is Spring trying to spread Spring MVC beyond EE boundaries? Is Microsoft trying to spread ASP.NET Web API beyond the .NET boundaries? Is Ruby On Rails trying to spread its REST API beyond RoR boundaries? Or are they all trying to integrate it in their framework as well as they possibly can?