GlassFish

Differences between revisions 1 and 2
Revision 1 as of 2008-12-04 18:37:36
Size: 1998
Comment:
Revision 2 as of 2008-12-04 19:17:04
Size: 1915
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
It is a dynamically extensible and embeddable platform that is modular. It is a dynamically extensible and embeddable platform that will support multiple configurations to address a broad set of user classifications. GlassFish will shed the "one size fits all" approach typically found with application servers available today.


== Release Note ==
Provide a modular, lightweight, highly productive Java EE server for users to to deploy against.
Line 7: Line 11:

This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.

== Use Cases ==

== Assumptions ==
Support for up-and-coming Java EE and web services standards as well as popular scripting languages and open source frameworks is a requirements in the enterprise world.
Line 15: Line 14:

You can have subsections that better describe specific parts of the issue.
GlassFish v3's current release, Prelude is a lightweight Web 2.0 platform. It provides a web container which can be extended to Java EE 6 technologies which are currently in preview status. See [[https://glassfish.dev.java.net/downloads/v3-prelude.html|https://glassfish.dev.java.net/downloads/v3-prelude.html]] for more info.
Line 19: Line 17:

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

=== UI Changes ===

Should cover changes required to the UI, or specific UI that is required to implement this

=== Code Changes ===

Code changes should include an overview of what needs to change, and in some cases even the specific details.

=== Migration ===

Include:
 * data migration, if any
 * redirects from old URLs to new ones, if any
 * how users will be pointed to the new way of doing things, if necessary.

== Test/Demo Plan ==

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.
Glassfish v3 will need to be fully built from source to be included in 'main'. Glassfish v3 uses maven to build and pulls down several external jars that are required at compile time or at runtime.
 * Packaging effort is required for the external jars
 * GlassFish includes it's own update center to deliver patches and additional modules. The update center needs to be either modified to provide Ubuntu packages or possibly disabled
 * Since current version is V3 prelude, more packaging will be required as product adds JavaEE 6 technologies
Line 44: Line 23:

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
GlassFish build relies on Maven to download dependencies from repositories. Updates are needed in Ubuntu's Maven packages for the build to leverage installed packages etc for the source build to meet 'main' requirements.
Line 48: Line 26:

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

----
CategorySpec

Summary

GlassFish v3 Prelude is a lightweight Web 2.0 development and deployment platform built on a modular OSGi-based architecture. It is a dynamically extensible and embeddable platform that will support multiple configurations to address a broad set of user classifications. GlassFish will shed the "one size fits all" approach typically found with application servers available today.

Release Note

Provide a modular, lightweight, highly productive Java EE server for users to to deploy against.

Rationale

Support for up-and-coming Java EE and web services standards as well as popular scripting languages and open source frameworks is a requirements in the enterprise world.

Design

GlassFish v3's current release, Prelude is a lightweight Web 2.0 platform. It provides a web container which can be extended to Java EE 6 technologies which are currently in preview status. See https://glassfish.dev.java.net/downloads/v3-prelude.html for more info.

Implementation

Glassfish v3 will need to be fully built from source to be included in 'main'. Glassfish v3 uses maven to build and pulls down several external jars that are required at compile time or at runtime.

  • Packaging effort is required for the external jars
  • GlassFish includes it's own update center to deliver patches and additional modules. The update center needs to be either modified to provide Ubuntu packages or possibly disabled

  • Since current version is V3 prelude, more packaging will be required as product adds JavaEE 6 technologies

Unresolved issues

GlassFish build relies on Maven to download dependencies from repositories. Updates are needed in Ubuntu's Maven packages for the build to leverage installed packages etc for the source build to meet 'main' requirements.

BoF agenda and discussion

GlassFish (last edited 2009-01-26 17:08:19 by nitya-doraisamy)