Mr. Narasimman,

Hello...  Thanks for the response.  I am not positive I understand what you
mean by the "proxy".  I am not using a client proxy that would be created by
something like wsdl.exe.  I simply have a client application that has added a
web reference using the Add Reference features of DevStudion 2005.  It is
this processes that has imported into my application the namespace org.xTango.

The sample code below is what I use behind a simple Button Event.        

// A simple test method to see if my Internet Appliance can authenticate.  
// This method abstracts the details from the UI.
public string HandleAuthEvent( string userID, string password )
{
  // Create an instance of the web service.  
  // The web.config defines the target URL for the web service.
  // Currently that is
  // http://xTango.org:8008/xTangoWebServices/xTangoWebServices.asmx
  // Don't let the extension of ASMX confuse you the reader.  We use the
  // MS standard URL extension to make this architecture more familuar to
  // OEM vendors/partners.  The Web Service is implemented on an Embedded
  // system running Tiny OS and a ported version of the GoAhead embedded
  // web server for an AtMega RISC based system.
  org.xtango.xTangoServices x = new org.xtango.xTangoServices();

  // Execute the web service on the appliance
  string xResp = x.AuthenticateUser(userID, password);
 
  // If NULL something failed that was not associated with a network error.
     
  if ( xResp == null )
  {
     xResp = "Web Service response was NULL.  Bad news!!";      
  }
  else
  {
     // Cool.  We got something back, report the response to the caller.
     // In the real working world this response would be something usfull,
     // at this point it is simply a string with the value of True or False.
     xResp = string.Format("WebRequest returned {0}", xResp );
  }
  return xResp;
}

To provide the XML that I linked in the original message I used the Trace
Utility that is part of the Soap Toolkit, a very nice tool by the way.

So...  The Web Method AuthenticateUser is indeed returning a response and
the response is encapsulated within the SOAP Envelope as follows:

http://www.kcrismon.com/phaseivengr/xTango/requestSamples/authenticateuser_2.xml

So...  I don't think I have a Client Proxy such as is created with WSDL.EXE
but if that is what I need I most certainly will create one and use that
within my application.

Is that what you would suggest?

BTW: I imlemented a simple brain dead version of this web service using the
DevStudio 2005 C# Web Service project and my application will indeed see real
data but using the Trace Utility as above my response XML from my Embedded
Web Appliance application is returning what appears to be the same exact XML
as what the brain dead Web Service is returning.  Some of the HTTP headers
are different but as I understand it the Content-Type: text/xml;
charset=utf-8 is the only header that really can make a difference.  I may of
course be wrong and please tell me what HTTP headers are important as part of
the response.  My embedded web server can certainly handle what ever headers
are required.

I am at a loss and will appreciate any help you may be able to provide.

If you want more details than this forum can provide please contact me at
krc4531@hotmail.com

Hope all is well with you and hope to hear from you soon.