The Jakarta XML Web Services, Version 2.3 Technology Compatibility Kit (TCK) includes the following items:
Jakarta XML Web Services TCK Signature, API, End-to-end, WS-I Conformance, Java-to-WSDL/WSDL-to-Java Mapping and Web Services Addressing Conformance tests:
jakarta.xml.ws
, jakarta.xml.ws.handler
, jakarta.xml.ws.handler.soap
, jakarta.xml.ws.http
, jakarta.xml.ws.spi
, jakarta.xml.ws.spi.http
, jakarta.xml.ws.soap
, and jakarta.xml.ws.wsaddressing
.The Jakarta XML Web Services TCK tests have been built and tested with the the Compatible Implementation (CI) Eclipse GlassFish Server 5.1 running on the Java(tm) Standard Edition 8 (Java SE 8) platforms. If you are using a different Web server, you will need to make adjustments to the procedures outlined in this document.
The Jakarta XML Web Services TCK tests run on the following platforms:
In the instructions in this document, variables in angle brackets need to be expanded for each platform. For example, <TS_HOME>
becomes $TS_HOME
on Solaris/Linux and %TS_HOME%
on Windows 10. In addition, the forward slashes (/
) used in all of the examples need to be replaced with backslashes (\
) for Windows XP.
Added support for Java SE 8 based signatures.
Added tests for @Repeatable(value=WebServiceRefs.class) @WebServiceRef.
There are a few Jakarta XML Web Services tests that reference schemas over the internet and this caused build issues when attempting the rebuildable portion of Jakarta XML Web Services when test machines had no access to the internet.
The following test references schema [ http://www.w3.org/2006/03/addressing/ws-addr.xsd
]
src/com/sun/ts/tests/jaxws/wsa/j2w/document/literal/epr
The following test references schema [ http://ws-i.org/profiles/basic/1.1/swaref.xsd
]
src/com/sun/ts/tests/jaxws/wsi/w2j/document/literal/swareftest
If you attempt to build the jaxws tree for the VI as part of the rebuildable technology rules and you do not have access to the internet than the build will fail for these test cases. You need to use a Jakarta XML Web Services catalog to resolve the URI's locally. A Jakarta XML Web Services catalog file exists under the following directory:
TS_HOME/src/com/sun/ts/tests/jaxws/common/xml/catalog/META-INF/jax-ws-catalog.xml
The wsimport ant task within TS_HOME/src/com/sun/ts/tests/jaxws/common/xml/common.xml
refers to this catalog file appropriately for both the CI and VI wsimport ant task tool wrappers.
We do not distribute these standards defined schema files as part of our test suite. So the licensee will have to ensure to download and get a copy of the above schemas however they decide to and place them in the TS_HOME/lib/schemas directory of the test suite in order to build these tests with no internet access. The catalog file mentioned above will resolve these URI's locally to these schema files under the TS_HOME/lib/schemas.
jakarta.xml.ws.Endpoint
publishing API's
The following properties, which are used by the Endpoint API tests in the
jaxws/api/jakarta_xml_ws/Endpoint
directory, must be set in the ts.jte file:
http.server.supports.endpoint.publish
property indicates whether or not your HTTP server supports endpoint publishing.
http.server.supports.endpoint.publish.2
property indicates whether or not the Jakarta EE 8 CI server supports endpoint publishing.
If your server supports endpoint publishing (supports the use of
jakarta.xml.ws.Endpoint.publish()
methods), set the property value
to "true". In an unmanaged environment, such as that in standalone mode, this
call is usually allowed. When the property is set to "true", the test will check
that the endpoint publish methods publish the endpoints without throwing an
exception. When this result occurs with this scenario, the result is considered
a PASS.
If your server does not support endpoint publishing (does not support the use of
jakarta.xml.ws.Endpoint.publish()
methods), set the property value to
"false". In a managed environment, such as the Jakarta EE 8 Compatible Implementation,
this is usually the case and this call would not be allowed. When the property is
set to "false", the tests will check that these endpoint publish methods do not
publish the endpoints and an exception will be thrown. When this result occurs
with this scenario, the result is considered a PASS.
The http.server.supports.endpoint.publish.2
property settings are used to specify
whether or not endpoint publishing is supported by the Jakarta EE 8 CI HTTP server.
The same settings and caveats as the http.server.supports.endpoint.publish
property apply to this property, based on whether or not the Jakarta EE 8 CI
supports endpoint publishing.
Refer to the Jakarta XML Web Services TCK 2.3 User's Guide, available in the Jakarta XML Web Services TCK 2.3 documentation bundle, for complete instructions on installing, setting up, and running the Jakarta XML Web Services TCK. The online version of the JT Harness version 5.0 documentation is available here.
Follow the steps below to configure Apache Tomcat 8 for Jakarta XML Web Services TCK 2.3
<tomcat-users> <role rolename="tomcat"/> <role rolename="role1"/> <role rolename="Administrator"/> <role rolename="Manager"/> <role rolename="Employee"/> <user username="both" password="tomcat" roles="tomcat,role1"/> <user username="tomcat" password="tomcat" roles="tomcat"/> <user username="j2ee" password="j2ee" roles="Administrator,Employee"/> <user username="javajoe" password="javajoe" roles="Manager,Employee"/> <user username="role1" password="tomcat" roles="role1"/> </tomcat-users>
Copyright (c) 2011, 2020 Oracle and/or its affiliates. All rights reserved.