No, not one of them implements this API initially and has no plans (which I know) for its implementation. Regarding JCP standards, this is DOA; it offers very little (a streamlined API for streaming data, does not bind data at all), and there are very few incentives for any of its use, except for adding a compatibility flag for a set of implemented JSRs.
There is a Jackson-based JSR-353 implementation available at https://github.com/pgelinas/jackson-javax-json/ , however, if you really think this is a good idea, base your code on this API.
source share