GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Clarify that all resource references must be resolved at deployment time · Issue #54 · javaee/javaee-spec

This repository was archived by the owner on Jan 30, 2019. It is now read-only.
This repository was archived by the owner on Jan 30, 2019. It is now read-only.

Clarify that all resource references must be resolved at deployment time #54

Copy link
Copy link
Open
Open
Clarify that all resource references must be resolved at deployment time#54
Copy link

Description

@bshannon
bshannon
opened on Aug 1, 2017
Issue body actions

From the beginning, a goal of Java EE has been to provide reliable and predictable behavior
for applications. Applications express their requirements on aspects of the operational
environment using deployment descriptors and annotations. The Deployer has visibility into
these requirements of the application and can map them to the facilities of the operational
environment. The application expects all of its requirements to be met before it starts
execution. There's no need for the application to check whether its resource requirements
have been met.

The Java EE platform specification needs to make it clear that deployment MUST fail if the
resource requirements of the application can not be met. Among other things, this means
that all resource references must be mapped to actual resources in the operational environment.

Activity

  1. bshannon commented on Aug 2, 2017

    @bshannon
    bshannon
    on Aug 2, 2017
    MemberAuthor
    More actions

    The key is that an application should not be started if its resource requirements haven't
    been met. An alternative would be to deploy the application but not start it, perform
    whatever administrative actions are necessary to satisfy the resource requirements,
    and then start the application.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.