Is Java source roundtripping (java->xsd->java) a requirement ?

This is an issue for a JAXRPC service client brought up in the JAXRPC
2.0 F2F.

The following text (reproduced here to avoid document chasing)
provides the background for this issue and and is taken from the
second bullet item in Section 9.1,�Requirements� in JAXRPC 1.1
specification:

[https://jsr222.dev.java.net/files/documents/919/2643/jaxrpc-1_1-fr-spec.pdf](https://jsr222.dev.java.net/files/documents/919/2643/jaxrpc-1_1-fr-spec.pdf)

A service client environment should be capable of importing a WSDL
document and generating a Java based client side representation for a
service described in this document. A client side representation
includes classes Requirements generated based on the mapping of
the WSDL definitions to the corresponding Java representation.

ISSUE: [Issue is from JAXRPC 2.0 F2F March 11,12 F2F]. It was noted at
the JAXRPC 2.0 F2F that the classes generated from a WSDL document on
a JAXRPC service client should be similar not necessarily identical to
the JAXRPC service classes from which the WSDL document was generated
on the server. The example discussed was that Date can be mapped to
xsd:date in the WSDL document generated when a JAXRPC service is
exported. But xsd:date may be mapped to Calendar in the generated
classes on the JAXRPC service client. This is a JAXB 2.0 issue since
JAXB 2.0 specifies the mapping rules used in the generation of the
section.

While roundtripping may be desirable, since JAXRPC service client’s view is the
WSDL document - not the JAXRPC service classes - a requirement for rountripping
is not totally clear. JAXB 2.0 can assist in the roundtripping by generating schema
annotations on the XML schema constructs generated in the
section.

NOTE: Roundtripping of source for Schema -> Java -> Schema case is not
a requirement.
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[2.0 draft]