|
When a project is as large as the next revision of Java EE it is difficult to decide where priorities lie. What has to be included and what can be postponed? The Java EE Expert Group has asked for feedback.
The preamble to the Java EE 7 Feedback Survey explains:
The Java EE 7 expert group has been hard at work trying to define the next revision of the platform. It is shaping up quite nicely with things like WebSocket/HTML 5 support, a standard API for JSON processing, the next version of JAX-RS, an overhaul of JMS, batch processing in Java EE, the retiring of EJB 2 entity beans and JAX-RPC, greater alignment with CDI, a long-awaited update to the JCache API, and much, much more.
The survey has six questions and it looks as though the Java EE Expert Group will use the feedback to help it prioritize which issue to address in Java EE 7 and which to postpone until a more distant future.
The first question concerns four new JSRs that are candidates for inclusion in Java EE 7:
- The Java API for Web Socket 1.0
- The Java API for JSON Processing
- Java Batch 1.0
- JCache 1.0
and asks which you think it is important to add to into the full Java EE platform as well as into the lighter-weight Web Profile
Attention turns next to the Context and Dependency Injection for Java EE API (CDI) which was a key part of Java EE 6. The first question simply asks whether CDI should be enabled by default in Java EE, two further questions explore issues of CDI annotations and the final two questions in the survey are about support for interceptors.
The survey, which is now up on SurveyMonkey has been designed to make it as easy as possible to have you opinion on the future if Java EE taken into account.

Google Takes On Ad-Blocker Microsoft 16/05/2013
What seems like a small spat between Google and Microsoft over a new You Tube app for WP8 is actually a lesson to all of us, and might set a precedent in a much wider context.
|
Intel Beacon Mountain For Android 17/05/2013
Intel has just released Beacon Mountain - an Android development environment. You might be wondering why anyone would need another Android development environment? The answer in this case is the Atom. [ ... ]
| | More News |
|