+

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. WAS provides an extension to the Web Services for Java EE 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.

We can learn about the CustomBinder API in the topic CustomBinder interface. The topic Custom data binders includes general information about custom binders and the topic Custom binding providers reviews how they are packaged for development.

This usage pattern reviews how to deploy the provider package to the 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 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 concepts


Custom data binders for JAX-RPC applications
Custom binding providers for JAX-RPC applications

 

Related tasks


Manage shared libraries

 

Related


CustomBinder interface for JAX-RPC applications
Java virtual machine settings
Additional Application Programming Interfaces (APIs)
Web services specifications and APIs