Wargames - Java vulnerabilities and why you should care

JavaForum presents two talks this evening

Wargames - Java vulnerabilities and why you should care
Java is great and we all spend time on making it more performant, more scalable and maintainable. But we better should also spend some time on making it more secure. With all that new Java releases and features also come new vulnerabilities and exploits. Because Java is everywhere, it has a huge attack surface which makes it interesting for hackers to search for vulnerabilities in Java and foremost in Java based applications. This sessions will explain what all these mystique acronyms like NVD, CVE, CVSS, CPU, PSU etc. mean and how they are related to Java security. It will also be shown what tools are available to you to check whether your Java application is vulnerable to known issues.

From Spring Boot 2 to Spring Boot 3 with Java 21 and Jakarta EE
Jakarta EE 9 changed its package namespace from javax.* to jakarta.*. This may sound like a trivial change that mostly affects Jakarta EE. So, why should Spring developers care? As it turns out, the namespace changes ripple throughout the entire Java ecosystem. And Spring is no exception. Spring Framework 6 and Spring Boot 3 raise their baseline to Jakarta EE 9 API level which is supported by Tomcat 10 and Jetty 11 for example. Attending this session will teach you how to make this migration as smooth as possible. A live coding demo will take you through the steps involved, and point out where to pay special attention. We will also briefly examine some of the changes introduced in Jakarta EE 10 that will prepare you for what to expect from Spring 6.x. Some pointers to what we can expect from Jakarta EE 11 will also be provided.