The JAX-WS, Version 2.2 Technology Compatibility Kit (TCK) includes the following items:
JavaTest harness and documentation
The JavaTest harness Release Notes are provided in the JavaTest documentation directory in the JAX-WS TCK 2.2 documentation bundle.
The JavaTest harness provides three User's Guides in PDF format. The JavaTest User's Guides are also available in JavaHelp format, and can be displayed either in the JavaTest harness or in a separate viewer launched from the command line.
JAX-WS TCK Signature, API, End-to-end, WS-I Conformance, Java-to-WSDL/WSDL-to-Java Mapping and Web Services Addressing Conformance tests:
A Signature test that checks that all of the public APIs are supported/defined as specified in the JAX-WS Version 2.2 implementation that is being tested.
API tests to verify the functionality of all the public APIs under javax.xml.ws
, javax.xml.ws.handler
, javax.xml.ws.handler.soap
, javax.xml.ws.http
, javax.xml.ws.spi
, javax.xml.ws.spi.http
, javax.xml.ws.soap
, and javax.xml.ws.wsaddressing
.
WS-I Conformance Tests that test and check for conformance to the WS-I Basic Profile 1.1, Attachment Profile 1.0, and Simple Soap Binding Profile 1.0 conformance specifications.
Java-to-WSDL/WSDL-to-Java Mapping Tests that test and check for conformance to the Java-to-WSDL and WSDL-to-Java mappings.
Web Services Addressing Conformance Tests that test and check for conformance to the Web Services Addressing 1.0 - Core, Web Services Addressing 1.0 - Metadata, and Web Services Addressing 1.0 - SOAP Binding conformance specifications.
The JAX-WS TCK tests have been built and tested with the Sun GlassFish Enterprise Server v3 running on the Java(tm) Standard Edition 5 (Java SE 5), Java(tm) Standard Edition 6 (Java SE 6) and Java(tm) Standard Edition 7 (Java SE 7) platforms. If you are using a different Web server, you will need to make adjustments to the procedures outlined in this document.
The JAX-WS 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 XP. In addition, the forward slashes (/
) used in all of the examples need to be replaced with backslashes (\
) for Windows XP.
6932307 -- jaxws/wsi/w2j/document/literal/swareftest
6947724 -- jaxws2.2 install bug: config.vi/config.ri targets missing dependency and password template file
6948858 -- tck6/src/com/sun/ts/tests/jaxws/wsa/j2w/document/literal/epr/Client.java
6957526 -- src/com/sun/ts/tests/jaxws/wsa/w2j/document/literal/action
6939015 -- JAXWS TCK6 test suite refers to schema documents on internet
6952150 -- 2 or more successive builds without a clean yields incorrect ear files in JAXWS
6953119 -- com/sun/ts/tests/jaxws/wsa/j2w/document/literal/addressingfeature
6960142 -- jaxws class missing default constructor
6960327 -- jaxws/wsa/w2j/document/literal/respectbindingfeatur/Client.java#afCltEnabledNotREQSvrNotEnabledrbfSv
6960329 -- jaxws issue with wsa:ReplyTo and wsa:To headers (they are optional) in spec
6969067 -- afCltNotEnabledSvrEnabledREQrbfSvrEnabledCltEnabledTest_from_standalone
6969068 -- com/sun/ts/tests/jaxws/wsa/w2j/document/literal/requiredfalse
6981956 -- wsdl-override values
6984212 -- Need to fix regression in AttachmentHelper.java as well as cleanup of XMLUtils.java
6984235 -- webresult2/client/Client.java#testWSDL4
6989390 -- WSA test directories with addressing Optional on Client and Server MUST NOT check for addr headers
6989674 -- jaxws/wsa/j2w/document/literal/action needs to be fixed to require addressing on Client and Server
6991272 -- Fix WSA addressingfeature tests to properly handle Optional addressing (WSA Headers MAY exist)
6995353 -- SOAPMessage.getSOAPHeader() call needs fixing to handle SOAPException case in getAction* routines
7002203 -- SOAPFaultException test cases need to check all possible fault codes, MessageAddressingHeaderRequired and MustUnderstand
7005163 -- jaxws/wsa/j2w/document/literal/action
7015787 -- jaxws/wsi/w2j/document/literal/swareftest
7018028 -- Adjust tests to check for WebServiceException or SOAPFaultException
7022516 -- document/literal/anonymous/Client.java#testNonAnonymousResponsesAssertion
7022586 -- jaxws/ee/w2j/document/literal/onewayhandlertest
7027102 -- jaxws/api/javax_xml_ws/Provider/invokeTest5 & invokeTest7
7028100 -- Need to add RI and VI properties for http.server.supports.endpoint.publish
7028947 -- Fix to logic error in javax_xml_ws/Endpoint test
7037082 -- ClassCastException in remote agent during execution of 2 api/javax_xml/ws/wsi/w2j/rpc/literal tests
7038100 -- The method getHeaders in SOAPHandler
12875293 -- SCHEMA NAMING IN JWS TESTS
13424068 -- FIX HANDLER TESTS TO CHECK FOR INSTANCEOF JAVAX.XML.WS.SOAP.SOAPFAULTEXCEPTION
Added support for Java SE 7 based signatures.
There are a few JAX-WS tests that reference schemas over the internet and this caused build issues when attempting the rebuildable portion of JAX-WS 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 jax-ws catalog to resolve the URI's locally. A jax-ws 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 RI 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.
javax.xml.ws.Endpoint
publishing API's
The following properties, which are used by the Endpoint API tests in the
jaxws/api/javax_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 Java EE 6 RI server supports endpoint publishing.
If your server supports endpoint publishing (supports the use of
javax.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
javax.xml.ws.Endpoint.publish()
methods), set the property value to
"false". In a managed environment, such as the Java EE 6 Reference 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 Java EE 6 RI 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 Java EE 6 RI
supports endpoint publishing.
Refer to the JAX-WS TCK 2.2 User's Guide, available in the JAX-WS TCK 2.2 documentation bundle, for complete instructions on installing, setting up, and running the JAX-WS TCK.
Follow the steps below to configure Apache Tomcat 5 for JAX-WS TCK 2.2
<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>
Follow the steps below to configure Apache Tomcat 6 for JAX-WS TCK 2.2
<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 © 2011, Oracle and/or its affiliates. All rights reserved. Use is subject to license terms.