This gives plenty of advanced warning to developers that they should stop using certain APIs. InfoQ: How do you balance the need for backwards compatibility with pruning? Chinnici: First of all, according to the pruning process it takes two releases before any technology is made optional. I look forward to the day when Java web developers will be able to target a richer platform like the web profile in their applications, instead of plain servlet containers. Considering that all of the APIs in the web profile have open source implementations, and often more than one, it's not too difficult for a servlet container vendor to start offering a web profile product. Of course, developers will truly embrace the web profile only when vendors start shipping products that implement it, but I think that the very existence of the web profile will attract new vendors to the field. InfoQ: How will you judge if the web profile is a success? Chinnici : Adoption. We also introduced technologies like CDI that have the potential to become the common foundation for all future Java EE applications. In this respect, I'm quite satisfied that in Java EE 6 we managed to break down a lot of barriers between APIs, most of which were historical anyway. One element that I've been paying a lot of attention to is how all the components of the platform work together. It's an API that scales well from beginners to experienced developers, and from simple projects to complex ones. I believe we managed to strike the right middle ground between making an API powerful and keeping it simple. I'm very pleased by the form that some of the new APIs took, e.g. Additionally, all the major APIs already in EE were updated: Servlet, EJB, JPA, Connectors, JAX-WS and more. In terms of new APIs, the main ones are JAX-RS, Bean Validation and Contexts and Dependency Injection for Java EE (CDI).
![netbean glassfish netbean glassfish](https://i.ytimg.com/vi/XOvmtmhxFOQ/maxresdefault.jpg)
InfoQ: What are the key new APIs and updates in EE 6? Are there any particular features that you are really pleased with? Chinnici: It's a pretty long list.
Netbean glassfish code#
The overall effect from all these changes taken together is that the amount of code in your application goes down, and so does the number of external libraries you have to bring in to get all the functionality you need to develop a complete web application. Just as importantly, we simplified the packaging of applications, for example by letting you put EJB components directly inside a web application and by making descriptors optional. We also added standard APIs for validation and dependency injection which are usable across all tiers. We have new, powerful but easy to use APIs like JAX-RS, but also improved ones like JSF 2.0. While we did just that with respect to servlets in Java EE 6, there are many more features that together contribute to simplifying the development of web applications. When thinking about "ease of development", most developers identify it with the introduction of an annotation-based programming model. Chinnici: The two initiatives that will benefit developers the most are the renewed push for ease of development in the web tier and the introduction of profiles. As the platform is officially launched I talked to Sun Microsystems' Roberto Chinnici, one of the two leads for the EE 6 specification, beginning by looking at the significance of these themes from a developer's perspective. The pruning work has seen largely underused features like EJB Entity beans, JAX-RPC, JAXR and Java EE Deployment marked as future optional components.Īt the same time, EE 6 has overhauled key parts of the platform and continued to push on the ease of development work which started with Java EE 5. For profiles the specification provides a general definition and introduces the Web Profile, defining a smaller container comprising a subset of key components such as servlets, JPA, JTA, JSF, CDI and EJB Lite.
![netbean glassfish netbean glassfish](https://2.bp.blogspot.com/-40vz5qjkE3E/U2Jw2gYNLjI/AAAAAAAAAzo/IE63LNpbuWw/s1600/how-to-add-glassfish-application-server-v4-in-netbeans-ide-9.jpg)
![netbean glassfish netbean glassfish](https://i.stack.imgur.com/D01JE.png)
Netbean glassfish portable#
For extensibility the CDI portable extension SPI in particular offers substantially easier integration of additional technologies into the Java EE environment. EE 6 has delivered something on each of those areas. When the Java EE 6 specification was first made public the three central themes could be summarised as improving extensibility, adding profiles and pruning redundant APIs.
Netbean glassfish full#
Following the final approval vote for Java EE 6 last week, Sun has today announced the official release of the Java EE 6 SDK, along with GlassFish version 3, the first application server with full support for the platform, and NetBeans 6.8.