Viktor, This is good feedback; thank you for passing it along! Can you please shed some more light on your development environment so that we can best understand your requirements?
- What version of .NET are you using?
- Are you using WCF?
- Are you using any added products to orchestrate your web services consumption - ie Amberpoint or something of that nature?
- ...
Brent,
We use .NET 3.5 and Visual Studio 2008. We'd like to use WCF, but we have 2 problems with it. (WSDL is probably fine)
First of all, we have a simple solution to use old fashion Web service reference with WSE 3.0 (Web Services Extensions). Code:
using Microsoft.Web.Services3.Security.Tokens;
...
GenesisIntegrationWs
giws = new GenesisIntegrationWs();
UsernameToken usernameToken = new UsernameToken("login", "password", PasswordOption.SendHashed);
giws.RequestSoapContext.Security.Tokens.Add(usernameToken);
And it almost works (server returns that it can't validate user credentials, probably wrong user or password), but we traced sent messages, they have security header as required (I suppose we'll discuss this with the support).
But we'd like to use WCF and the problems are:
1. We can't find how correctly set security info (UsernameToken)
2. When trying to run test without security header (just to try), program throws an exception:
RPC Message in operation ExportGetSegmentedDataRequest has an invalid body name Export.GetSegmentedDataRequest. It must be ExportGetSegmentedDataRequest
Shortly speaking, looks like Web service proxy class, which was created by adding Service reference with Visual Studio don't like period in method or other names. Looks like it has created incorrect wrapper for class for Export.GetSegmentedDataRequest message (commenting it in code, the same exception is thrown for any else message with period in name).
Do you have samples of WCF client for your web services?