GlassFish Server Open Source Edition 3.2 - Embedded GlassFish One Pager
1. Introduction1.1. Project/Component Working Name:Embedded GlassFish 1.2. Name(s) and e-mail address of Document Author(s)/Supplier:Name: bhavanishankar@java.net 1.3. Date of This Document:04/26/11 2. Project Summary2.1. Project Description:The objective of the embedded GlassFish project is to enable running of GlassFish in the JVM of the user's application. Refer 3.1EmbeddedOnePager and project page for more details. Main objectives of GlassFish Server Open Source Edition 3.2 release are : 2.1.1. The GlassFish embedded inside user's application using org.glassfish.embeddable APIs should have fidelity with the regular GlassFish. In 3.1, there is already great degree of fidelity in web profile. The goal of 3.2 is to achieve fidelity in full profile. 2.1.2. Technology compliance. Embedded GlassFish full distribution should meet full Java EE product requirements (section EE 9.7 of Java EE 6 specification), while the web distribution meet "WP 2.1 Required Components" of Java EE Web Profile specification. 2.1.3. Enhance embedded user guide to provide more common scenarios on unit testing different types of applications. 2.2. Risks and Assumptions:One way to achieve #2.1.1 would be to provide some switch (command line option) to be able run existing devtests (v2/tests) on Embedded GlassFish. Individual owners of each technology area should make sure to run their respective devtests with Embedded GlassFish using the command line option as stated above. 3. Problem Summary3.1. Problem Area:Problem areas addresses by embedded are :
3.2. Justification:Embedded is an important developer feature, used by members of the GlassFish community. It also offers potential opportunities with respect to the ISV use case. 4. Technical Description:4.1. Details:Refer section 4.1 of 3.1EmbeddedOnePager for all the details. Detailed maven plugin documentation is available here. 4.2. Bug/RFE Number(s):Feature Request 4.3. In Scope:Refer description. 4.4. Out of Scope:Clustering with Embedded GlassFish. 4.5. Interfaces:4.5.1 Public InterfacesPackage names (stable): org.glassfish.embeddable org.glassfish.embeddable.archive org.glassfish.embeddable.spi javax.ejb.embeddable Package names (evolving): org.glassfish.embeddable.web org.glassfish.embeddable.web.config 4.6. Doc Impact:More samples, use cases to be added to the embedded server guide. 4.7. Admin/Config Impact:Embedded GlassFish will have no admin console. 4.8. HA Impact:None. 4.9. I18N/L10N Impact:None. 4.10. Packaging, Delivery & Upgrade:4.10.1. Packaging4.10.2. DeliveryRefer section 4.10.2 of 3.1EmbeddedOnePager 4.10.3. Upgrade and Migration:None 4.11. Security Impact:None 4.12. Compatibility ImpactNone 4.13. Dependencies:4.13.1 Internal DependenciesIt should be responsibility of every module owner to run their devtests in Embedded GlassFish mode. 4.13.2 External Dependencies4.14. Testing Impact:GlassFish devtests should be run with embedded GlassFish by the module developers. 5. Reference Documents:For blogs and other details visit project page 6. Schedule:6.1. Projected Availability:
|