On 11/8/2021 5:03 PM, Michael Osipov wrote:
Am 2021-11-08 um 16:56 schrieb Oleg Kalnichevski:
...
I need to setup a small project next week. Give me a bit of time.
The above won't work because DataHandler is javax.activation.DataHandler
used with SOAP MTOM directly in the generated clients. I see no way to
return that input stream with a closure because it contrdicts the
closure concept.
I don't know how familiar you are with JAX-WS and MTOM, but those
DataHandlers are core concepts with are passed around with a readable
source either as input or output.
See also
https://docs.oracle.com/middleware/1212/wls/WSGET/jax-ws-mtom.htm#WSGET3485.
As of now, I am afraid that a closure will not be able to cover all
possible usecases.
Michael
I must recant my previous statement. Not everything can be turned into a
closure without some (sometimes major) refactoring, and some APIs are
just given and cannot be refactored.
Still I want to put more emphasis on the usage of
HttpClientResponseHandler going forward and steer users toward using it
as closures in their application code. Starting with our sample code and
the migration guide.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
