Skip to content

Operation map

This page reconciles the one operation PDFService exposes against what repository source actually invokes end-to-end.

Operation map

No operation declared by PDFService is called from repository source: nothing in this repository constructs PdfServiceProxy or the generated PDFServiceClient, so there is no active, end-to-end call site to record in this table*. See Uncalled operations below, and the important caveat that follows it, for the one nuance this finding carries.

Uncalled operations

Operation SOAP action Input message Reason not called
LoadCache http://tempuri.org/IPDFService/LoadCache PDFCacheArgs args No call site found in repository source

Important caveat: PdfServiceProxy.GetImage does contain its own internal call to LoadCache (Services/SAIF.Services.Web.Proxies/PDFServiceProxy.cs:42), documented for completeness in Client reference, but no repository source constructs or calls PdfServiceProxy itself, so that call site is never reached end-to-end by any code path in this repository today (see Tech debt).

Coverage

Check Count Reconciles
Operations declared by the proxy 1 —
Operations called from source 0 Rows in "Operation map"
Operations present but not called 1 Rows in "Uncalled operations"
Called + not called 1 Equals operations declared by the proxy
Every called row resolves or is †-marked Not applicable — no operations are called from repository source —
Every called row has a section in Client reference Not applicable — no operations are called from repository source —

Note: Statements marked with † are derived from dependency library documentation via the Legends CLI. Statements marked with * were inferred from code structure or contextual evidence. Statements marked with ** could not be confirmed; treat as unknown until verified.

Sources

  • Services/SAIF.Services.Web.Proxies/PDFServiceProxy.cs
  • Services/SAIF.Services.Web.Proxies/Service References/PDFService/PDFService.wsdl