WS-I refers to Web service interoperability; this includes interoperability across platforms, operating systems, and programming languages.
The WS-I organization sets out standards collected in documents called Profiles that define the requirements needed to make a Web service interoperable. The Rational Developer products validate Web services against the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP) and the WS-I Attachments Profile 1.0 (WS-I AP). For more information on WS-I, refer to their Web site: http://www.ws-i.org/
By default, the WS-I SSBP compliance level is set to Ignore. With this setting, no warning will be given if non-compliant choices are made. This compliance level is used by the Web service wizards and the WSDL validation tool. This sample generates a WS-I compliant Web service, therefore you should set the WS-I compliance level to Require.
You can change the WS-I compliance level by following the proceeding steps:
The remaining steps in this tutorial will be done in the J2EE perspective. If you are asked if you want to change to another perspective after performing a task, select No.
The EJB project will contain the business logic for the Web service as well as the WSDL file.
EJB Web services require a router project. This project contains the router servlet that acts as the endpoint for the service and will call out to the EJB. If you are using SOAP over JMS as your transport method the router project needs to be an EJB project. If you are using SOAP over HTTP as we are in this tutorial, the router project should be a Web project. The project you create must be added to the same EAR as the EJB project that will contain the enterprise bean. This project should not contain any of the business logic for your Web service.
You can create a Web project by following the proceeding steps: