Failed

com.sun.ts.tests.jaxws.mapping.j2wmapping.document.literal.wrapped.Client.VerifyWsdlPartNamesAndMessageNamesForMessages_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:45 UTC 2021
#-----testdescription-----
$file=/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src/com/sun/ts/tests/jaxws/mapping/j2wmapping/document/literal/wrapped/Client.java
$root=/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src
assertion_ids=JAXWS\:JAVADOC\:214  wsdl\:part name for the wrapper\nJAXWS\:JAVADOC\:215  wsdl\:part name for the wrapper\nJAXWS\:JAVADOC\:221  wsdl\:Message's name. Default name is the exception's class name.\nJAXWS\:SPEC\:3000  Conformance Requirement (WSDL 1.1 support)\: Implementations MUST support mapping Java to WSDL 1.1.\nJAXWS\:SPEC\:3001  Conformance Requirement (Standard annotations)\: An implementation MUST support the use of annotations defined in section 7 to customize the Java to WSDL 1.1 mapping.\nJAXWS\:SPEC\:3002  Conformance Requirement (Java identifier mapping)\: In the absence of annotations described in this specification, Java identifiers MUST be mapped to XML names using the algorithm defined in appendix B of SOAP 1.2 Part 2[4].\nJAXWS\:SPEC\:3004  Conformance Requirement (Package name mapping)\: The jakarta.jws.WebService annotation (see section 7.9.1) MAY be used to specify the target namespace to use for a Web service and MUST be used for classes or interfaces in no package. In the absence of a jakarta.jws.WebService annotation the Java package name MUST be mapped to the value of the wsdl\:definitions elements targetNamespace attribute using the algorithm\: 1. The package name is tokenized using the "." character as a delimiter. 2. The order of the tokens is reversed.  3. The value of the targetNamespace attribute is obtained by concatenating "http\://" to the list of tokens separated by "." and "/".\nJAXWS\:SPEC\:3005  Conformance Requirement (WSDL and XML Schema import directives)\: Generated WSDL MUST comply with the WS-I Basic Profile 1.0[8] restrictions (See R2001, R2002, and R2003) on usage of WSDL and 16 XML Schema import directives.\nJAXWS\:SPEC\:3007  Conformance (portType naming)\: The jakarta.jws.WebService annotation (see section 7.10.1) MAY be used to customize the name and targetNamespace attributes of the wsdl\:portType element. If not customized, the value of the name attribute of the wsdl\:portType element MUST be the name of the SEI not including the package name and the target namespace is computed as defined above in section 3.2.\nJAXWS\:SPEC\:3008  Conformance Requirement (Inheritance flattening)\: A mapped wsdl\:portType element MUST contain WSDL definitions for all the methods of the corresponding Java SEI including all inherited methods.\nJAXWS\:SPEC\:3012  Document style A single wsdl\:part child element that refers, via an element attribute, to a global element declaration in the wsdl\:types section.\nJAXWS\:SPEC\:3019  The jakarta.jws.SOAPBinding annotation MAY be used to specify at the type level which style to use for all methods it contains or on a per method basis if the style is document.\nJAXWS\:SPEC\:3020  This style is identified by a jakarta.jws.SOAPBinding annotation with the following properties\: a style of DOCUMENT, a use of LITERAL and a parameterStyle of WRAPPED.\nJAXWS\:SPEC\:3033  Conformance Requirement (SOAP binding support)\: Implementations MUST be able to generate SOAP HTTP bindings when mapping Java to WSDL 1.1.\nJAXWS\:SPEC\:3034  Conformance Requirement (SOAP binding style required)\: Implementations MUST include a style attribute on a generated soap\:binding.\nJAXWS\:SPEC\:3035  Conformance (Port selection)\: The portName element of the WebService annotation, if present, MUST be used to derive the port name to use in WSDL. In the absence of a portName element, an implementation MUST use the value of the name element of the WebService annotation, if present, suffixed with Port. Otherwise, an implementation MUST use the simple name of the class annotated with WebService suffixed with Port.\nJAXWS\:SPEC\:3057  Document Wrapped.\nApplication's programming model doesn't use these bean classes, so the applications need not package these classes. JAX-WS implementations may generate these classes dynamically as specified in this section. \n    * Conformance (Bundling wrapper beans)\: A JAX-WS implementation SHOULD not require an application to package request and response bean classes. However, when the bean classes are packaged, they MUST be used.\n\nThe name of wsdl\:part for the wrapper must be named as "parameters" and "result" for input and output messages respectively in the generated WSDL.  The jakarta.xml.ws.RequestWrapper and jakarta.xml.ws.ResponseWrapper annotations (see 7.3 and 7.4) MAY be used to customize the name of the wsdl\:part for the wrapper part. \n    * Conformance (Default Wrapper wsdl\:part names)\: In the absence of customizations, the name of the wsdl\:part for the wrapper MUST be named as "parameters" and "result" for input and output messages respectively in the generated WSDL.\n    * Conformance (Customizing Wrapper wsdl\:part names)\: Non-default partName values of the jakarta.xml.ws.RequestWrapper and jakarta.xml.ws.ResponseWrapper annotations, if specified on SEI method, MUST be used as wsdl\:part name for input and output messages respectively in the generated WSDL. \n\nIf a SEI's method parameter or return type is annotated with @XmlElement, that annotation is used for the wrapper bean properties. This can be used to map corresponding XML schema element declaration's attributes like minOccurs, maxOccurs, and nillable etc. It is an error to specify @XmlElement with a parameter or return type that is mapped to header part. If both @XmlElement and @WebParam/@WebResult are present, then it is an error to specify @XmlElement's name, and namespace elements different from @WebParam/@WebResult's name and targetNamespace elements respectively.\n    * Conformance (Wrapper property)\: If a SEI's method parameter or return type is annotated with @XmlElement, that annotation MUST be used on the wrapper bean property.
classname=com.sun.ts.tests.jaxws.mapping.j2wmapping.document.literal.wrapped.Client
direction=reverse
finder=cts
id=VerifyWsdlPartNamesAndMessageNamesForMessages_from_standalone_reverse
keywords=all VerifyWsdlPartNamesAndMessageNamesForMessages standalone_vehicle reverse
service_eetest=yes
testArgs=-ap jaxws-url-props.dat
testName=VerifyWsdlPartNamesAndMessageNamesForMessages
testProps=\ ts.home
test_directory=com/sun/ts/tests/jaxws/mapping/j2wmapping/document/literal/wrapped

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

#-----testresult-----
description=file\:/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src/com/sun/ts/tests/jaxws/mapping/j2wmapping/document/literal/wrapped/Client.java\#VerifyWsdlPartNamesAndMessageNamesForMessages_from_standalone_reverse
end=Fri Mar 26 03\:38\:45 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\:45 UTC 2021
test=com/sun/ts/tests/jaxws/mapping/j2wmapping/document/literal/wrapped/Client.java\#VerifyWsdlPartNamesAndMessageNamesForMessages_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/mapping/j2wmapping/document/literal/wrapped

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