WebSphere Web services preferences
The WebSphere® Web services preferences page allows you to set the following preferences used when creating or consuming WebSphere Web services.
Security
- Show only FIPS compliant algorithms:
- Select this if you only want the FIPS compliant algorithms to be shown in the Data Encryption method algorithm and Key Encryption method algorithm drop-down lists. Use this option if you expect this application to be run on a WebSphere Application Server that has set the Use the Federal Information Processing Standard (FIPS) option in the Global security panel of the WebSphere administrative console.
- Show '*' instead of letters for passwords
- By default the workbench will display an asterisk "*" rather than letters for passwords.
JAX-WS Code generation
- Top Down
- Copy WSDL into project: Select this to copy the WSDL file from which the Web service is being created into the Web service project. This is a convenient option if you plan to create the client at a later time or publish the WSDL for other users.
- Enable wrapper style: For WSDL documents that implement a document/literal wrapped pattern, a root element is declared in the XML schema and is used as an operation wrapper for a message flow. Separate wrapper element definitions exist for both the request and the response. More simply, the element whose name is the same as the operation (the wrapper element) is broken apart so that each of its content elements becomes a parameter of the generated Java™ method signature.
- Generate serializable JAXB classes: In WebSphere Application Server v7.0 and v8.0 when you enable the Java 6 facet, you can choose to generate JAXB classes which implement java.io.Serializable. Classes that do not implement this interface will not have any of their state serialized or deserialized.
- Enable MTOM support: If you select this check box the SOAP Message Transmission Optimization Mechanism will be enabled.
- Generate schema library project from XSD file: Selecting this will run the JAX-WS Schema to Java compiler to generate schema code into a schema library.
- Generate Web service deployment descriptor: For JAX-WS Web services deployment information is generated dynamically by the runtime; static deployment descriptors are no longer required. Selecting this checkbox will generate them.
- Version of JAX-WS code to be generated: When deploying to WebSphere Application Server v7.0 or later, you can generate JAX-WS 2.1 compliant code, and when using WebSphere Application Server v8.0 you can generate JAX-WS 2.2 compliant code. Previous versions of the server only support JAX-WS 2.0.
- Bottom Up
- Enable SOAP 1.2 support: You can choose between SOAP 1.1 and SOAP 1.2 bindings.
- Enable MTOM support: If you select this check box the SOAP Message Transmission Optimization Mechanism will be enabled.
- Java to WSDL mapping style: This specifies the style of Java to WSDL mapping. Style defines encoding style for messages sent to and from the Web service. Parameter style determines whether the method's parameters represent the entire message body or whether parameters are elements wrapped inside a top-level element named after the operation. The combinations are RPC, Document/Wrapped, or Document/Bare.
- Generate WSDL into the project: Select this to generate a WSDL file into the Web service project. This is a convenient option if you plan to create the client at a later time or publish the WSDL for other users.
- Generate Web service deployment descriptor: For JAX-WS Web services deployment information is generated dynamically by the runtime; static deployment descriptors are no longer required. Selecting this checkbox will generate them.
- Client
- Enable asynchronous client support: If you select to enable an asynchronous client, for each method in the Web service two additional methods will be created. These are polling and callback methods which allow the client to function asynchronously.
- Generate serializable JAXB classes: In WebSphere Application Server v7.0 and v8.0 when you enable the Java 6 facet, you can choose to generate JAXB classes which implement java.io.Serializable. Classes that do not implement this interface will not have any of their state serialized or deserialized.
- Generate portable client: Selecting this checkbox would allow you to move your Web service client code from one machine to another or from one instance of WebSphere Application Server to another. If this option is selected, the WSDL document and all the XML Schema and other WSDL documents that it depends upon will be copied into the client project under WEB-INF/wsdl and a file:relativeURL pointing to this copy will then be injected into the JAX-WS Service class's static initialization block.
- Generate Web service deployment descriptor: For JAX-WS Web services deployment information is generated dynamically by the runtime; static deployment descriptors are no longer required. Selecting this checkbox will generate them.
- Generate ibm-webservicesclient-bnd.xml template for overriding the service's endpoint URL: When enabled, results in the generation of a WebSphere extended deployment descriptor which overrides the endpoint URL used by clients when invoking a Web service. This only takes effect when the client is using JSR-109 (that is, has a client service-ref deployment descriptor). Otherwise, the client runs in unmanaged form and ignores this setting. If you generate deployment descriptors and try to use a TCP/IP monitor, the endpoint is fixed, and the TCP/IP monitor will not see any traffic.
- Enable MTOM support: If you select this check box the SOAP Message Transmission Optimization Mechanism will be enabled.
- Version of JAX-WS code to be generated: When deploying to WebSphere Application Server v7.0 or later, you can generate JAX-WS 2.1 compliant code. Previous versions of the server only support JAX-WS 2.0.