V3 Core Deployment Improvements These are the features for both application deployment and app server deployment. This document is part of V3AdministrationImprovements.
| Feature-ID |
Requirement |
Priority |
Comments |
Issue Link |
Eng Response |
| CoreDeploy-1 |
Ability to run the application archive. |
P3 |
Ease-of-use feature. The idea is that user just provides a web application or enterprise application and we do everything we can to just run the application after having verified that it is runnable. This is purely a developer feature that enables the users to quickly deploy their application in GlassFish. An example would be, an introspection of a "verified" archive (the archive that passed verification - see EE-2 ) reveals that there are 10 resources (of various types) being used by the application. This operation then defines all the underlying constructs like connection pools, mail resources etc. to make them work by creating the data sources in default database like "Java DB". |
|
No. |
| CoreDeploy-2 |
Provide Directory Deployment for all types of archives. |
P1 |
See the related DEVEX-13 . This is already implemented in v2, and will continue to be supported in v3 |
|
Yes. Already supported in GF V2. |
| CoreDeploy-3 |
Provide Directory Deployment for all types of targets (like clusters, instances, domain etc.) |
P3 |
Deploying to a directory should deploy the application to a cluster, specific instances, domains, etc. Obviously this will require some means of specifying targets (ex: more than one auto-deploy directory). |
|
No. |
| CoreDeploy-4 |
More fine grained control over (session) bean lifecycle, pooling and caching |
P3 |
Community request . Some beans are more important than others. Would like multiple EJB pools. This is most likely subsumed by |
|
No. |
| CoreDeploy-5 |
Removed. Duplicate of Deploy-004 |
P2 |
Applications can be "rolled back" to a prior (known and working) version |
|
|
Jspwiki style: sortable
|
