How to represent Service in language about ballerina-lang HOT 7 CLOSED

A file can contain one or more resources. If a file contains resources then that file can be a service - with appropriate annotations as needed.

If a file has other things (like actors and functions) then those play no part of the service aspect.

from ballerina-lang.

Each file with one or more resources becomes a service.

from ballerina-lang.

Service name is not going to be the name of the file rather context defined as an annotation.

from ballerina-lang.

We might have to support service name annotation as this is useful in representing a given service (title) via OpenAPI spec.

https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#infoObject

from ballerina-lang.

We define the service at the beginning of the file as in the below example.

package samples.echo;

service EchoService;

@GET
@Path ("/*")
resource echoResource (message m) {
    reply m;
}

from ballerina-lang.

Is the following correct:
A single file can contain resources with very different annotations. E.g. some resources have annotations that refer to HTTP parameters; some other resources have JMS annotations; etc.

I looks very strange to me to call that a single service: a single service that reacts to a bunch HTTP request, to JMS publish, etc.

Wrt Kasun's comment: In Swagger, the title field refers to the title of the application. And for me, an application may support more than one service.

Summary: we should not only decouple file name and service name, but also support multiple services within a single Balerina file.

from ballerina-lang.

Hi Frank - latest syntax does exactly what you said .. file name is irrelevant and a file can contain multiple services.

Closing the issue.

from ballerina-lang.