Java EE 8 - Only what is New

[David Sachdev]

With the move to the Spring Framework we saw many industry leaders move away from some of the older technologies in EE for what the Spring Framework included.  With JEE3, we started to see some benefits in EE again, and a bit of a hybrid approach to picking and choosing what was good from Spring, but also pulling in some of the good technologies that JEE3 brought to the table.  Do you address the Spring Framework and go over the pros and cons of Spring versus EE, and where they can work together, and where it is best to not intermingle?

Thanks
David Sachdev

[Jack Ramon]

Java EE 8 introduces major and minor updates to core APIs such as Servlet 4.0 and Context and Dependency Injection 2.0. It also introduces two new APIs—Java API for JSON Binding (JSR 367) and the Java EE Security API (JSR 375).

[Alex Theedom]

Hi David

Thanks for your question.

In the book, I demonstrate with plenty of code examples the new features added to Java EE 8. It includes two large chapters on the brand new security API and JSON Binding. There are some really cool new additions such as the Reactive client in JAX-RS and asyn events in CDI to name just a few. I touch on the spring framework, although version 5 does looks really interesting. When developing microservices you can develop some in Java EE, some in Spring other in GoLang or whatever best solves the problem. In terms of mixing them in one project, I suggest that there would have to be a very good reason for doing so. Perhaps some of the Spring APIs could be used with a Java EE project but making them work together might be more of a headache than its worth.

[David Sachdev]

Alex Theedom wrote:Hi David

Thanks for your question.

In the book, I demonstrate with plenty of code examples the new features added to Java EE 8. It includes two large chapters on the brand new security API and JSON Binding. There are some really cool new additions such as the Reactive client in JAX-RS and asyn events in CDI to name just a few. I touch on the spring framework, although version 5 does looks really interesting. When developing microservices you can develop some in Java EE, some in Spring other in GoLang or whatever best solves the problem. In terms of mixing them in one project, I suggest that there would have to be a very good reason for doing so. Perhaps some of the Spring APIs could be used with a Java EE project but making them work together might be more of a headache than its worth.

Thanks for the reply - and for highlighting some of the things to look out for.   The security API and the Reactive Client have definitely piqued my interest!

Thanks
David Sachdev