GlassFish Wiki : GlassFishV3Themes

{ALLOW delete kumara }
{ALLOW delete jclingan }
{ALLOW comment Authenticated }
{ALLOW view All }
{ALLOW view Anonymous }

GlassFish V3 Themes

1) Next Generation Applications

GlassFish will continue supporting up-and-coming Java EE and web services standards as well as refresh versions of existing standards. GlassFish will continue to invest in technologies which facilitate integration with enterprise resources and external services. GlassFish will also reach beyond Java SE and Java EE to support popular scripting languages and popular open source frameworks.

Feature	Description
A.) Modularity and extensibility	GlassFish should support multiple configurations to address a broad set of user classifications. GlassFish V3 will address large, complex and mission critical deployments yet also scale down to simple, lightweight and reliable deployments. This requires a flexible architecture that enables enterprises, ISVs and OEMs to "pay for what they need". GlassFish will shed the "one size fits all" approach typically found with application servers available today. User classifications include: * OEMs - broad needs ranging from delivering core parts of GlassFish V3 in embedded devices such as network routers to bundling GlassFish V3 feature-rich capabilities as part of a larger enterprise solution. * ISVs - deploy to a platform the fits the requirements of the problem their product addresses. * ASPs - hosting providers and enterprises utilizing virtualization technologies want to offer web container services without the overhead of unnecessary containers. * Enterprises - drive down costs and complexity for simple deployments but require feature-rich capabilities for mission critical deployments. * Java developers - lightweight and productive development while leveraging scripting languages to either augment or replace existing applications while leveraging their existing expertise. * Native scripting language developers - The Java community has been broadening its base to include the needs of scripting developers. Native GlassFish support of scripting languages provides a high-performance, multi-threaded deployment platform and offers the benefits of the broader Java ecosystem including tools, new business opportunities, etc.
B.) Multiple Framework Support	Popular frameworks such as Spring, hibernate, stripes, OpenPortal, OpenSSO, Open ESB, etc should be work out of the box. Ideally these frameworks would plug in to the administration console for configuration and management of the frameworks
C.) Multi-language, Scripting Support	GlassFish will broaden its applicability beyond Java-centric development by providing native support for JRuby and PHP. With native scripting support, JRuby and PHP developers will benefit from many of the production features such as clustering for scalability, high performance the overall reliability and manageability of GlassFish V3. Scripting developers will also benefit from the ease-of-deployment and rapid development features offered with NetBeans and GlassFish.
D.) Rich client support	GlassFish should provide support for an enhanced user experience through the use of rich clients. Rich client technologies include OpenLazlo, AJAX frameworks such as JMaki, and interoperate with technologies such as JavaFX script.
E.) Java EE6, Standards	GlassFish will continue as the reference implementation for Java EE, offering early and complete Java EE support. GlassFish V2 is the delivery vehicle for the Java EE 5 Reference Implemntation and GlassFish V3 will be the delivery vehicle for the Java EE 6 Reference Implementation. GlassFish V3 modularity and extensibility theme is a natural fit for Java EE 6 extensibility and profile goals. Java EE 6 also delivers better SOA and RESTful web services support, and updates to existing specifications. GlassFish V3 will also add and refresh standards deemed relevant to the GlassFish community
F.) SOA/Web Services/ESB	Metro, the web services stack in GlassFish, will continue the sedimentation process. The main focus of Metro in V3 is to improve performance and usability. This includes implementation improvements (such as efficient handling of large attachments) as well as documentation and samples improvements. Several new features are planned as well, such as full integration of WS-Addressing, WS-Policy support in JAX-WS, and Kerberos support. GlassFish will also continue alignment with JBI and Open ESB by providing the facilities required to deliver integration of web services and enterprise resources for loosely coupled enterprise applications.
G.) Microsoft Interoperability	continued focus on MS Web services interoperability
H.) Connectors	a basic set of connectors and ability to leverage connector development/management with (OpenESB ?)

2) Ease of Use

The system should be considered by those experienced with application servers to have easy-to-use yet powerful features while those unfamiliar with application servers will easily be able to install, configure and manage basic functions. Ease of use applies equally for rapid round trip development by a single developer and for a large multi-administrator, multi-cluster enterprise development. For example, developers should not be required to log into the administration console or be required to use the CLI while enterprises require secure administration and command-line scripting capabilities. The following describes the areas of requirements for this theme:

Feature	Description

A.) Easy access to the correct Bits / Options / Bundles	B.) Easy to Install (installer)	Ease of use will drive broader developer and enterprise adoption of GlassFish. The installer should minimize steps and configuration options through the use of sensible defaults. Closely aligned to installation is ease of upgrade. The application server should be easy to upgrade to from GlassFish V2, and provide the framework for ease-of-upgrade to GlassFish V3.next.
C.) Easy to Manage (admin console)	When using the administration console, the user should only be presented with the features appropriate for the role. For example, developers should not be burdened with the complexity of clusters. Production operators should not be presented with the details of cluster configuration. Enterprises should be able to easily configure roles to fit their governance standards. Errors codes should uniquely define a potential issue with easy access to steps for resolution (or tips).
D.) Easy to Enhance / Customize (Update Center)	Developers should be able to leverage the Update Center to download GlassFish updates and additional functionality such as open source frameworks like Spring, Hibernate, Open ESB, Open SSO, OpenPortal, JDBC drivers, JCA or JBI connectors, samples, blueprints, etc. Notification of available Update Center updates should be readily available in the administration console.
E.) Administration CLI	Full, extensible, limitable CLI for administration functions. The CLI should be at parity with the administration console (or as close as possible)
F.) Easy Development Tooling and Utilities	Integration with popular IDEs through the use of IDE plugins. Support for GlassFish module creation.

3) Advanced Production Features

GlassFish will provide those set of features that will meet the needs of the class of users described below from a single set of bits and with available modules. Each user type will have specific requirements basic to their needs, e.g., OEM's will desire ability to easily customize administration features and tools (thus customizable screens and extensive CLI's) while data center administrators will want tools that allow management of multiple clusters of application servers, etc. Specifically, the following sub-themes should contain all features related to production readiness:

Feature	Description
A.) Mission Critical Features	Features such as reliability, centralized administration, clustering for scalability, clustering for high availability - instance fail over / fail back. Reliability is key as users should feel that GlassFish "simply works".
B.) High Performance	GlassFish should continue its focus on delivering performance as a means to gain production adoption. Performance is an important decision-making criteria for mission critical deployments.
C.) Advanced administration	Administration features should scale as needs grow. Developers, administrators, deployers, operators, etc should only be presented with the tools required to fulfill their role. Potential administration features include: * Delegated Administration * Role Based Administration * Centralized management of all deployment tiers (Load balancer, application server, HADB). * More complete SNMP Support * Scripting support for Self Management and Command-Line. * Feature parity between command-line interface and web console. * Customization of administration console based on role * Ability to compose and create tasks.