|
|
|
|
.NET WebService Studio .NET Webservice Studio Submitted By: Microsoft Corporation
Introduction: .NET Webservice Studio is a tool to invoke webmethods interactively. The user can provide a WSDL endpoint. On clicking button Get the tool fetches the WSDL, generates .NET proxy from the WSDL and displays the list of methods available. The user can choose any method and provide the required input parameters. On clicking Invoke the SOAP request is sent to the server and the response is parsed to display the return value.
This tool is meant for webservice implementers to test their webservices without having to write the client code. This could also be used to access other webservices whose WSDL endpoint is known.
The PanelsWSDL EndPoint: The user can either type a remote URI for the WSDL or browse the file-system for a local WSDL file. Upon filling the editbox the user can click the Get button to get the WSDL and generate the proxy.
Invoke Tab: This tab lists the methods available in the webservice at the given WSDL endpoint. The user can choose the webmethod to invoke. Before invoking the user can provide the input parameter and the required headers. The input values should be provided in the property grid at top right.
WebMethods support a rich-set of input types varying from a simple primitive type to a complex nested structure or a dataset. The tool provides an intuitive UI to input various types. The tool uses WinForm control property grid extensively for this. This allows the user to plug in custom DataEditors and Type converters. (Please see PropertyGrid help for more info on DataEditors and TypeConverters). To plug in custom DataEditors, the user should go to edit|options and include the type for which the new DataEditor is meant for and the DataEditorType along with the assembly that defines the editor.
Request/Response Tab: This tab shows the SOAP message that was sent as request and the response messages. This tab provides a way to play with the raw SOAP messages. User could modify the request and resend the request. The user can also modify various HTTP request properties.
WSDL Tab: The WSDL tab has the list of WSDLs generated for the given WSDL end point and the .NET proxy that can be used to consume the webservice. Various WSDL options can be specified through Edit|Options. Some typical options are Proxy protocol such as SOAP, GET or POST; Proxy Language such as VB, CS or JS etc. (do WSDL.exe /? from the command line to view the list of options) Message Tab: These tabs display various messages including any error messages and this help text.
Menu OptionsFile | Save All File: Saves the WSDL file, the schema file and the proxy file from WSDL tab. The user can choose a directory and a base name for all the files. The WSDL files are stored with .wsdl extension, schema files with a .xsd extension and the proxy with a .cs or .vb depending on the language in which it is generated.
File | Exit: Duh
Edit | Find: Searches the current selection of the WSDL tab (i.e. WSDL, Schema or the proxy text) for the specified string
Edit | Find Next: Searches the last Find-string
Edit | Options: Shows dialog box to edit various options including WSDL settings.
Help | Help: Shows this message
Help | About: Shows the vanity box.
FAQCan I invoke web methods from WebService servers that are not implemented using .NET? Yes any webservice that provides a WSDL endpoint can be accessed.
The default URL in the generated proxy (from the Service section of the WSDL ) is not correct. How can I change it? You can change any of the properties of the proxy by selecting the root node (with the webservice name) in the tree that lists all the methods in the invoke tab.
My webservice is protected with basic-authentication. How can I provide the username-password? Goto proxy properties and provide BasicAuthUserword and BasicAuthPassword. (The password edit box is not protected. Beware!)
How about NTLM Authentication? If the current user is allowed to view the webservice then set proxy-property UserDefaultCredential to true. (Ensure the properties KeepAlive and AllowAutoRedirect are set to true)
Invoking my webmethod fails for unknown reason. The response message does not reveal anything. Is there a way to view the response header? Switch to request response tab and click the Send button. This should resend the SOAP message. The response message now should be displayed with the Response Header.
My webmethod takes a dataset as parameter. In the invoke tab property grid I am not able to add any tables to the dataset. Is there a way to do this? Unfortunately the default data editor for datasets does not allow addition of tables or columns. The workaround is to open the data-editor and load a serialized dataset or its schema. |
|
|
