# Standard Web Project Properties Dialog Box: JAX-RPC Web Services

Use to preconfigure the features that are used by the `wscompile` tool to compile a JAX-RPC web service:

- If you are implementing an existing WSDL file, the `wscompile` tool will create a service endpoint interface and implementation class for your JAX-RPC web service.
- If you are creating a web service from scratch, the `wscompile` tool creates a WSDL file.

Note: If the project does not contain JAX-RPC web services, the JAX-RPC Web Services page does not exist.

Features

If you are implementing an existing WSDL file, you can check or type one or more of the following `wscompile` tool features:

Feature | Effect on Web Service
--- | ---
`datahandleronly` | Maps attachments to the DataHandler type.
`donotoverride` | No regeneration of classes that already exist on the classpath.
`donotunwrap` | Disables unwrapping of document/literal wrapper elements in WSI mode (default).
`explicitcontext` | Turns on explicit service context mapping.
`jaxbenumtype` | Maps anonymous enumeration to its base type.
`nodatabinding` | Turns off data binding for literal encoding.
`noencodedtypes` | Turns off encoding type information.
`nomultirefs` | Turns off support for multiple references.
`norpcstructures` | No generation of RPC structures (`-import` only).
`novalidation` | Turns off full validation of imported WSDL documents.
`resolveidref` | Resolve `xsd:IDREF`.
`searchschema` | Searches schema aggressively for types.
`serializeinterfaces` | Turns on direct serialization of interface types.
`strict` | Generates code strictly compliant with the JAX-RPC Specification.
`unwrap` | Enables unwrapping of `document/literal` wrapper elements in WSI mode.
`wsi` | Checks for compliance with the WSI-Basic Profile, which is a specification for improved interoperability. For example, the WS-I Basic Profile prohibits the use of `rpc/encoded`. Therefore, if you set the `wsi` feature, a warning will be generated when you build a web service that uses a WSDL file that uses `rpc/encoded`.

If you want to compile a document-style web service, you can check or type one or more of the following `wscompile` tool features:

Feature | Description | Required?
--- | --- | ---
`documentliteral` | Use this to specify in the WSDL file that the web service is of style "document". By default, all web services that do not have at least one operation are compiled as document-style web services. | Yes
`donotoverride` | No regeneration of classes that already exist on the classpath. | No
`rpcliteral` | Not applicable. | -
`strict` | Generates code strictly compliant with the JAX-RPC Specification. | No
`useonewayoperations` | Not applicable. | -

If you want to compile a RPC-style web service, you can check or type one or more of the following wscompile tool features:

Feature | Description | Required?
--- | --- | ---
`documentliteral` | Not applicable. | -
`donotoverride` | No regeneration of classes that already exist on the classpath. | No
`noencodedtypes` | Encoding rules are defined in the XML Schema. By default, RPC-style web services have their encoding rules defined in the SOAP 1.1 Specification. With this feature, it uses the XML Schema defined in the types element for encoding purposes instead. | No
`nomultirefs` | Turns off support for multiple references. | No
`rpcliteral` | Use this to specify in the WSDL file that the web service is of style "rpc". By default, all web services that have at least one operation are compiled as RPC-style web services. | Yes
`serializeinterfaces` | Turns on direct serialization of interface types. | No
`strict` | Generates code strictly compliant with the JAX-RPC Specification. | No
`useonewayoperations` | Methods with void return types are mapped as one-way operations. | No

Related Topics

Developing Applications with NetBeans IDE,

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.