[
https://issues.jboss.org/browse/ARTIF-675?page=com.atlassian.jira.plugin....
]
Brett Meyer updated ARTIF-675:
------------------------------
Description:
Define a new, generic model to better encapsulate "services", discovery, and
re-use. Arguably, some of this should probably be added to the core, base model as well.
Ideas (from various sources):
- Provides a catalog of information, what services exist and are available for use
- Presents the condition of the service lifecycle is eg. Implemented, testing, advised
against, etc.
- Provides information about the version of the services
- Allows you to record and retrieve multiple versions of the same service
- Allows you to dynamically refer to the latest version of the service
- Allows dynamically at runtime to search and select end-point chosen service
- Collects information who and what services are used
- Provides information that services are repeatedly used and which are not
- Determining the impact of changes the services to existing dependent services
- Providing information to consumers of the services about ongoing or planned changes to
of the services
- Identify the environments (OS, app server, etc.) supported by the artifact
- Differentiate between front and back end artifacts
- Security: what version of SSL is used, etc. (extremely valuable for security audits)
was:
Define a new, generic model to better encapsulate "services", discovery, and
re-use.
Ideas (from various sources):
- Provides a catalog of information, what services exist and are available for use
- Presents the condition of the service lifecycle is eg. Implemented, testing, advised
against, etc.
- Provides information about the version of the services
- Allows you to record and retrieve multiple versions of the same service
- Allows you to dynamically refer to the latest version of the service
- Allows dynamically at runtime to search and select end-point chosen service
- Collects information who and what services are used
- Provides information that services are repeatedly used and which are not
- Determining the impact of changes the services to existing dependent services
- Providing information to consumers of the services about ongoing or planned changes to
of the services
- Identify the environments (OS, app server, etc.) supported by the artifact
- Differentiate between front and back end artifacts
Define new "service" model
--------------------------
Key: ARTIF-675
URL:
https://issues.jboss.org/browse/ARTIF-675
Project: Artificer
Issue Type: Feature Request
Reporter: Brett Meyer
Assignee: Brett Meyer
Define a new, generic model to better encapsulate "services", discovery, and
re-use. Arguably, some of this should probably be added to the core, base model as well.
Ideas (from various sources):
- Provides a catalog of information, what services exist and are available for use
- Presents the condition of the service lifecycle is eg. Implemented, testing, advised
against, etc.
- Provides information about the version of the services
- Allows you to record and retrieve multiple versions of the same service
- Allows you to dynamically refer to the latest version of the service
- Allows dynamically at runtime to search and select end-point chosen service
- Collects information who and what services are used
- Provides information that services are repeatedly used and which are not
- Determining the impact of changes the services to existing dependent services
- Providing information to consumers of the services about ongoing or planned changes to
of the services
- Identify the environments (OS, app server, etc.) supported by the artifact
- Differentiate between front and back end artifacts
- Security: what version of SSL is used, etc. (extremely valuable for security audits)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)