Community
Participate
Working Groups
I'm using Web service wizards to create a Web service client, with the monitor service checkbox checked on the first page. After wizard finishes no TCP/IP monitor is created. It turns out this only happens if my wsdl has a soap12 endpoint. If endpoint is soap11, it works.
The soap12 endpoint is bypassed in the code because the WTP does not recognize the ExtensibilityElement that represents the endpoint. In fact, WTP does not support soap12 endpoints, but some of our adopter products do and their wsdl parser passes the soap12 endpoint to the monitor setup code which does not know how to read it. To fix this, we need to let the adopter code read the enpoint for us, i.e. we need to expose an extension-point for this.
Created attachment 107617 [details] patch Also taken this opportunity to merge the jst and wst versions of the GetMonitorCommand, so we don't have to continue duo maintanance on these files (they are almost identical).
Patch reviewed and committed to R3_0_maintenance. It has been released to WTP 3.0.1 as v200807162242. Andrew, please add documentation to the exsd file defining the extension point.
Function is verified in maintenance build. Re-opening for documentation.
Created attachment 108761 [details] Documentation
Documentation released to R3_0_maintenance and HEAD as v200807310127.
Closing
