Seconals,
I think that we have poked our heads out, eyes blinking in the
bright workaday sun.
The reason why the final round trip wasn't connecting, I'm pretty
sure, is that the filter uses a (buffered) ByteArrayOutputStream
from which it takes the data (as a byte array).
This works fine with posts & gets followed by dispatches.
However, when Atif reconstructs the service response on the fly he
injects this into the response as a string with a print method.
Hence the filter sees nothing.
This only happens on the response stage and when a consumer
exception is created on the fly. The same "empty" byte array
object is seen in both cases.
The easiest solution is for Atif to convert the response into a byte
stream.
Sorted.
Regards,
Brian
ps I'm glad that this has come to me so early. I had said to Atif
that I would not leave the office until I had spotted the critter. I can
now mark a 46 page essay that's lying on my desk...
Or I could go home for a large, stone-cold dry martini...
..............nnneeewowww!!
|
