Skip to content

Failed

com.sun.ts.tests.jaxws.wsa.j2w.document.literal.addressingfeature.Client.afClientNotEnabledServerEnabledNotREQTest_from_standalone_reverse (from xml-ws-tck)

Failing for the past 1 build (Since #99 )
Took 0 ms.

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:52 UTC 2021
#-----testdescription-----
$file=/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src/com/sun/ts/tests/jaxws/wsa/j2w/document/literal/addressingfeature/Client.java
$root=/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src
assertion_ids=JAXWS\:JAVADOC\:190  Specifies if this feature is enabled or disabled. If enabled, it means the endpoint supports WS-Addressing but does not require its use. Corresponding 3.1.1 Addressing Assertion must be generated in the generated WSDL.\nJAXWS\:SPEC\:4034  Proxies.\nProxy instances are not guaranteed to be thread safe. If the instances are \naccessed by multiple threads, usual synchronization techniques can be used to support multiple threads.\n\nThe use of WS-Addressing requirements can be indicated in a WSDL as per Addressing 1.0 - Metadata[35] . A proxy created using getPort() calls is configured with the addressing requirements as specified in the associated WSDL or explicitly passing jakarta.xml.ws.soap.AddressingFeature web service feature.\n    * Conformance (Proxy's Addressing use)\: A proxy MUST be configured with the use of addressing requirements as indicated in the associated WSDL. But if the proxy is created using jakarta.xml.ws.soap.AddressingFeature web service feature, the feature's addressing requirements MUST take precedence over WSDL's addressing requirements.\nJAXWS\:SPEC\:6011  Conformance (enabled property)\: Each derived type of jakarta.xml.ws.WebServiceFeature MUST provide a constructor argument and/or method to allow the web service developer to set the value of the enabled property.\nJAXWS\:SPEC\:6011.1  The public default constructor MUST by default set the enabled property to true.\nJAXWS\:SPEC\:6011.2  An implementation MUST honor the value of the enabled property of any supported WebServiceFeature.\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.1  Enabling this feature on the server will result in the runtime being capable of consuming and responding to WS-Addressing headers.\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.5  The AddressingFeature's responses property can be configured to control\nwhether the endpoint requires the use of anonymous, non-anonymous and all \nresponses.\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\: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\:10025  Addressing section\:  If the jakarta.xml.ws.soap.AddressingFeature is enabled, implementations are required to follow WS-Addressing[32,33,34] protocols.\nWSAMD\:SPEC\:3001.1  See assertion html documents.\nWSAMD\:SPEC\:3001.3  See assertion html documents.\nWSAMD\:SPEC\:3001.4  See assertion html documents.
classname=com.sun.ts.tests.jaxws.wsa.j2w.document.literal.addressingfeature.Client
direction=reverse
finder=cts
id=afClientNotEnabledServerEnabledNotREQTest_from_standalone_reverse
keywords=all afClientNotEnabledServerEnabledNotREQTest standalone_vehicle reverse
service_eetest=yes
testArgs=-ap jaxws-url-props.dat
testName=afClientNotEnabledServerEnabledNotREQTest
testProps=\ webServerHost  webServerPort  platform.mode
test_directory=com/sun/ts/tests/jaxws/wsa/j2w/document/literal/addressingfeature

#-----environment-----

#-----testresult-----
description=file\:/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src/com/sun/ts/tests/jaxws/wsa/j2w/document/literal/addressingfeature/Client.java\#afClientNotEnabledServerEnabledNotREQTest_from_standalone_reverse
end=Fri Mar 26 03\:38\:52 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\:52 UTC 2021
test=com/sun/ts/tests/jaxws/wsa/j2w/document/literal/addressingfeature/Client.java\#afClientNotEnabledServerEnabledNotREQTest_from_standalone_reverse
timeoutSeconds=1200
totalTime=2
work=/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tckwork/xml-ws-tck/com/sun/ts/tests/jaxws/wsa/j2w/document/literal/addressingfeature

#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.