Fellow experts,
We've been receiving some good feedback on the users list
(jsr366-users_at_javaee-spec.java.net) regarding the inclusion of the
Java EE Security API. I hope all of you have been following the
discussion. If not, the users list archives are here:
https://java.net/projects/javaee-spec/lists/users/archive/2017-04/thread/1
In short, support for including the Java EE Security API in the full
platform has been unanimous, but there has been some disagreement as
to whether the Security API should be included as part of the Web
Profile, largely due to its dependence on JASPIC.
I would appreciate if you would weigh in on this issue.
thanks,
-Linda
On 4/7/17, 3:11 PM, Linda DeMichiel wrote:
> The Java EE Security API has received strong support in the community
> and has been making good process as evidenced by its recent Early
> Draft. This JSR is now on-track to complete within the Java EE 8 time
> frame.
>
> We believe that the Java EE Security API adds value to the Java EE
> Platform due to its simplifications and enhancements to platform
> security, and should be included as a required technology in both the
> Java EE 8 Platform and the Java EE 8 Web Profile.
>
> Please let us know if for some reason you object.
>
> thanks,
>
> -Linda