SOAP Extension Problem

[Dejan]

I was trying, for the first time, to create a (fairly simple) SOAP
extension for some of my web services. They were to be called from the
WindowsForms host application.
Following error message occured:

Client found response content type of '', but expected 'text/xml'.

Calling this web service from the browser (as recommended) produced
little more explanation:

Exception Details: System.InvalidOperationException: Request format is
unrecognized.

Stack Trace:

[InvalidOperationException: Request format is unrecognized.]
System.Web.Services.Protocols.WebServiceHandlerFac tory.CoreGetHandler(Type
type, HttpContext context, HttpRequest request, HttpResponse response)
+388
System.Web.Services.Protocols.WebServiceHandlerFac tory.GetHandler(HttpContext
context, String verb, String url, String filePath) +94
System.Web.HttpApplication.MapHttpHandler(HttpCont ext context,
String requestType, String path, String pathTranslated, Boolean
useAppConfig) +699
System.Web.MapHandlerExecutionStep.System.Web.Http Application+IExecutionStep.Execute()
+95
System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean&
completedSynchronously) +173

This explanation left me unclear if this was the case of malformed XML
or (somehow) missing content type?

Initial implementation was connected to the service by using
(SoapExtensionAttribute inherited) attribute. I tried with the
<soapExtensionTypes> entry in the web.config, with no result at all.

Next step for me was to go back and try an official MS example (from
the Developer Studio help files) - simple request/response service
log. It resulted with exactly the same set of error messages.

Following that I commented out all the code in the overriden
ProcessMessage - voiding all extension functionality - same thing
again. It seems that this problem has nothing to do with the web
service code itself or with the SoapExtension inherited class code. Am
I missing some additional configuration parameters?

This kind (and very similar kind) of problems were raised several
times on this forum by now, but nobody gave any reasonable answer yet
to it.

Everything works under Windows XP (tested on two different machines),
IIS 5.1.

At this stage, I am starting to run out of ideas. Any comment is
appreciated.
Regards,

Dejan Petrovic

[John Jenkins]

I have seen this a couple of times and never fully got to the bottom of it.
When using config settings are you sure you set them correctly? If nothing
is return from your service then the config settings are most likely not set
correctly.

"Dejan" <pe*******@roymorgan.com> wrote in message
news:7e**************************@posting.google.c om...

I was trying, for the first time, to create a (fairly simple) SOAP
extension for some of my web services. They were to be called from the
WindowsForms host application.
Following error message occured:

Client found response content type of '', but expected 'text/xml'.

Calling this web service from the browser (as recommended) produced
little more explanation:

Exception Details: System.InvalidOperationException: Request format is
unrecognized.

Stack Trace:

[InvalidOperationException: Request format is unrecognized.]
System.Web.Services.Protocols.WebServiceHandlerFac tory.CoreGetHandler(Type type, HttpContext context, HttpRequest request, HttpResponse response)
+388
System.Web.Services.Protocols.WebServiceHandlerFac tory.GetHandler(HttpContex
t context, String verb, String url, String filePath) +94
System.Web.HttpApplication.MapHttpHandler(HttpCont ext context,
String requestType, String path, String pathTranslated, Boolean
useAppConfig) +699
System.Web.MapHandlerExecutionStep.System.Web.Http Application+IExecutionStep
..Execute() +95
System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean&
completedSynchronously) +173

This explanation left me unclear if this was the case of malformed XML
or (somehow) missing content type?

Initial implementation was connected to the service by using
(SoapExtensionAttribute inherited) attribute. I tried with the
<soapExtensionTypes> entry in the web.config, with no result at all.

Next step for me was to go back and try an official MS example (from
the Developer Studio help files) - simple request/response service
log. It resulted with exactly the same set of error messages.

Following that I commented out all the code in the overriden
ProcessMessage - voiding all extension functionality - same thing
again. It seems that this problem has nothing to do with the web
service code itself or with the SoapExtension inherited class code. Am
I missing some additional configuration parameters?

This kind (and very similar kind) of problems were raised several
times on this forum by now, but nobody gave any reasonable answer yet
to it.

Everything works under Windows XP (tested on two different machines),
IIS 5.1.

At this stage, I am starting to run out of ideas. Any comment is
appreciated.
Regards,

Dejan Petrovic

[Elena Kharitidi]

Web Services Framework requires valid ContentType to be able to process a
SOAP message. In your case the ContentType is empty.
This could happens if
1. the SoapExtension explicitly sets the SoapMessage.ContentType to null
(or empty string)
2. the SoapExtension modifies the message stream in a way that it looks
empty, the most common case is that after the stream manipulation its
position is not re-set to the beginning of the stream:

case SoapMessageStage.AfterSerialize:
// need to set the position at the begginning of the stream
to be able to process the stream data
newStream.Position = 0;
GenerateNewStreamData(newStream, oldStream);
break;

case SoapMessageStage.BeforeDeserialize:
GenerateNewStreamData(oldStream, newStream);
// have to reset the position to 0, so the stream could be
processed by other extensions or the WS Framework
newStream.Position = 0;
break;

[Dejan]

You were right, problem was in the stream re-wind. This was a simple
case of doing it in the wrong place, in the AfterSerialize stage.
Thank you very much for your help.
el****@online.microsoft.com (Elena Kharitidi) wrote in message news:<C#**************@cpmsftngxa10.phx.gbl>...

Web Services Framework requires valid ContentType to be able to process a
SOAP message. In your case the ContentType is empty.
This could happens if
1. the SoapExtension explicitly sets the SoapMessage.ContentType to null
(or empty string)
2. the SoapExtension modifies the message stream in a way that it looks
empty, the most common case is that after the stream manipulation its
position is not re-set to the beginning of the stream:

case SoapMessageStage.AfterSerialize:
// need to set the position at the begginning of the stream
to be able to process the stream data
newStream.Position = 0;
GenerateNewStreamData(newStream, oldStream);
break;

case SoapMessageStage.BeforeDeserialize:
GenerateNewStreamData(oldStream, newStream);
// have to reset the position to 0, so the stream could be
processed by other extensions or the WS Framework
newStream.Position = 0;
break;
--