The following properties are defined in the schema.json.
For each service, you have a host which is the domain for the service. You can have two different services that belong to two different domains deployed to one server instance.
Each service will have a unique identifier. For one schema file, the host and service are the same and shared by all actions/endpoints.
Each service can have multiple actions defined as array items. Each action has a name and a version which uniquely identify the action/endpoint. You can have two actions with the same name but different versions if the newer version is not backward compatible.
The handler in action will define the class name of the handler for the action in the generated project.
The scope is a concept of OAuth 2.0 specification to control which client can access the action.
The schema is a JSON schema which defines the body of the request. The light-hybrid-4j will use it to validate the request.
For this particular example, we have two actions: query and info.
With the schema.json is ready for service1, let’s create a config.json and generate the service1 in the next step.