Failed

com.sun.ts.tests.jaxws.mapping.j2wmapping.rpc.literal.withannotations.Client.VerifyInputOutputReturnAndFaultTypeElementMappings_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/rpc/literal/withannotations/Client.java
$root=/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src
assertion_ids=JAXWS\: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\:3013  RPC style Zero or more wsdl\:part child elements (one per method parameter and one for a non-void return value) that refer, via a type attribute, to named type declarations 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\:3027  This style is identified by a jakarta.jws.SOAPBinding annotation with the following properties\: a style of RPC, a use of LITERAL and a parameterStyle of WRAPPED. The Java types of each in, out and in/out parameter and the return value are mapped to named XML Schema types using the mapping defined by JAXB. For out and in/out parameters the class of the value of the holder is used rather than the holder itself. Each method parameter and the return type is mapped to a message part according to the parameter classification\: in The parameter is mapped to a part of the input message. out The parameter or return value is mapped to a part of the output message. in/out The parameter is mapped to a part of the input and output message. The named types are used as the values of the wsdl\:part elements type attribute, see figure 3.2. The value of the name attribute of each wsdl\:part element is the name of the corresponding method parameter or return for the method return value.\nJAXWS\:SPEC\:3028  A service specific Java exception is mapped to a wsdl\:fault element, a wsdl\:message element with a single child wsdl\:part element and an XML Schema global element declaration. The wsdl\:fault element appears as a child of the wsdl\:operation element that corresponds to the Java method that throws the exception and refers to the wsdl\:message element. The wsdl\:part element refers to an XML Schema global element declaration that describes the fault.\nJAXWS\:SPEC\:3029  Conformance Requirement (Exception naming)\: In the absence of customizations, the name of the global element declaration for a mapped exception MUST be the name of the Java exception. The jakarta.xml.ws.WebFault annotation MAY be used to customize the local name and namespace name of the element.\nJAXWS\:SPEC\:3030  JAXB defines the mapping from a Java bean to XML Schema element declarations and type definitions and is used to generate the global element declaration that describes the fault. For exceptions that match the pattern described in section 2.5 (i.e. exceptions that have a getFaultInfo method and WebFault annotation), the FaultBean is used as input to JAXB when mapping the exception to XML Schema. For exceptions that do not match the pattern described in section 2.5, JAX-WS maps those exceptions to Java beans and then uses those Java beans as input to the JAXB mapping. The following algorithm is used to map non-matching exception classes to the corresponding Java beans for use with JAXB\: In the absence of customizations, the name of the bean is the same as the name of the Exception suffixed with  Bean . In the absence of customizations, the package of the bean is a generated jaxws subpackage of the SEI package. E.g. if the SEI package is com.example.stockquote then the package of the bean would be com.example.stockquote.jaxws. For each getter in the exception and its superclasses, a property of the same type and name is added to the bean. The getCause and getLocalizedMessage getters from java.lang.Throwable and the getClass getter from java.lang.Object are excluded from the list of getters to be mapped. The bean is annotated with a JAXB @XmlType annotation whose name property is set to the name of the exception and whose namespace property is set to the namespace name mapped from the exception package name. Additionally, the @XmlType annotation has a propOrder property whose value is an array containing the names of all the properties of the exception class that were mapped in the previous bullet point, sorted lexicographically according to the Unicode value of each of their characters (i.e. using the same algorithm that the int java.lang.String.compareTo(String) method uses). The bean is annotated with a JAXB @XmlRootElement annotation whose name property is set, in the absence of customizations, to the name of the exception. The bean is annotated with a JAXB @XmlType annotation.  If the exception class has a @XmlType annotation, then it is used for the fault bean's @XmlType annotation. Otherwise, the fault bean's @XmlType annotation is computed with name property set to the name of the exception and the namespace property set to the target namespace of the corresponding portType. \n    * Conformance(Fault bean's @XmlType)\: If an exception class has a @XmlType annotation, then it MUST be used for the fault bean's @XmlType annotation.\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\:3058  Service Specific Exception.\n    * Conformance (Exception naming)\: In the absence of customizations, the name of the wsdl\:message element MUST be the name of the Java exception. \n\nThe jakarta.xml.ws.WebFault annotation may be used to customize the name of the wsdl\:message element and also to resolve any conflicts.\n\n    * Conformance (Exception naming)\: If an exception has @WebFault, then messageName MUST be the name of the corresponding wsdl\:message element. \n\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)\: JAX-WS implementations do not require an application to package exception bean classes. However, when the exception bean classes are packaged, they MUST be used.\nJAXWS\:SPEC\:7013  Conformance (JSR-181 conformance)\: A JAX-WS 2.0 implementation MUST be conformant to the JAXWS profile of JSR-181 1.1
classname=com.sun.ts.tests.jaxws.mapping.j2wmapping.rpc.literal.withannotations.Client
direction=reverse
finder=cts
id=VerifyInputOutputReturnAndFaultTypeElementMappings_from_standalone_reverse
keywords=all VerifyInputOutputReturnAndFaultTypeElementMappings standalone_vehicle reverse
service_eetest=yes
testArgs=-ap jaxws-url-props.dat
testName=VerifyInputOutputReturnAndFaultTypeElementMappings
testProps=\ ts.home
test_directory=com/sun/ts/tests/jaxws/mapping/j2wmapping/rpc/literal/withannotations

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

#-----testresult-----
description=file\:/home/jenkins/agent/workspace/jakartaee-tck_master/xml-ws-tck/src/com/sun/ts/tests/jaxws/mapping/j2wmapping/rpc/literal/withannotations/Client.java\#VerifyInputOutputReturnAndFaultTypeElementMappings_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/rpc/literal/withannotations/Client.java\#VerifyInputOutputReturnAndFaultTypeElementMappings_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/rpc/literal/withannotations

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