Redesign of Repository verticle - Multiple specialized repository verticles

[marcinczeczko]

1. Server Verticle configuration

"server" : {
  "config": {
    ...,
    "repositories": [
        {
            "path" : "/content/local/.*",
            "address" : "knotx.filesystem-repository"
        },  
        {
            "path" : "/content/.*",
            "address" : "knotx.http-repository"
        }
    ],
    "engine" : {
        "address": "knotx.template-engine"
    }
  }
}

• remove dependencies section and exchanged into
• repositories configuration section, where you can create an array (order is important due to overlapping regexp) where a path is mapped to the repository verticle responsible for delivering content for the given path.
• engine section, where you can define address of the knot.x rendering engine

  2. Split Repository verticle into two specialized

Instead of Repository verticle create two:

• HttpRepositoryVerticle - to support http
• FileSystemRepositoryVerticle - to support local filesystem

Each verticle should have it's own configuration with same syntax as others

1. Http Repo

"httpRepository" : {
  "config": {
    "address": "knotx.http-repository",
    "config": {
      {
        "domain": "localhost",
        "port": 3001
      }
    }
  }
}

1. Local Repo

"localRepository" : {
  "config": {
    "address": "knotx.filesystem-repository",
    "config": {
      {
        "catalogue": ""
      }
    }
  }
}

3. Processing, request/response handling

The request/response handling should remain the same for specialized verticles. The most important informmation is that, the message payload that is used to communicate with them, should have unified structure.

• Requesting repository require original request
• Response from repositories should have "response" object (http like), e.g.: response.statusCode (http respository is fine, local should map file system operations to 200, 404 or 500 or others) response.headers (http repo is easy, local repo will not return any) response.body (html template returned by repository)

  4. Update example monolith and integration tests

  5. Update documentation

configurations in core, example how to create your own repository verticle

[marcinczeczko]

Lower priority for now in my opinion - services communication & post processing is our main focus now.