My apologies for posting to an ASP.NET group, but I'm expecting a bit
of cross-pollination with folks using/building web services, and this
group has some spot-on good folks in it...
Our project is using WSE 1.0 for its use of DIME attachments. In one
of our environments, we're getting back Soap responses in which we
see 'Object reference not set to an instance of an object.' This,
we've discovered, is not a NPE in our code: our code has executed
correctly, and in fact, in tracing the messages sent as a response
from the endpoint, the correct XML is listed.
When we receive the XML in our client, we get a server soap fault
that says
<faultstring>Server was unable to process request. -->
Object reference not set to an instance of an object.
Putting in place a custom SOAP trace extension to trace the message's
serialization, deserialization (see
http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/cpguide/html/cpconalteringsoapmessageusingsoapextensions.asp),
we're seeing that the AfterSerialize is firing multiple times on the
server side. In the first instance, we're fine, and the XML looks as
we expect. In the second instance, we're fine: looks like timestamp
info is added to the Soap header. In the 3rd instance, we're not
fine anymore.. We get the exception.
Any ideas of where I'd look to find the chain of extensions being
fired, or see which extension is causing the problem?
------------------------ Yahoo! Groups Sponsor --------------------~-->
Most low income households are not online. Help bridge the digital divide today!
http://us.click.yahoo.com/cd_AJB/QnQLAA/TtwFAA/saFolB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
