Small correction, I meant Richards-Branch, he shared in an other thread:
https://github.com/rzo1/tomee/tree/cxf4


On 18.08.23 19:15, Benedict Eisenkrämer wrote:
Hi,

I now have a kind of working setup for the tck, related to this ticket: https://issues.apache.org/jira/browse/TOMEE-4166 The setup tests against this modified main-branch of the tomee-repository: https://github.com/Sollder11/tomee
I only changed a few things with the embedded-tomee there.
My current tck-setup can be found here: https://gitlab.com/Sollder1/tomee-10-jaxrs-tck-setup-tests

My last result was:
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]   JAXRSClientIT.<init>:59->usersetup:97 user not set ==> expected: <true> but was: <false> [ERROR]   JAXRSClientIT.<init>:59->usersetup:97 user not set ==> expected: <true> but was: <false> [ERROR] JAXRSBasicClientIT.<init>:59->JAXRSClient.setup:53 user was not set ==> expected: <true> but was: <false> [ERROR] JAXRSBasicClientIT.<init>:59->JAXRSClient.setup:53 user was not set ==> expected: <true> but was: <false> [ERROR] JAXRSBasicClientIT.<init>:59->JAXRSClient.setup:53 user was not set ==> expected: <true> but was: <false> [ERROR] JAXRSBasicClientIT.<init>:59->JAXRSClient.setup:53 user was not set ==> expected: <true> but was: <false> [ERROR] JAXRSBasicClientIT.<init>:59->JAXRSClient.setup:53 user was not set ==> expected: <true> but was: <false> [ERROR] JAXRSClientIT.sseBroadcastTest:193->JAXRSCommonClient.assertEquals:721 [Ljava.lang.Object;@43a8dd9b ==> expected: <true> but was: <false> [ERROR] JAXRSClientIT.dynamicFeatureIsRegisteredTest:111->JAXRSCommonClient.assertEquals:721 [Ljava.lang.Object;@7b8f8de5 ==> expected: <true> but was: <false> [ERROR] JAXRSClientIT.featureIsRegisteredTest:93->JAXRSCommonClient.assertEquals:721 [Ljava.lang.Object;@6c4cfe0e ==> expected: <true> but was: <false>
[ERROR] Errors:
[ERROR] JAXRSClientIT.clientSideReaderIsNotUsedOnServerTest:124->JaxrsCommonClient.invoke:219 » Fault [ERROR] JAXRSClientIT.clientSideReaderIsUsedOnClientTest:195->JaxrsCommonClient.invoke:219 » Fault [ERROR] JAXRSClientIT.clientSideWriterIsNotUsedOnServerTest:159->JaxrsCommonClient.invoke:219 » Fault [ERROR] JAXRSClientIT.clientSideWriterIsUsedOnClientTest:234->JaxrsCommonClient.invoke:219 » Fault [ERROR] JAXRSClientIT.serverSideReaderIsNotUsedOnClientTest:177->JaxrsCommonClient.invoke:219 » Fault [ERROR] JAXRSClientIT.serverSideReaderIsUsedOnServerTest:107->JaxrsCommonClient.invoke:219 » Fault [ERROR] JAXRSClientIT.serverSideWriterIsNotUsedOnClientTest:213->JaxrsCommonClient.invoke:219 » Fault [ERROR] JAXRSClientIT.serverSideWriterIsUsedOnServerTest:141->JaxrsCommonClient.invoke:219 » Fault [ERROR] SeBootstrapIT.shouldBootInstanceDespiteUnknownConfigurationParameters:236 » AbstractMethod [ERROR] SeBootstrapIT.shouldBootInstanceUsingConvenienceMethods:148 » AbstractMethod R... [ERROR]   SeBootstrapIT.shouldBootInstanceUsingDefaults:71 » AbstractMethod Receiver cla... [ERROR] SeBootstrapIT.shouldBootInstanceUsingExternalConfiguration:186 » AbstractMethod [ERROR] SeBootstrapIT.shouldBootInstanceUsingImplementationsDefaultIpPort:317 » AbstractMethod [ERROR]   SeBootstrapIT.shouldBootInstanceUsingProperties:107 » AbstractMethod Receiver ... [ERROR] SeBootstrapIT.shouldBootInstanceUsingSelfDetectedFreeIpPort:280 » AbstractMethod [ERROR]   JAXRSSigTestIT.signatureTest:412 Fault JAXRSSigTestIT.signatureTest() failed!,...
[INFO]
[ERROR] Tests run: 2796, Failures: 10, Errors: 16, Skipped: 128
[INFO]

The full result may be found here: https://gitlab.com/Sollder1/tomee-10-jaxrs-tck-setup-tests/-/tree/main/runs/sollder1/_18082023_1903?ref_type=heads

As can be expected the tests for the new SE-Bootstrap fail, as this is a new feature in JakartaEE10. Also all the Authorization / Security Tests fail, I do not really get what to do there ,as the documentation is rather vague here. The other issues may very well be related to the fact, that the cxf-version used is not actually compatible.

Some feedback/inside would be very much appreciated.

I will try to run against the Roberts branch next, which already includes the newest cxf version and seems to have only four failures with the old tck. I think this should result in a few more tests succeeding, although cxf4 is not yet fully JakartaEE10 compatible.

Gruß Benedict

Reply via email to