Web Services Custom Data Binding, Part 1, How to choose a custom mapping technology for Web services

From the developerWorks archives

Nicholas Gallardo and Greg Truty

Date archived: July 17, 2017 | First published: January 25, 2006

In most scenarios, the mapping from XML schema to Java™, as defined by JAX-RPC, yields a suitable set of Java beans for handling your Web services data. However, there are cases when you may prefer an alternate mapping, or when there just isn't a well-defined mapping for your particular schema construct (xsd:choice is a common example). For these cases, IBM® WebSphere® V6 has introduced a new feature called Custom Data Binding that allows you to integrate alternate data binding technologies like JAX-B, EMF/SDO and XML beans, as well to define your own XML schema to Java mappings. This article provides an overview of the technology and how you can get started integrating it into your application.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.

Zone=SOA and web services, Middleware
ArticleTitle=Web Services Custom Data Binding, Part 1: How to choose a custom mapping technology for Web services