I’m making this post because I’ve been unable to find a post on the web for a problem I had with a .Net web-service and a Java (AXIS) client. I wanted to send a fairly large data transfer object over SOAP and found that I got the error message below. I found very little on the web but with the help of a colleague finally worked out that it can be solved by overriding a default in the web.config for the .Net web-service, like this: <httpRuntime maxRequestLength=”131072“/>
Here’s the exception: When RoutingStyle is set to RequestElement, SoapExtensions configured via an attribute on the method cannot modify the request stream before it is read. The extension must be configured via the SoapExtensionTypes element in web.config, or the request must arrive at the server as clear text. –> Object reference not set to an instance of an object.
I’m getting the same message that you’re referenced in your exception, however I’m transferring a relatively small file. I’ve tried your web.config change and it doesn’t seem to have made a difference.
Any other thoughts/opinions?
-Doug
Comment by Doug Setzer — 2006-11-8 @ 23:10
Sorry Doug, the aim of my post here was to advertise a small victory, I wouldn’t dream of trying to offer support for the MS interop war as a whole. All I can suggest is to get googling. :(
Comment by savaged — 2006-11-9 @ 9:02
The longer that I’ve been fighting with that project, the more I realize how victorious you’ve been! .NET and axis just simply don’t play nice. I have sorted out that the exception really means, “uhhh… something went wrong in reading this SOAP envelope; it could be that the request was buggered, you’re custom input filters are crapping out or – I’m just have a pill of a day”.
I do appreciate the response, though.
Cheers.
Comment by Doug — 2006-11-19 @ 1:39
Thank you. thank you. Error message was misleading. Thanks to you and google.com for finding you.
Comment by Mrudul — 2007-01-24 @ 20:54