GlassFish Server Open Source Edition 3.1 - Eclipse Integration One Pager
1. Introduction1.1. Project/Component Working Name:Eclipse Plugins for GlassFish Server Open Source Edition 3.1 1.2. Name(s) and e-mail address of Document Author(s)/Supplier:Ludovic Champenois: ludovic.champenois@oracle.com 1.3. Date of This Document:05/27/10 1.4. Abbreviations for Unnamed Products and Projects2. Project Summary2.1. Project Description:Extend the plugin that integrates Glassfish Server 3 to work well with GlassFish Server 3.1 2.2. Risks and Assumptions:Assumptions
Risks
3. Problem Summary3.1. Problem Area:Some of the features exposed by the existing GlassFish/GlassFish integration are changing in the GlassFish Server 3.1 release.
There are some new features that are being added to GlassFish Server 3.1 that would be useful to developers.
There are some features of GlassFish Server 3.0 (and 3.1) that would be useful to developers that were not exposed in previous integrations. Some of the 'interfaces' that the IDE leverages to provide a Java EE development environment will change in the GlassFish Server 3.1 release. 3.2. Justification:The Eclipse/Glassfish integration has a number of features that are impacted directly or indirectly by the changes being made in GlassFish Server 3.1. As 3.1 matures the number 4. Technical Description:4.1. Details:The IDE integration is written as Eclipse plugins. These modules implement a number of services that the IDE then uses to interact with the server. 4.2. Bug/RFE Number(s):To see a more complete picture of the Bugs/RFEs for the project, look at the [ issues|https://glassfishplugins.java.net] 4.3. In Scope:The plugin will allow the user to interact with versioned applications in the Servers explorer, which allows users to see deployed applications and manipulate them. 4.4. Out of Scope:The Eclipse integration plugin for GlassFish Server 3.1 will not expose the developer to clusters and stand-alone instances. Users will not be able to leverage the application versioning feature as part of their project development workflow. 4.5. Interfaces:4.5.1 Public Interfaces4.5.2 Private Interfaces4.5.3 Deprecated/Removed Interfaces:4.6. Doc Impact:The documentation of the plugin is handled by the GlassFish documentation team. 4.7. Admin/Config Impact:The plugin does not change the admin or config, but it does leverage these two areas of the server significantly. 4.8. HA Impact:The plugin does not interact with HA. 4.9. I18N/L10N Impact:The IDE integration is coded following the i18n requirements from the Eclipse IDE. The plugin is not currently localized. We will follow Oracle guidelines for OEPE there. 4.10. Packaging, Delivery & Upgrade:4.10.1. PackagingThe plugin is included in OEPE, so it has no independent packaging requirements. 4.10.2. DeliveryThe IDE integration has no impact on the server delivery. There is a strong desire for the two projects (Eclipse and GlassFish Server 3.1) to work together nicely when 3.1 ships 4.10.3. Upgrade and Migration:The plugin will continue to support a large number of releases so users can upgrade their IDE from Eclipse 3.5, 3.6 updates and not lose functionality. 4.11. Security Impact:The IDE integration does not have a direct security impact. The IDE performs many operation on the server via the http adapter. In 3.0, queries on this interface would generate 4.12. Compatibility Impact4.13. Dependencies:4.13.1 Existing Dependencies
4.13.2 New Dependencies
4.14. Testing Impact:New Testing requirements will be on the OEPE team for integration testing. Plugin testing is TBD... 5. Reference Documents:The Deployment One Pager The Connectors One Pager The Restful API One Pager The Logging One Pager 6. Schedule:6.1. Projected Availability:Eclipse 3.6: June 2010: Support for GlassFish 3.0.1 and nightly builds of GlassFish 3.1 |