roundtripping

Before I proceed, let me answer a question you might be asking: why do we care about roundtripping?

The use case in which roundtripping issues arise is when you expose an existing application as a Web service.

The latest refinements improve synchronizing model and code information when roundtripping capabilities, too.

The easiest way around the issue of Date not roundtripping is simply to avoid it.

For an introduction to the concept behind roundtripping please read the previous tip as listed in the Resources section.

This tip introduces the notion of roundtripping and begins to hint at some problems with the existing JAX-RPC mapping rules.

Having been in the roundtripping-is-dead camp for about a year, I now find myself having to confront this issue once again.

In this roundtripping, the original constructs are not necessarily preserved.

Once you understand what roundtripping is good for, subsequent tips will go into greater detail with issues.

So these roundtripping issues really only concern themselves with the server.

It begins to point out some roundtripping issues with the JAX-RPC specification.

Failure to do so will compromise roundtripping.

Stay tuned for further roundtripping tips which will go into more details.

When roundtripping a Web service, it is important to follow Java coding conventions.

Roundtripping is the process of mapping from one representation to another and back again.

Since roundtripping isn't perfect, extra work is required in addition to using the original code in your Web service EAR file.

This is the first of a series of tips on the topic of roundtripping.

This is the second of three tips on roundtripping and data integrity.