1

Topic: WSDL wrong SoapAction

All greetings! Is WSDL from indirect service Comprises such section <wsdl:operation name = "SecurityAuthenticate"> <soap:operation soapAction = "http://webservices.alienDomain.com/1ASI … LQ_06_1_1A"/> This Action is correct But thus in  a class it turns out [OperationContract (Action = "http://xml.alienDomain.com/AlienDomainW … ateRequest", Property of attribute gets to title SoapAction and request does not work Why so happens and how to solve this situation? Thanks... To Substitute Action dynamic it would not be desirable, methods there it is a lot of Hands to correct  classes too

2

Re: WSDL wrong SoapAction

Hello, mDmitriy, you wrote: D> All greetings! D> why so happens and how to solve this situation? Check up I now, unfortunately, I can not (simply there is no time), and earlier such intricate WSDL to me did not come across, but, probably, standard WSDL the parcer does not calculate for a similar construction (though it of strange, other method explicitly to specify Action like it is not provided) and simply ignores soap:operation, and name Action forms the standard method - taking  service, adding an operation name + Request in the end (though with the last part a question - judging by it https://stackoverflow.com/questions/647 … eplyaction - should not be added in the end of anything). I suspect that editing methods: - on the move corrects WSDL - slightly to correct the generator (there there are some variants). Since straight off I can not advise  an operating variant I will ask for you: - Can send to (lay out) the minimum played back example WSDL (it is possible and c WSDL if there there is nothing closed, only then at once prompt on what to look - long not to search)? - As you generate a client part (in studio, through svcutil...) and whether can use for example  the generator?

3

Re: WSDL wrong SoapAction

Hello, Michael Romanov, you wrote: > - on the move corrects WSDL it does not approach > - slightly to correct the generator (there there are some variants). Here it is interesting, and how? I with pleasure would remove from the generated classes a heap of any hogwash > - can send (to lay out) the minimum played back example WSDL (it is possible and c WSDL if there there is nothing closed, only then at once prompt on what to look - long not to search)? I can send everything, but only to you personally if tell  it is the confidential information, alas > - as you generate a client part (in studio, through svcutil...) and whether can use for example  the generator? I generate through studio how to connect to it the generator or to adjust available - I do not know basically the generator for manual generation - too the decision not so often it  like even can such be collected from  classes, but too I do not know as

4

Re: WSDL wrong SoapAction

5

Re: WSDL wrong SoapAction

Hello, Michael Romanov, you wrote: > I above described about process, further under the link like it should be more or less clear, but just in case I will put the example of Thanks big, I will look

6

Re: WSDL wrong SoapAction

7

Re: WSDL wrong SoapAction

Hello, Michael Romanov, you wrote: > I viewed the files sent by you and found the problem reason, but yet I do not know as better to solve - something can colleagues prompt. > in general an essence that in sent wsdl some operations have identical names. Many thanks though are clear now, in what side to dig and how to dig - I will think thanks

8

Re: WSDL wrong SoapAction

9

Re: WSDL wrong SoapAction

And one more example I will result... As it appeared, with loading of meta data from file system all not so is simple and obvious, as at downloading is immediate from the server... Therefore, if you do a variant with own utility to you can it is useful the following fragment: var metadataSet = new MetadataSet ();//Read wsdl's foreach (var file in Directory. EnumerateFiles (dir, "*.wsdl")) {var serviceDescription = System.Web.Services.Description.ServiceDescription.Read (file); var wsdlSection = MetadataSection.CreateFromServiceDescription (serviceDescription); metadataSet. MetadataSections. Add (wsdlSection);}//Read schemas foreach (var file in Directory. EnumerateFiles (dir, "*.xsd")) {var xsdSection = MetadataSection. CreateFromSchema (XmlSchema. Read (new FileStream (file, FileMode. Open), null)); metadataSet. MetadataSections. Add (xsdSection);} //Create importer var wsdlImporter = new WsdlImporter (metadataSet);//Add extension (optional) wsdlImporter. WsdlImportExtensions. Add (new ImportTraicer ());//Import endpoints (it's important! In other variants (e.g. ImportAllContracts ()) bindings will be skipped) var contracts = wsdlImporter. ImportAllEndpoints ();//Check importing errors foreach (var error in wsdlImporter. Errors) {Console. WriteLine (error. Message);}

10

Re: WSDL wrong SoapAction

Hello, Michael Romanov, you wrote: > And one more example I will result... Thanks