Failed

com.sun.ts.tests.jaxws.api.jakarta_xml_ws.LogicalMessage.Client.SetGetPayloadSourceTest_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:23 UTC 2021
#-----testdescription-----
$file=/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src/com/sun/ts/tests/jaxws/api/jakarta_xml_ws/LogicalMessage/Client.java
$root=/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src
assertion_ids=JAXWS\:JAVADOC\:30  Gets the message payload as an XML source, may be called multiple times on the same LogicalMessage instance, always returns a new Source that may be used to retrieve the entire message payload. If the returned Source is an instance of DOMSource, then modifications to the encapsulated DOM tree change the message payload in-place, there is no need to susequently call setPayload. Other types of Source provide only read access to the message payload.\nJAXWS\:JAVADOC\:32  Sets the message payload\nJAXWS\:SPEC\:5000  Conformance (Provider support required)\: An implementation MUST support Provider < Source >  in payload mode with all the predefined bindings. It MUST also support Provider < SOAPMessage >  in message mode in conjunction with the predefined SOAP bindings and Provider < javax.activation.DataSource@gt; in message mode in conjunction with the predefined HTTP binding. In payload mode, to send a response with no payload, an empty Source payload\ncan be used in payload mode. An empty source can be constructed using zero-argument default constructors of DOMSource, SAXSource, StreamSource.\nJAXWS\:SPEC\:5001  Conformance Requirement (Provider default constructor)\: A Provider based service endpoint implementation MUST provide a public default constructor.\nJAXWS\:SPEC\:5002  Conformance Requirement (Provider implementation)\: A Provider based service endpoint implementation MUST implement a typed Provider interface.\nJAXWS\:SPEC\:5003  Conformance (WebServiceProvider annotation)\: A Provider based service endpoint implementation MUST carry a WebServiceProvider annotation (see 7.7).\nJAXWS\:SPEC\:6002  Conformance (Provider createAndPublishEndpoint Method)\: The effect of invoking the createAndPublishEndpoint method on a Provider MUST be the same as first invoking the createEndpoint method with the binding ID appropriate to the URL scheme used by the address, then invoking the publish-(String address) method on the resulting endpoint.\nJAXWS\:SPEC\:7000  Conformance (Correctness of annotations)\: An implementation MUST check at runtime that the annotations pertaining to a method being invoked, either on the client or on the server, as well as any containing program elements (i.e. classes, packages) is in conformance with the specification for that annotation\nJAXWS\:SPEC\:7002  The ServiceMode annotation is used to specify the mode for a provider class, i.e. whether a provider wants to have access to protocol message payloads (e.g. a SOAP body) or the entire protocol messages (e.g. a SOAP envelope).\nJAXWS\:SPEC\:7008  The WebServiceProvider annotation is specified on classes that implement a strongly typed jakarta.xml.ws.Provider. It is used to declare that a class that satisfies the requirements for a provider (see 5.1) does indeed define a Web service endpoint, much like the WebService annotation does for SEI-based endpoints.\nJAXWS\:SPEC\:7009  The BindingType annotation is applied to an endpoint implementation class. It specifies the binding to use when publishing an endpoint of this type.\nWS4EE\:SPEC\:5005  See assertion html documents.
classname=com.sun.ts.tests.jaxws.api.jakarta_xml_ws.LogicalMessage.Client
direction=reverse
finder=cts
id=SetGetPayloadSourceTest_from_standalone_reverse
keywords=all SetGetPayloadSourceTest standalone_vehicle reverse
service_eetest=yes
testArgs=-ap jaxws-url-props.dat
testName=SetGetPayloadSourceTest
testProps=\ webServerHost  webServerPort  platform.mode
test_directory=com/sun/ts/tests/jaxws/api/jakarta_xml_ws/LogicalMessage

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

#-----testresult-----
description=file\:/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src/com/sun/ts/tests/jaxws/api/jakarta_xml_ws/LogicalMessage/Client.java\#SetGetPayloadSourceTest_from_standalone_reverse
end=Fri Mar 26 03\:38\:23 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\:23 UTC 2021
test=com/sun/ts/tests/jaxws/api/jakarta_xml_ws/LogicalMessage/Client.java\#SetGetPayloadSourceTest_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/api/jakarta_xml_ws/LogicalMessage

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