![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#31
| |||
| |||
|
|
I do not believe a requirement (in my case a post code/test requirement) to capture Soap traffic is asking for all that much. I don't think asking for a simple method that gets invoked while receiving and sending what is the actual message sent up and down the line is an over the top request. It apparently isn't there (except maybe as 3rd party add-on). |
|
I have reviewed samples on web service side and client side, mostly for pre MSVS 2005 where it seems a lot has changed. Apparently the now depreciated Soap SDK worked. It has been superceded by WSE 1, WSE1.1, WSE2, and WSE3. |
|
These don't seem to work. I appreciate digging into the bowels can be hard/difficult. It was easier in ASP days. Now it is easier to code just the work you want without coding so much housekeeping. Fine. But it shouldn't be that complex either. Enter WSE. Previously it was suggested I look at WSE. I found WSE v3 and it loaded fine (earlier versions are not correct for my configuration). I configured it, used it to update my client sde test aspx page's web.config, my code matches the sample code, and I believe I've done all configuration tasks documented. The WSE Soap Tracing isn't working. Searches show that others have hit the same wall I have. It would appear MS provided a tool to capture Soap messages cleanly and somewhat easily, yet it doesn't work, and doesn't say that it failed or even tried. So the tool is not working or it use isn't fully documented. I'm hoping someone can resolve my client side ASPX WSE3 Framework v2 .Net 2005 issue that seems to predominently involve changes to web.config. |
#32
| |||
| |||
|
#33
| |||
| |||
|
#34
| |||
| |||
|
#35
| |||
| |||
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |