Arjan Tijms' Weblog

I maintain a page on zeef.com about the upcoming Java EE 8 specification . On this page I collect all interesting links about the various sub-specs that will be updated or newly introduced in EE 8. The page is up since April last year and therefor currently has almost 10 months worth of data (at the moment 8.7k views, 5k clicks). While there still aren't any discussions and thus links available for quite a couple of specs, it does give us some early insight in what's popular. At the moment the ranking is as follows: Position Link Category 1 Java EE 8 roadmap [png] Java EE 8 overal 2 JSF MVC discussion JSF 2.3 3 Let's get started on JSF 2.3 JSF 2.3 4 Servlet 4.0 Servlet 4.0 5 Java EE 8 Takes Off! Java EE 8 overal 6 An MVC action-based framework in Java EE 8 MVC 1.0 7 JSF and MVC 1.0, a comparison in code MVC 1.0 8 Let's get started on Servlet 4.0 Servlet 4.0 9 Jav

This is the second part of a series where we revisit JACC after taking an initial look at it last year. In the first part we somewhat rectified a few of the disadvantages that were initially discovered and looked at various role mapping strategies. In this second part we'll take an in-depth look at obtaining the container specific role mapper and the container specific way of how a JACC provider is deployed. In the next and final part we'll be bringing it all together and present a fully working JACC provider. Container specifics The way in which to obtain the role mapper and what data it exactly provides differs greatly for each container, and is something that containers don't really document either. Also, although the two system properties that need to be specified for the two JACC artifacts are standardized, it's often not at all clear how the jar file containing the JACC provider implementation classes has to be added to the container's class path. A