[
https://issues.apache.org/jira/browse/JAMES-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
René Cordier closed JAMES-3092.
-------------------------------
Fix Version/s: 3.6.0
Resolution: Done
> Implement a JMAP meta project to redirect towards the correct JMAP
> implementation
> ---------------------------------------------------------------------------------
>
> Key: JAMES-3092
> URL: https://issues.apache.org/jira/browse/JAMES-3092
> Project: James Server
> Issue Type: Sub-task
> Reporter: René Cordier
> Priority: Major
> Fix For: 3.6.0
>
>
> `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:
> {code:java}
> Accept: application/json;jmapVersion=draft` for jmap draft implementation
> version.
> Accept: application/json;jmapVersion=rfc-8620` for `jmap-rfc-8620`
> implementation version.
> {code}
> - 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
