Mike,

JAX-WS seems to specify something similar to your suggestion.

Under the WSDL->Java section it says:
------------------------------------------------------------------------------

2.3.4.3 Message and Part

The asynchronous mapping supports both wrapper and non-wrapper mapping
styles, but differs in how it
maps out and in/out parts or wrapper children:

in The part or wrapper child is mapped to a method parameter as
described in section 2.3.1.

out The part or wrapper child is mapped to a property of the response
bean (see below).

in/out The part or wrapper child is mapped to a method parameter (no
holder class) and to a property of the
response bean.

------------------------------------------------------------------------------

It goes on to describe the details of the Response bean in Sec.
2.3.4.4... akey point being that if there are multiple outputs, they
get wrapped with a response bean (which becomes visible to the
application, unlike the typically doc-lit-wrapped wrapper bean),
whereas if there is only one output it gets placed directly in the
Response.

JAX-WS doesn't seem to mention this in any Java->WSDL context, though.
  I imagine the best way to deal with that is to say that only async
Java interfaces that could have been mapped from WSDL are valid in an
async context...rather than trying to jump through hoops making sense
of any interface at all.

Scott

Reply via email to