Actually, what I'm doing is very similar to the venetian blind design at http://devresource.hp.com/drc/slide_presentations/schemaWSDL/index.jsp (Figure 5). In my case, the CustomerDetails and PartList elements of QuoteRequestType are SOAPElements instead of a generated type.
Came across a random snippet while googling. Apparently this is another example of JAX-RPC 1.x 's poor error management. It doesn't support the full XML schema (in this case, the 'choice' element), yet charges forward blindly and does not report a problem.
I am experimenting with the early release of JAX-RPC 2.0 which is supposed to support the full XML schema. It looks like they put a lot of work into this release. Hopefully the error management has been improved as well.
Nope. The JAX-WS 2.0 EA is just as poorly designed, and apparently completely unusable from JBoss.