Setting the level of WS-I compliance
The web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, 1.2, 2.0, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), the WS-I Attachments Profile 1.0 (WS-I AP), and the WS-I Basic Security Profile 1.0 (WS-I BSP). You can choose to make your web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols are not WS-I compliant.
About this task
For more information on WS-I, refer to their web site: http://www.ws-i.org/. This site contains resources such as an overview of web services interoperability, usage scenarios, and specifications.
- WS-I AP 1.0 (WS-I Attachments Profile 1.0)
- Supports interoperable SOAP messages with attachments-based web services.
- WS-I BP 1.1 + SSBP 1.0 (WS-I Basic Profile and WS-I Simple SOAP Binding Profile)
- This includes the basic profile and requirements related to the serialization of an envelope and its representation in a SOAP message.
- WS-I BP 1.2 (WS-I Basic Profile)
- The WS-I Basic Profile 1.2 builds on Basic Profile 1.1 by incorporating Basic Profile 1.1 errata and requirements from Simple SOAP Binding Profile 1.0, and adding support for WS-Addressing and MTOM.
- WS-I BP 2.0 (WS-I Basic Profile)
- The WS-I Basic Profile 2.0 consists of a set of non-proprietary web services specifications, along with clarifications, refinements, interpretations and amplifications of those specifications which promote interoperability.
- WS-I BSP 1.0 (WS-I Basic Security Profile)
- The Basic Security Profile 1.0 provides guidance on the use of WS-Security and the REL, Kerberos, SAML, UserName and X.509 security token formats.
Depending on the type of web service being created, you may or may not want your web service to comply with the WS-I profiles. The default level of compliance is to generate a warning if a non WS-I SSBP complaint web service option is selected and to ignore any non WS-I AP compliant selections. You can set the level of WS-I compliance at the workspace or project level. The web services wizards, the WebSphere® run-time environments, the WSDL editor, and other web services tools provided support and encourage the development of WS-I compliance services.
For each profile you can select from three levels of compliance with WS-I specifications:
- Require WS-I compliance - this level prevents you from creating a non-compliant web service.
- Suggest WS-I compliance - this level allows you to create a non-compliant web service, but provides a visible warning stating how the service is non-compliant.
- Ignore WS-I compliance - this level allows you to create a non-compliant web service and does not notify you of non-compliance.
You can set the level of WS-I compliance at the workspace level, or at the project level.
Set the level of WS-I compliance for the workspace
About this task
To set the level of WS-I compliance for the workspace:
Procedure
- From the Window menu, select Preferences.
- Select from the component tree.
- Expand Profile Compliance and select the profiles with which you want your web services to be compliant. Select the level of compliance you want from the drop-down lists.
- Click Apply, then click OK.
Set the level of WS-I compliance for a project
About this task
To set the level of WS-I compliance for a project:
Procedure
- In the Project Navigator, right-click and select Properties.
- Select Service Policies from the component tree.
- Select the check box to enable project-specific settings.
- Expand Profile Compliance and select the profiles with which you want your web services to be compliant. Select the level of compliance you want from the drop-down lists.
- Click Apply, then click OK.