[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-platform-dev] Review of Platform TCK removal of duplicate Jakarta JSON Binding tests
|
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
