I have a problem with the way that the generated proxy handles the information when trying to return information from an emulated webservice. When trying to consume the emulated service, the method result is always null, but for other (simple) types it works (ie with string). The problem is that there is no way to debug the Invoke method in Visual Studio and so I can't see what is happening. It should work! Below is the returned xml info from the (emulated) webservice; inspected with a proxy inspector: <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http:// schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <getAllServiceConfigurationsResponse xmlns="http://nxp.com/ ACSTopi.Services.wsdl"> <getAllServiceConfigurationsResult> <BOM_Infrastructure_ESB_ISOESBRuntimeConfiguration type="ACSTopi.API.Business.BOM.Infrastructure.ESB.ISOESBRuntimeConfiguration" assembly="ACSTopi.API.Business.BOM" instance- id="b39322e1-79e6-4b2d-82e1-77a798b18ae9" object-id="88"> <Serialized> ...xml info goes here </Serialized> </BOM_Infrastructure_ESB_ISOESBRuntimeConfiguration> </getAllServiceConfigurationsResult> </getAllServiceConfigurationsResponse> </soap:Body> </soap:Envelope> Worth noting: The proxy knows the structure of the objects (BOM_Infrastructure_ESB_ISOESBRuntimeConfiguration) and generates the correct proxy objects. The overall communication runs, it's just the result returned is null. Does anybody know what is happening, or can suggest a solution. Christian
A null return usually means a namespace mismatch. The server is sending data in a different XML namespace than expected by the client. -- John Saunders | MVP - Connected System Developer wrote in message news:ada983ef-8637-4987-9084-dd13cb105496@m73g2000hsh.googlegroups.com... > I have a problem with the way that the generated proxy handles the > information when trying to return information from an emulated > webservice. > > When trying to consume the emulated service, the method result is > always null, but for other (simple) types it works (ie with string). > > The problem is that there is no way to debug the Invoke method in > Visual Studio and so I can't see what is happening. It should work! > > > Below is the returned xml info from the (emulated) webservice; > inspected with a proxy inspector: > > > <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http:// > schemas.xmlsoap.org/soap/envelope/"> > <soap:Body> > <getAllServiceConfigurationsResponse xmlns="http://nxp.com/ > ACSTopi.Services.wsdl"> > <getAllServiceConfigurationsResult> > <BOM_Infrastructure_ESB_ISOESBRuntimeConfiguration > type="ACSTopi.API.Business.BOM.Infrastructure.ESB.ISOESBRuntimeConfiguration" > assembly="ACSTopi.API.Business.BOM" instance- > id="b39322e1-79e6-4b2d-82e1-77a798b18ae9" object-id="88"> > <Serialized> > ...xml info goes here > </Serialized> > </BOM_Infrastructure_ESB_ISOESBRuntimeConfiguration> > </getAllServiceConfigurationsResult> > </getAllServiceConfigurationsResponse> > </soap:Body> > </soap:Envelope> > > Worth noting: The proxy knows the structure of the objects > (BOM_Infrastructure_ESB_ISOESBRuntimeConfiguration) and generates the > correct proxy objects. > > The overall communication runs, it's just the result returned is null. > > > Does anybody know what is happening, or can suggest a solution. > > Christian
