Adopt-a-JSR for Java EE 7 and beyond
Adopt-a-JSR is an initiative by JUG leaders to encourage JUG members to get involved in a JSR and to evangelize that JSR to their JUG and the wider Java community, in order to increase grass roots participation. The typical question in Adopt-a-JSR is "how do I get started ?".
In general, the Starter Level tasks are helpful at all stages of a JSR. The platform is already released and several JUGs already contributed to improve the quality.
The Java EE 7 platform was released on Jun 12, 2013 can be downloaded from here. You can continue to provide feedback on different JSRs and influence the future direction:
- Java API for WebSocket 1.0 (JSR 356)
- Java API for JSON Processing 1.0 (JSR 353)
- Batch Applications for the Java Platform 1.0 (JSR 352)
- Concurrency Utilities for Java EE 1.0 (JSR 236)
- Java API for RESTful Web Services 2.0 (JSR 339)
- Java Message Service 2.0 (JSR 343)
- Expression Language 3.0 (JSR 341)
- JavaServer Faces 2.2 (JSR 344)
- Servlet 3.1 (JSR 340)
- Java Persistence API 2.1 (JSR 338)
- Enterprise JavaBeans 3.2 (JSR 345)
- Contexts and Dependency Injection 1.1 (JSR 346)
- Interceptors 1.2 (JSR 318)
- Bean Validation 1.1 (JSR 349)
- Java Transaction API 1.2 (JSR 907)
General Areas for Providing FeedbackEach specification can take general feedback in the following areas:
- Build sample applications using the implementations integrated in GlassFish 4.
- Ensure all issues in JIRA are:
- reproducible with the latest codeline.
- have a short, self-contained, compilable, executable reproducer
- have the correct metadata (component, environment, version, etc).
- Read the final version of the specification (available from the JSR page) and provide feedback. You don't need to necessarily review the entire specification and instead can focus on specific chapters and sections.
- Review the javadocs for clarity and completeness.
- Explore integration of one/multiple technologies with your existing Java EE applications.
- File bugs on the corresponding spec or RI project.
Guidelines for Providing Feedback
These are general guidelines for providing feedback. The specification lead and the Expert Group has the final decision on incorporating the feedback.
- For RFEs, any amount of detail would be useful. Code snippets, text description, proposals, etc help understand the intent.
- Multiple JUGs can and should collaborate on a particular JSR. There is always plenty of work and going through the material multiple times only makes it that more better.
- When communicating with the EG, its recommended to include "Adopt-a-JSR" in the subject line.
- When filing a JIRA issue, use "adoptajsr" tag.
How to Participate ?The following one time activities will allow to collaborate with other JUGs participating in Adopt-a-JSR program.
- Join the Adopt-a-JSR program and subscribe to email@example.com (archive).
- Update the wiki to indicate your interest in a particular JSR by creating a page.
- Communicate directly with the specification lead or the java.net users alias for the specification.
Getting Started with Java EE 7
- Java EE 7 SDK Download (includes GlassFish Server Open Source Edition 4.0, samples, tutorials, etc)
- Java EE 7 Specifications
- Java EE 7 Javadocs
- Java EE 7 Maven Coordinates
Learn about different Java EE 7 components using the following playlist of 16 videos:
Remember to click on the playlist icon and select different videos.