News: Java EE 5 SDK Update 2 is Out
Updated versions of Java EE SDK and Java Application Platform SDK (overview) are now available for download. These new versions bundle JDK 6 and are fully tested with JDK 6 as well as JDK 5.0. In addition, the Java Application Platform SDK includes Sun Java System Access Manager (7.1 Beta), JBI Runtime with BPEL from project Open ESB and a beta version of Portlet Container to enable development and testing of JSR 168 portlets. Developer content such as Java EE 5 samples, blueprints, tutorial and API javadocs are also included. Sun Java System Application Server (9.0 Update 1 Patch 1) based on Project Glassfish is included in the SDK. It contains a performance bugfix that enables great price/performance on the application tier with SPECjAppServer result of 521.42 JOPS@Standard, 19% improvement from the previous version 8.2. This is the only SPECjAppServer result published so far on an open-source application server. It is also the first and only SPECjAppServer result published on an application server that is certified to the Java EE 5 specification. The Java EE Tools bundle has also been refreshed to use the Java Application Platform SDK Update 2. References:
- Posted by: Nazrul Islam
- Posted on: December 15 2006 09:19 EST
Also, take a look at this blog for more details on JDK 6 and SpecJAppServer submission. --Nazrul
I have a question, is there a way to when in debug mode to add a mew method or fields without recompilling entire class. In Java 5 only changing of method body is allowed(I must restart application when changing method signature). If they improved this it would be nice :)
I have a question, is there a way to when in debug mode to add a mew method or fields without recompilling entire class. In Java 5 only changing of method body is allowed(I must restart application when changing method signature). If they improved this it would be nice :)Do you mean redeploy instead of recompile? Are you asking for a comparision between the fix-in-place features of the JDK 6 JVM versus the JDK 5 JVM? NetBeans has this capability. So do a bunch of other IDE's. I have not tried it, especially when working with deployed code. vbk
How far the Sun app server has come. In June of 2000, we launched the iPlanet Application Server 6.0, in reference to the previously launched Netscape Application Server 4.1 and NetDynamics Application Server 5.2, both administered under the Sun-Netscape Alliance. By being the first J2EE compliant app server, iPlanet achieved a little fame and success, but gave the mantle to BEA with the WebLogic enterprise. Sun's sales force simply had an easier sell of hardware servers by using BEA's software servers. All of this has been rectified under the Glassfish regime. We launched Sun's Application Server 7.0 on October 28, 2002, marking the first Sun-only app server, and initiating the process that would lead to JEE leadership. Even as JBoss emerged as the de facto standard of the post-bubble Java build-out, Sun puts together a respectable and gaining important app server program, that will soon supercede Solaris as the most vital software platform in Sun's quiver. Those words seem to fall on deaf ears around the Sun executive team, save Pratik and a few others, but it is noticeable and irrefutable that Glassfish has shocked the TSS world. This announcement is further proof of what many of us have been trying to do since 1999: make Sun relevant in the Java space. It is a worthy mission, and if not complete, it is nonetheless on the way. Developers and non-WebLogic and WebSphere vendors should take notice of what Sun is doing and create compatibility with Glassfish. The promise of a fully inter-operable marketplace for Java apps and components is only possible with the implementation of a Sun-lead certification kit, and then only dominant with the full resources of the global Enterprise Java workforce, who has the most to gain from the objectives at the core of Glassfsih...