Hi Scott,
One more thought is to pull the webservices test into their own TCK if there are vendors who continue to provide JAXRPC support within their platform
That might be useful, as some of the webservices tests will require use of other Jakarta EE 9 technologies (e.g. jakarta.ejb.SessionBean instead of javax.ejb.SessionBean).
For the jaxrpc test folder, I think there will also be some jakarta.servlet changes, so in both cases, your idea would be useful, as the Jakarta EE 8 Platform would not likely work.
Does anyone else think that they would use a standalone JAXRPC TCK that contains the current jaxrpc tests + the webservices tests that depend on JAXRPC?
Would JAXRPC not being part of Jakarta EE 9, mean the tests would need to be moved to a separate repo, so the JAXRPC standalone TCK could be released and maintained independently of the Jakarta EE Platform TCK 9.0.0?
Best
Lance
Hi Scott,
I would consider making the tests configurable similar to how JAXRPC is and remove when JAXRPC is finally removed
We are supposed to remove the JAXRPC tests now (as per EE 9 release plan [1]). Soon, we will no longer be able to reference javax.xml.rpc classes in the Jakarta EE 9 TCK source. I think that the general concern was about removing any tests from the src/com/sun/ts/tests/webservices folder, in case they are expected to cover testing non-JAXRPC technologies.
I keep forgetting JAXRPC is finally being removed
From the keyword.properties [2], it looks like the answer is that the webservices source tree, only contains JAXRPC tests. Sound right?
I believe these tests all reply on JAXRPC and based on a quick scan appears to be the case.
Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037Oracle Java Engineering 1 Network Drive Burlington, MA 01803Lance.Andersen@xxxxxxxxxx
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
