There are enough JSONB tests in the Platform TCK to see that integration doesn’t work.
Thanks,
Dmitry
From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Emily Jiang via jakartaee-platform-dev
Sent: 28 февраля 2022 г. 13:30
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Cc: Emily Jiang <emijiang6@xxxxxxxxxxxxxx>
Subject: [External] : Re: [jakartaee-platform-dev] Review of Platform TCK removal of duplicate Jakarta JSON Binding tests
I am concerned with this discussion and the fact that the implementations do not need to or can't run the standalone tests in JSON-B. Let's give you an example.
If a runtime A uses Yasson for their JSON-B 3.0 implementation and it does not integrate well with Yasson, it should not be able to claim certification for JSON-B 3.0. However, since JSON-B standalone TCK is not required/able to be executed,
how can we verify whether a runtime is JSON-B 3.0 compatible? As for the platform integration tests, I don't think it is sufficient to cover the full picture as they focus on how to interact with other Jakarta EE specs.
On 2/24/22 3:49 PM, Nathan Rauh wrote:
Scott,
Do you mean to instead say that “every
JSON-B 3.0 implementation must pass the Standalone JSON Binding TCK” ?
When phrased as, “every
Jakarta EE 10 implementation must pass the Standalone JSON Binding TCK”, (below) it is unachievable for application servers because the arquillian support is gone from the Standalone JSON Binding TCK leaving no way to run it in a container (The issue
raised by Kyle).
Every JSON-B 3.0 implementation must still pass the Standalone JSON Binding TCK, that is certainly true and wouldn't change.
Application servers should be able to pass the Java SE style tests in the Standalone JSON Binding TCK, with the JSON-B SPEC API + implementation that they are using.
There will also be a set of Platform TCK tests that verify that JSON-B can be used in the required EE containers. From the feedback so far, the number of Platform TCK JSON-B tests should be small to minimize code duplication between the TCKs.
Scott
Updated as per feedback from Brian Decker:
We need to verify that the Jakarta EE 10 Platform requirements for use of JSON Binding API are met by reviewing the [1][2] pull requests. Wiki [3] has notes on the Platform requirements. In summary, every Jakarta EE 10 implementation must pass the Standalone
JSON-B TCK which validates that Application Client, Servlet, Server Pages, and Enterprise Beans can use the JSON Binding API successfully.
Correction: In summary, every Jakarta EE 10 implementation must pass the Standalone JSON Binding TCK which validates the JSON Binding implementation can pass the JSON Binding TCK
successfully.
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
--
|
