axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aleksander Slominski <>
Subject Re: streaming outbound messages (was Re: [Vote] 1 Msg or 2)
Date Wed, 07 Feb 2001 01:59:44 GMT
Doug Davis wrote:

> Just wondering... let's say we get everything streaming and let's say
> that its soooo good that the outgoing message actually starts to leave
> the last handler before the before all other handlers are done.  And
> let's say that one of the handlesr (not the last one in the chain) throws
> a fault.  At this point the transport listener (or sender depending on
> how you look at things) has already send back an rc of 200 but it
> really needs to be a non-ok rc, doesn't it?  How does this get handled?

i think that it was already mentioned on soap mailing list and i have became
very aware of this when i was implementing outbound streaming in our SoapRMI.
SOAP 1.1 does not handle this case at all. you have basically two choices:
* close connection abruptly when there is exception - on receiving side it will
be interpreted as io exception and deserializing of input arguments will fail
(that is ok) but the client will not know the reason of fault and may try
reconnect (and that is wrong)
* extend SOAP envelope specification to allow Fault element to appear anywhere
in message to signal that an exception happened during streaming...

i think that second choice is the right one but as we try in our SoapRMI to be
fully SOAP 1.1 compatible it is now implemented with first option (no
proprietary extensions...)

Aleksander Slominski, LH 316, IU,
As I look afar I see neither cherry Nor tinted leaves Just a modest hut
on the coast In the dusk of Autumn nightfall - Fujiwara no Teika (1162-1241)

View raw message