[jira] [Created] (JAMES-4017) JMAP user notifcations should not fail if "no longer existing types" stored on the DB

["Tran Hong Quan (Jira)" <se...@james.apache.org>]

Tran Hong Quan created JAMES-4017:
-------------------------------------

             Summary: JMAP user notifcations should not fail if "no longer existing types" stored on the DB
                 Key: JAMES-4017
                 URL: https://issues.apache.org/jira/browse/JAMES-4017
             Project: James Server
          Issue Type: Improvement
          Components: JMAP
            Reporter: Tran Hong Quan
            Assignee: Antoine Duprat


## Why
**GIVEN** at first James supports a change type e.g. Thread, and user registers updates for the Thread changes via `PushSubscription/set`.
**WHEN** James gives up supporting the Thread change type
**THEN**:
- `PushSubscription/get` likely would fail as `TypeStateFactory` fails to parse the Thread type from DB
- `PushListener` likely would fail as `TypeStateFactory` fails to parse the Thread type from DB

Expect: Should not fail if DB contains the "no longer existing types".

## How
Be more lenient in `TypeStateFactory`:  skip the parsing failure upon retrieval phase and a WARN level log.

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org