|
From: David G. <dg...@co...> - 2003-08-07 04:35:45
|
I've updated SoapWriterPipelineStage to return the soap response (thanks for the help, Jonathan!). I'm not sure if (or why!) anyone would depend on the prior functionality returning null, but, using the principal of 'better safe than sorry' (perhaps Dejan can include a paragraph or two about this in his new book), I've left the default behavior alone and added an attribute 'responseDoc' which must be set to true in the SoapWriter config file in order to see the new functionality. I haven't yet updated the documentation to include this new attribute, partly because I don't know where to update it, and partly because I'd like to remove it and force the SoapWriter to always return the response. If you don't need it, you can ignore it. However, because I don't have a good feel as to what impact this might cause, I thought I'd ask those older and wiser than myself (or at least older than my daughter). Shall I force the SoapWriter to always return the response? If not, then where can I document the responseDoc attribute? And why does it always seem darkest before the dawn? Thanks, David -- David Glick Transmit Consulting, Inc 619-475-4052 dg...@tr... |