[JAMES-3092] Implement a JMAP meta project to redirect towards the correct JMAP implementation

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Done
• Fix Version/s: 3.6.0
• Assignee: Unassigned
• Reporter: René Cordier
• Created: 06/Mar/20 09:22
• Updated: 10/Apr/20 02:05
• Resolved: 10/Apr/20 02:05

Description

`Currently`: JMAP draft server implemented base on serverless-Jetty and served it only.

`What we expected`: Served both `Jmap draft` and `Jmap-rfc-8620` implementation versions in `reactive server`.

`Proposal`:

• Reuse of work from [Refactoring jmap-draft to be reactive with reactor-netty](https://ci.linagora.com/linagora/lgs/openpaas/james/issues/1638).
• Server will served 2 implementations via `header filter` configuration for incoming request:

    Accept: application/json;jmapVersion=draft` for jmap draft implementation version.
    Accept: application/json;jmapVersion=rfc-8620` for `jmap-rfc-8620` implementation version.
  

• Implementation [jmap-rfc-8620](https://tools.ietf.org/html/rfc8620) into separate module by suggested name:
  `org.apache.james.jmap.rfc-8620`

DoD: memory integration tests about version handling