From sac-owner Thu Sep 25 16:27:58 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m8PNRv7t011442 for ; Thu, 25 Sep 2008 16:27:58 -0700 (PDT) Received: from sunmail4.singapore.sun.com (localhost [127.0.0.1]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m8PNRuNP003444 for ; Fri, 26 Sep 2008 07:27:56 +0800 (SGT) Received: (from noaccess@localhost) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/Submit) id m8PNRu5w003443 for one-pager-not-2b-used-directly; Fri, 26 Sep 2008 07:27:56 +0800 (SGT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m8PNRrVA003436 for <@sunmail2sca.sfbay.sun.com:one-pager@sun.com>; Fri, 26 Sep 2008 07:27:56 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K7R00F09YIJGR00@nwk-avmta-1.sfbay.Sun.COM> for one-pager@sun.com (ORCPT one-pager@sun.com); Thu, 25 Sep 2008 16:27:55 -0700 (PDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K7R000H0YII8CB0@nwk-avmta-1.sfbay.Sun.COM> for one-pager@sun.com (ORCPT one-pager@sun.com); Thu, 25 Sep 2008 16:27:54 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m8PNRsvj016705 for ; Thu, 25 Sep 2008 16:27:54 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K7R00D01YFKPY00@fe-sfbay-09.sun.com> (original mail from Lloyd.Chambers@Sun.COM) for one-pager@sun.com (ORCPT one-pager@sun.com); Thu, 25 Sep 2008 16:27:54 -0700 (PDT) Received: from [192.168.1.8] ([129.150.19.60]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K7R00IQ8YIGZ250@fe-sfbay-09.sun.com> for one-pager@sun.com (ORCPT one-pager@sun.com); Thu, 25 Sep 2008 16:27:53 -0700 (PDT) Date: Thu, 25 Sep 2008 16:27:52 -0700 From: Lloyd Chambers Subject: [2008/611]Glassfish v3 Prelude Sender: Lloyd.Chambers@Sun.Com To: one-pager@Sun.Com Message-id: <009D7D52-A69A-4830-97AE-0FFB09990A8F@sun.com> MIME-version: 1.0 X-Mailer: Apple Mail (2.929.2) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 9086 Template Version: @(#)onepager.txt 1.35 07/11/07 SMI 1. Introduction 1.1. Project/Component Working Name: Glassfish v3 Prelude 1.2. Name of Document Author/Supplier: Lloyd Chambers, Jerome Dochez 1.3. Date of This Document: 2008-08-29 1.3.1. Date this project was conceived: early 2007 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Web and Application Platform PAC (WAPPAC) 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Anil.Gaur@sun.com 1.4.4. The name of your business unit: Software Infrastructure 1.5. Email Aliases: 1.5.1. Responsible Manager: Abhijit.Kumar@sun.com 1.5.2. Responsible Engineer: Lloyd.Chambers@sun.com 1.5.3. Marketing Manager: john.clingan@sun.com 1.5.4. Interest List: Jerome.Dochez@sun.com Kedar.Mhaswade@sun.com 2. Project Summary 2.1. Project Description: Project web site (open source): https://glassfish.dev.java.net/ GlassFish V3 Prelude ("Prelude" hereafter) is an interim release of the Glassfish V3 application server, following on the heels of "TP2" (Technology Preview 2) at the May 2008 Jave ONE conference. The Prelude release allows customers to have early access to a powerful new platform a year in advance of the final release. NOTE: the Prelude release carries with it no long-term support committment. Prelude is designate to have six (6) months of support once released. Customers are expected to move to the final Glassfish V3 release when available. GlassFish V3 is the next version of Sun's Java EE application server. The new features/themes of this release are modularity, extensibility and embeddability. The Prelude release delivers a Java EE 5 based web tier, scripting support, OSGi support, JDBC and persistence API on top of the new modular kernel of GlassFish. In addition, through update center the users will be able to obtain new Java EE 6 APIs and containers (for example, EJB 3.1 and JAX-RS 1.0). However, Prelude is NOT a Java EE compliant application server, primarly due to its lack of EJB support. Also, it does not support clustering. Previous versions of the application server were a monolithic implementation of all the features making upgradability of one particular feature almost impossible to achieve. GlassFish V3 offers a modular environment with any desired degree of granularity, where each module represent a well-defined area of functionality. This change required a rewrite of server management and runtime code to support a module-based environment. Fortunately, most of these underpinnings have little or no direct impact on the deployment of Java EE applications, while at the same time offering the ability to run the "new and exciting" web-based technologies. Furthermore, the "pluggable" nature of Glassfish V3 means that anyone can add new functionality; this was difficult or impossible with Glassfish V2. 2.2. Risks and Assumptions: Backward compatibility: the shift to a modular architecture required a rewrite of key management and runtime areas. Because some of these changes are structural in nature, limited areas in the management and monitoring areas "make no sense" in the V3 environment. Appropriate migration strategies are being developed for the Glassfish V2 to Glassfish V3 final release; Prelude has limited support for backward compatibility. 3. Business Summary Provide a compelling Java EE application server targeting a wide range of deployment environments, from handheld devices to large server farms. 3.1. Problem Area: Application server. 3.2. Market/Requester: The entire market for Java EE application servers. 3.3. Business Justification: The availability of a high performance, scalable, customizable and embaddable Java EE application server is key to Sun's web strategy. 3.4. Competitive Analysis: Glassfish V3 will provide a compelling Java EE environment to suite a wide range of performance and footprint requirements. 3.5. Opportunity Window/Exposure: N/A 3.6. How will you know when you are done?: Specific features have been detailed in specifications for Prelude. Completion of those features is a requirement. The testing and documentation teams have similar goals. 4. Technical Description: 4.1. Details: Work is well underway, with most functionality already complete. Work is in the bug-fix stage for this release of Prelude; new features outside those specified are not being added. A complete list of specifications may be found at TBD. 4.2. Bug/RFE Number(s): N/A 4.3. In Scope: 4.4. Out of Scope: This release will not be a Java EE compliant application server. In particular, it will not provide EJB support. 4.5. Interfaces: EXPORTED INTERFACES For this release, ALL exported interfaces are being designated as Uncommitted, because compatibility efforts are still in progress. A high degree of compatibility is a priority for the final release. Fundamental changes in the infrastructure (modularity) mean that compatibility will range from fair to excellent, depending on the area. Hundred Kilobyte Kernel (HK2) http://hk2.dev.java.net admin GUI rearranged to support Prelude capabilities asadmin CLI a complete list of commands is available AMX MBeans Java packages com.sun.appserver.management.* domain.xml changes to Not an Interface in V3, no DTD, XML only glassfish-api other Java interfaces exposed by glassfish JavaDB http://developers.sun.com/javadb IMPORTED INTERFACES (numerous, complete list TBD) Hundred Kilobyte Kernel (HK2) http://hk2.dev.java.net Felix (OSGi) http://felix.apache.org/site/index.html Grizzly https://grizzly.dev.java.net JavaDB http://developers.sun.com/javadb/ A notable import is the HK2 (Hundred Kilobyte Kernel) project, providing runtime and configuration support in Glassfish V3. 4.6. Doc Impact: Rvised documentation will be shipped with the product. It will explain the differences of Prelude compared to Glassfish V2. 4.7. Admin/Config Impact: Partial compatibility is achieved in the areas of the 'asadmin' CLI, AMX MBean interface and web-based GUI. All of these areas have undergone and/are undergoing massive rewrites. We expect to achieve a very high level of compatibility with Glassfish V2 by the final release; Prelude is an interrim release which achieves partial compatibility. 4.8. HA Impact: Clustering is not supported in Prelude. 4.9. I18N/L10N Impact: No. The usual internationalization guidelines are being followed. 4.10. Packaging & Delivery: Please see http://appserver.sfbay.sun.com/Wiki.jsp?page=GFV3IPSPackagingDescription // What packages, clusters or metaclusters does this proposal // impact? What is its impact on install/upgrade? 4.11. Security Impact: The usual Java EE security is in place. Administration through programmatic APIs such as AMX is not available securely in this release. 4.12. Dependencies: No dependencies on other Sun projects. 5. Reference Documents: Glassfish V2 WSARC/2006/586 http://sac.sfbay/Archives/CaseLog/arc/WSARC/2006/586 Hundred Kilobyte Kernel (HK2) https://hk2.dev.java.net/ 6. Resources and Schedule: 6.1. Projected Availability: September 2008 6.2. Cost of Effort: proprietary 6.3. Cost of Capital Resources: proprietary 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: Glassfish V3 Prelude 6.4.3. Type of CPT Review and Approval expected: Standard 6.4.4. Project Boundary Conditions: http://glassfish.dev.java.net 6.4.5. Is this a necessary project for OEM agreements: The final version of Glassfish V3 is target for OEM and embedded environments, in addition to clustered server environments. 6.4.6. Notes: 6.4.7. Target RTI Date/Release: 6.4.8. Target Code Design Review Date: 6.4.9. Update approval addition: N/A 6.5. ARC review type: Standard 6.6. ARC Exposure: Open (This project is Sun's open-source application server, and the vast majority of planning, specification and other documents are already online). 6.6.1. Rationale: N/A 7. Prototype Availability: 7.1. Prototype Availability: August, 2008 7.2. Prototype Cost: N/A