![[Jenkins]](/jakartaee-tck/static/298584b0/images/svgs/logo.svg){kind=logo}
Failed
com.sun.ts.tests.jaxws.wsa.w2j.document.literal.respectbindingfeature.Client.afCltEnabledREQSvrNotEnabledrbfSvrEnabledCltEnabledTest_from_standalone_reverse (from xml-ws-tck)
Error Message
test result: Error. VI classes and/or archives have not been built.
Stacktrace
test result: Error. VI classes and/or archives have not been built.
Standard Output
#Test Results (version 2) #Fri Mar 26 03:38:59 UTC 2021 #-----testdescription----- $file=/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src/com/sun/ts/tests/jaxws/wsa/w2j/document/literal/respectbindingfeature/Client.java $root=/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src assertion_ids=JAXWS\:JAVADOC\:189 Specifies if this feature is enabled or disabled.\nJAXWS\:JAVADOC\:191 If addressing is enabled, this property determines whether the endpoint requires WS-Addressing. If required is true, the endpoint requires WS-Addressing and WS-Addressing headers MUST be present on incoming messages. A corresponding 3.1.1 Addressing Assertion must be generated in the WSDL.\nJAXWS\:SPEC\:6012 jakarta.xml.ws.soap.AddressingFeature feature MUST be supported with the SOAP 1.1/HTTP or SOAP 1.2/HTTP bindings.\nJAXWS\:SPEC\:6012.2 Enabling this feature on the client will cause the JAX-WS runtime to include WS-Addressing headers in SOAP messages as specified by WS-Addressing[33].\nJAXWS\:SPEC\:6012.3 Disabling this feature will prevent a JAX-WS runtime from processing or adding WS-Addressing headers from/to SOAP messages even if the associated WSDL specified otherwise.\nJAXWS\:SPEC\:6012.4 The AddressingFeature's required property can be configured to control whether all incoming messages MUST contain Addressing headers.\nJAXWS\:SPEC\:6012.6 This feature is automatically enabled if the WSDL indicates the use of addressing as per the WS-Addressing 1.0 - Metadata[35]. \nDevelopers may choose to prevent this from happening by explicitly disabling the AddressingFeature.\nJAXWS\:SPEC\:6016 Conformance (jakarta.xml.ws.RespectBindingFeature)\: When the jakarta.xml.ws.RespectBindingFeature is enabled, a JAX-WS implementation MUST inspect the wsdl\:binding at runtime to determine result and parameter bindings as well as any wsdl\:extensions that have the required\=true attribute.\nJAXWS\:SPEC\:6016.1 All required wsdl\:extensions MUST be supported and honored by a JAX-WS implementation unless a specific wsdl\:extension has be explicitly disabled via a WebServiceFeature.\nJAXWS\:SPEC\:7020 jakarta.xml.ws.soap.Addressing\n The Addressing annotation is used to control the use of WS-Addressing[24] [33]. It corresponds with the AddressingFeature described in section 6.5.1.\nJAXWS\:SPEC\:7020.1 Add the following Table 7.15 \n \n Property enabled \n Description Specifies if WS-Addressing is enabled or not \n Default true\nJAXWS\:SPEC\:7020.2 Add the following Table 7.15 \n \n Property required \n Description Specifies Adddressing headers MUST be present on incoming messages.\n Default false\nJAXWS\:SPEC\:7020.3 an endpoint MUST explicitly specify what WS-Addressing Actions are to be used via the Action and FaultAction annotations.\nJAXWS\:SPEC\:7020.4 The client MUST explicitly enable addresssing via the AddressingFeature, and for each invocation, the client MUST explicitly set the BindingProvider.SOAPACTION URI PROPERTY.\nJAXWS\:SPEC\:7022 jakarta.xml.ws.RespectBinding\n The RespectBinding annotation is used to control whether a JAX-WS implementation MUST respect/honor the contents of the wsdl\:binding associated with an endpoint. It has a corresponding RespectBindingFeature described in s ection 6.5.3.\nJAXWS\:SPEC\:7022.1 Add the following Table 7.17 \n \n Property enabled \n Description Specifies whether the wsdl\:binding must be respected or not. \n Default true\nWSAMD\:SPEC\:3001.1 See assertion html documents.\nWSAMD\:SPEC\:3001.2 See assertion html documents.\nWSAMD\:SPEC\:3001.4 See assertion html documents. classname=com.sun.ts.tests.jaxws.wsa.w2j.document.literal.respectbindingfeature.Client direction=reverse finder=cts id=afCltEnabledREQSvrNotEnabledrbfSvrEnabledCltEnabledTest_from_standalone_reverse keywords=all afCltEnabledREQSvrNotEnabledrbfSvrEnabledCltEnabledTest standalone_vehicle reverse service_eetest=yes testArgs=-ap jaxws-url-props.dat testName=afCltEnabledREQSvrNotEnabledrbfSvrEnabledCltEnabledTest testProps=\ webServerHost webServerPort platform.mode test_directory=com/sun/ts/tests/jaxws/wsa/w2j/document/literal/respectbindingfeature #-----environment----- #-----testresult----- description=file\:/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src/com/sun/ts/tests/jaxws/wsa/w2j/document/literal/respectbindingfeature/Client.java\#afCltEnabledREQSvrNotEnabledrbfSvrEnabledCltEnabledTest_from_standalone_reverse end=Fri Mar 26 03\:38\:59 UTC 2021 environment=ts_unix execStatus=Error. VI classes and/or archives have not been built. harnessLoaderMode=Classpath Loader harnessVariety=Full Bundle javatestOS=Linux 3.10.0-1127.el7.x86_64 (amd64) javatestVersion=5.0 script=com.sun.ts.lib.harness.TSScript sections=script_messages TestRun start=Fri Mar 26 03\:38\:59 UTC 2021 test=com/sun/ts/tests/jaxws/wsa/w2j/document/literal/respectbindingfeature/Client.java\#afCltEnabledREQSvrNotEnabledrbfSvrEnabledCltEnabledTest_from_standalone_reverse timeoutSeconds=1200 totalTime=1 work=/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tckwork/xml-ws-tck/com/sun/ts/tests/jaxws/wsa/w2j/document/literal/respectbindingfeature #section:script_messages ----------messages:(0/0)---------- #section:TestRun ----------messages:(0/0)---------- ----------log:(6/278)---------- ********************************************* TEST NOT RUN: This test cannot be run until you rebuild the test classes and/or archives associated with it. Please see the TCK documentation for more information on rebuildable tests. ********************************************* result: Not run. Test running... test result: Error. VI classes and/or archives have not been built.