I think one of the issues, and for me this is huge issue, is how the JCP process is set up. In order to make changes in specs, even if they are platform initiated, specs have to be active. But specs

Wow. I guess @EJB was not the only miss... I didn't think too hard before asking that... :-) In any case, thanks for the pointer to the JIRA. I missed that reference when I went back in the

I had helped develop the initial JIRA on this and I do not think EJB is the only miss, though it may be the major miss. I also agree this is an important issue to get right.

Hi Kevin, I agree that consistency here would be desirable. However, in planning for Java EE 8 we had to prioritize resources around updating those specs we felt it most important to focus on, with

Hi, I know we discussed this back in May of 2016, but actual practice is causing us to scratch our heads... Without the @Repeatable annotation usage being spelled out at the Platform level, we're

Dear Java EE and java.net maintainers, Since java.net was shutdown, most of the content has been migrated to github. However, although much of the content is available, it's not easy to find it

Hi Kevin, This looks like a cut-and-paste bug. Table EE.6-1 indicates that Security 1.0 is not a requirement for Application Clients. Thanks again for your diligence in

Hi Kevin, I know nothing about support for the Application Client Container and Java EE Security. To be honest, I don't know much about the ACC at all, but doesn't it work via a kind of automatic

Hi, Looking at Figure EE.2-1 and I see that Security 1.0 is listed as part of the Application Client. I knew about the discussion to include Security 1.0 in the Web Profile. I was not aware of it

Excellent, Bill! Thanks for that link. I agree that we need that link somewhere more obvious. -- Kevin

Note that the schemas are in GitHub here. Kevin Sutter wrote on 06/ 6/17 11:29 AM:

All the downloads from our original java.net project are still available in the GitHub repository here. I should probably add a link from the web site to make it more obvious.

Since some specs are still evolving, I would expect this closer to the end. -Linda

Thanks, Linda. Do we expect any early versions of the schemas before the Java EE 8 spec finalizes? I wouldn't expect too many changes, just looking ahead... Thanks. -- Kevin

Hi Kevin, The downloadables from our old projects have not yet been migrated. I believe that will happen at some point this summer. All milestone spec drafts can be found on

Hi Linda, Where can we get access to downloadable files? The current groups.io repo doesn't have any files (https://javaee.groups.io/g/javaee-spec/files). And, if I try to go to our old repo on

Thanks, Linda. I'll cross-post to the interceptor mailing list as well just to complete the picture... Kevin

Hi Kevin, Thanks for calling this to my intention. It looks like the spec was ambiguous enough that it could be parsed with a meaning that I did not intend. I'll comment further

Hi, Are we discussing the updated Interceptor spec here? I know we had some discussions related to this update on the Java EE mailing list, but since it was released as part of the EJB family of

Hi Linda/All, Hope all is well. Earlier this week, Mark Reinhold posted an email proposing to move the release date of JDK 9 back to September 21