Uses of Package
de.iip_ecosphere.platform.services.spring.descriptor

Package
Description
Uses the Spring Local Cloud Deployer as Service Manager Implementation.
Interfaces describing the deployment descriptor.
Yaml implementation of the file-based artifact descriptor.
  • Class
    Description
    Represents a communication endpoint.
    If the service is not completely implemented rather than delegates functionality to an additional process that must be started and managed along with the service.
    Server process specification of servers to be started/stopped with an application.
    Information about a single service.
    Resolves declared types to dynamic Java classes (just attributes).
  • Class
    Description
    Information about an artifact containing services.
    Represents a communication endpoint.
    Represents a typed field in a record-like type declared in an artifact as part of Type.
    If the service is not completely implemented rather than delegates functionality to an additional process that must be started and managed along with the service.
    Represents a relation/connection between services, including the local communication broker/server endpoint (no other information given), an outgoing data port (channel, direction, type) or an opposite side incoming data port (channel, id, service, direction, type).
    Declares the direction types of an relation.
    Server process specification of servers to be started/stopped with an application.
    Information about a single service.
    Represents a type declared by an artifact.
    Represents typed data, e.g., a parameter.
    A validation function, to point generically to the private validation functions defined by this class.
  • Class
    Description
    Information about an artifact containing services.
    Represents a communication endpoint.
    Represents a typed field in a record-like type declared in an artifact as part of Type.
    If the service is not completely implemented rather than delegates functionality to an additional process that must be started and managed along with the service.
    Represents a relation/connection between services, including the local communication broker/server endpoint (no other information given), an outgoing data port (channel, direction, type) or an opposite side incoming data port (channel, id, service, direction, type).
    Declares the direction types of an relation.
    Server process specification of servers to be started/stopped with an application.
    Information about a single service.
    Represents a type declared by an artifact.
    Represents typed data, e.g., a parameter.