Scott,
In your posting re: JSON-B, you said “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.” But there’s some
confusion in my mind as to whether or not the standalone
JSON-B TCK actually covers these things you’ve mentioned.
Thanks for noticing that, I will respond with a correction to
my original email with the typo.
Agreed that is wrong since the JSON-B TCK does not contain
Jakarta EE container integration. The Platform TCK needs to
validate the Platform requirements as mentioned in the
https://github.com/eclipse-ee4j/jakartaee-tck/pull/849
conversation so far.
It’s similar to the sort of thing that
Kyle received pushback for in the PR[1] to remove the
concurrency coverage from the platform TCK where different
vehicles (and indeed the entire server environment) have not
been reproduced in the new TCK.
Thanks.
-Brian
[1] https://github.com/eclipse-ee4j/jakartaee-tck/pull/816
Brian Decker
Jakarta Platform TCK Lead
Rochester Blizzard (EJB Container)
Home Office
(612) 216-4881
Roch. Office
t/l 553-4686
bmdecker@xxxxxxxxxx
-----
From: Nathan Rauh nathan.rauh@xxxxxxxxxx
Sent: Thursday, February 24, 2022 9:58 AM
To: Brian M Decker bmdecker@xxxxxxxxxx
Subject: FW: [jsonb-dev] [External] : Verifying TCK
on Application Servers
Brian,
Could you or someone from the Jakarta TCK
group look into whether Dmitry’s comments, which mean we
wouldn’t need to run the new JSON-B TCK at all to claim EE
10 compatibility for Open Liberty given that we do include
Yasson, are valid? On the surface, it sounds nice, but I
want to be certain this won’t later prove to be an obstacle
to claiming Jakarta EE 10 compatibility because we cannot
actually run this TCK against Open Liberty. Thanks!
From: jsonb-dev <jsonb-dev-bounces@xxxxxxxxxxx>
on behalf of Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx>
Reply-To: jsonb developer discussions <jsonb-dev@xxxxxxxxxxx>
Date: Thursday, February 24, 2022 at 6:56 AM
To: jsonb developer discussions <jsonb-dev@xxxxxxxxxxx>
Subject: Re: [jsonb-dev] [External] : Verifying
TCK on Application Servers
Hi Kyle,
There are two simple rules:
- Make sure
that your platform implementation passes Platform TCK.
- Make sure
that JSONB implantation you use passes standalone JSONB
TCK tests. If you are using Yasson, you don’t need to do
anything. Yasson is going to be certified as JSONB
compatible implementation.
Thanks,
Dmitry
From: jsonb-dev <jsonb-dev-bounces@xxxxxxxxxxx>
On Behalf Of Kyle Aure
Sent: 23 февраля 2022 г. 21:40
To: jsonb-dev@xxxxxxxxxxx
Subject: [External] : [jsonb-dev] Verifying TCK on
Application Servers
Good Afternoon all,
I am working on verifying Open Liberty
using the updated TCK for Jakarta 10 and am a bit confused
with the recent changes made under PR:
https://github.com/eclipse-ee4j/jakartaee-tck/pull/849
In order to be verified as Jakarta EE 10
platform, we need to run and pass this TCK. However, since
this TCK has been modified to run as a standalone test
against only a compatible implementation we no longer have a
method of deploying and running these tests in a container.
So I guess my question is how are we
supposed to run these tests in a container for proper
verification?
Or is the idea that we do not need to run
these tests in a container, and instead each platform will
just need to run these tests against the implementation they
are using? (in our case that would mean just running the
same test as here:
https://github.com/eclipse-ee4j/yasson/blob/master/yasson-tck/pom.xml)
Thanks for your help, I just want to make
sure I understand the expectations here.
KYLE
JON AURE
WebSphere Development
Office: Roch Bldg 50-2 H220
Email: kyle.aure@xxxxxxx
-----
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.
Any contributor in the community can review the [1][2]
pull requests and provide feedback there (or ask
questions there). Any feedback provided here in
response to this email is not considered part of the
pull request review. The Platform team (and others) may
want to consider whether all of the Platform SPEC
requirements for JSON Binding will still be validated
after the [1][2] pull requests are merged.
Thanks all,
Scott
[1] https://github.com/eclipse-ee4j/jakartaee-tck/pull/848
[2] https://github.com/eclipse-ee4j/jakartaee-tck/pull/849
[3] https://github.com/eclipse-ee4j/jakartaee-platform/wiki/Guidelines_For_Standalone_TCKs
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev