+

Search Tips   |   Advanced Search

Usage patterns for deploying custom data binders for JAX-RPC applications

Custom data binders are used to map XML schema types with Java objects. Custom data binders provide bindings for XML schema types that are not supported by the current Java API for XML-based Remote Call Procedure (JAX-RPC) specification. WebSphere Application Server provides an extension to the Web Services for Java EE programming model called the CustomBinder interface that implements these custom bindings for a specific XML schema type. The custom binding provider is the package for the custom data binders that is imported into the runtime.

To learn more about the CustomBinder API, see the CustomBinder interface for JAX-RPC applications information. For general information about custom binders, see the custom data binders for JAX-RPC applications information. See the custom binding providers for JAX-RPC applications information to review how custom binding providers are packaged for development.

This usage pattern reviews how to deploy the provider package to your runtime, as well as the roles involved in the custom binding process.


Roles involved in custom data binding

Four roles are involved with custom data binding. These roles that are defined by the Web Services for Java EE specification are as follows:


Common usage patterns

The custom binder provider package can be deployed in various ways to provide flexibility beyond the standard JAX-RPC mapping standards. Three primary deployment usage patterns are as follows:


Usage patterns

This section reviews deploying custom data binders using one of the three patterns:


Related:

  • Custom data binders for JAX-RPC applications
  • Custom binding providers for JAX-RPC applications
  • Manage shared libraries
  • CustomBinder interface for JAX-RPC applications
  • Java virtual machine settings
  • Additional Application Programming Interfaces (APIs)
  • Web services specifications and APIs