Security in Java EE applications is a never-ending story. Most of the knowledge about how to build secure applications is derived from knowledge and experience. And we’ve all done the same mistakes every Java EE developer does over and over again. But how to solve the real business requirements behind …
Skinny modules, design by contract without a contract, proliferation of deployment packages are examples of a typical Java enterprise cargo cult disease. This session discusses a “perfect” Java EE 7 architecture and focus on the modularization, interaction and architectural aspects of Java EE 7.
Java EE 7 comes with a few interesting enhancements, some of which were directly driven by the need for a better Bean Validation integration. This talk provides you a better idea on how to benefit from the Java EE 7 enhancements in your application or framework.
Problems choosing between Java EE and Spring? Or do you want to use both in combination? Then this presentation is something for you.
Enterprise Java is old. Our heritage is old practices, patterns, and even cargo cult programming. With Java EE 7, you can remove an amazing amount of clutter just by focusing on the business domain and ignoring old “best” practices.
The Java EE 7 platform has four new components (WebSocket, JSON-P, batch, and concurrency), three that are significantly updated (JAX-RS, JMS, and EL), and several others that bring significant changes to the platform.