| Re: [jakartaee-tck-dev] Discussion on stand alone TCKs as part of the certification process |
I think that largely matches what I was thinking as well. But I have not seen that clearly documented outside of the some of the legacy EE8 guides. I just noticed today there has been some recent updates to the Jakarta guides so perhaps this is covered there. It depends entirely on what "product" you're trying to certify. If you have a Jakarta EE platform product, you'll need to certify with the Jakarta EE platform TCK. Since several required TCKs are not integrated with the platform TCK, the platform TCK rules require you to separately test with some of these other TCKs (such as CDI and BV). If you have a product that supports only the WebSocket API, you need to test with the WebSocket TCK. If you have a product that supports the Jakarta EE platform and also allows you to use pieces of that product independently of the entire platform, you'll need to certify with the platform TCK and the TCKs for all pieces that are usable independently. Does that make sense? Scott Highbarger wrote on 6/25/19 11:51 AM:
The CDI 2.0 was technically part of the EE8 Spec, while I believe the websocket 1.1 level was not. I'm wondering what the rest of the community is thinking in regards to these stand alone TCKs that don't directly over lap the jakartaeetck? Scott E. Highbarger [shighbar@xxxxxxxxxx] Advisory Software Engineer WebSphere Application Server CTS IBM Software Group (303) 773-5264 
|
Bill Shannon ---06/25/2019 01:37:01 PM---It depends entirely on what "product" you're trying to certify. If you have a Jakarta EE platform pr