ASP.NET Core 6.0微服务中运行时动态调用WSDL服务的问题求助

核心需求：在ASP.NET Core 6.0微服务中，从环境变量动态读取WSDL服务地址，调用SOAP服务的ConsultarSaldosCobros方法；添加服务引用的方式虽能正常工作，但无法适配多环境动态地址的场景，此前尝试的HttpClient、ChannelFactory方案未达预期。

方案一：使用HttpClient直接构造SOAP请求（轻量推荐） #

无需依赖WSDL生成的代理类，手动构造SOAP报文，完全适配动态地址需求，实现灵活且轻量。

实现步骤 #

1. 通过ASP.NET Core的IConfiguration读取环境变量中的服务地址
2. 构造符合SOAP 1.1规范的请求头与请求体
3. 发送POST请求并解析XML响应

代码示例 #

// 通过构造函数注入IConfiguration（ASP.NET Core标准注入方式）
private readonly IConfiguration _configuration;

public YourServiceClass(IConfiguration configuration)
{
    _configuration = configuration;
}

private async Task CallConsultarSaldosCobrosAsync()
{
    // 从环境变量/配置文件读取服务地址，默认值兜底
    string serviceUrl = _configuration["SoapService:Url"] ?? "http://localhost/SCTSBJAX/ServiciosVEXJx";
    string soapAction = "http://localhost:7031/ConsultarSaldosCobros/";

    // 构造完整SOAP请求体，注意命名空间与WSDL定义保持一致
    string requestBody = @"<soapenv:Envelope xmlns:soapenv=""http://schemas.xmlsoap.org/soap/envelope/"" xmlns:cce=""你的服务命名空间"">
        <soapenv:Header/>
        <soapenv:Body>
            <cce:ConsultarSaldosCobro>
                <cce:ConsultaCobroReq>
                    <sesionReq>
                        <sesionId>57301</sesionId>
                        <userId>8</userId>
                        <hashSesion>008B5AAD0643AE56C721CDF71AFE7D82A04F6C95031B650EA888FD7D512E9C95</hashSesion>
                        <codTran>1</codTran>
                        <codigoCanal>1</codigoCanal>
                    </sesionReq>
                    <servicioAdq>
                        <codigoEmpresaAdq>1</codigoEmpresaAdq>
                        <codigoAplicacionAdq>VEX</codigoAplicacionAdq>
                        <codigoServicioAdq>6</codigoServicioAdq>
                        <codigoCanalAdq>1201</codigoCanalAdq>
                        <referenciaAdquiriente>54214089</referenciaAdquiriente>
                        <fechaAdquiriente>2016-02-20T09:56:29-05:00</fechaAdquiriente>
                        <codigoComercio>0990858322001PG041</codigoComercio>
                        <codigoTerminal>123</codigoTerminal>
                    </servicioAdq>
                    <productoReq>
                        <codigoInstitucion>408</codigoInstitucion>
                        <codAplProducto>SER</codAplProducto>
                        <codigoProducto>386</codigoProducto>
                        <camposAdicionales>{""campos"":[{""codigo"":""Tipo Identificacion"",""valor"":""CEDULA"",""requerido"":""M""},{""codigo"":""Identificacion"",""valor"":""1304837162"",""requerido"":""M""}]}</camposAdicionales>
                    </productoReq>
                    <codigoInstitucionAut>406</codigoInstitucionAut>
                </cce:ConsultaCobroReq>
            </cce:ConsultarSaldosCobro>
        </soapenv:Body>
    </soapenv:Envelope>";

    // 推荐使用IHttpClientFactory复用实例，此处为简化示例直接创建HttpClient
    using HttpClient client = new HttpClient();
    client.DefaultRequestHeaders.Add("SOAPAction", soapAction);
    StringContent content = new StringContent(requestBody, Encoding.UTF8, "text/xml");

    HttpResponseMessage response = await client.PostAsync(serviceUrl, content);
    response.EnsureSuccessStatusCode();

    string responseXml = await response.Content.ReadAsStringAsync();
    // 解析响应XML，可根据需求改用XElement或XmlSerializer强类型解析
    XmlDocument doc = new XmlDocument();
    doc.LoadXml(responseXml);
    Console.WriteLine(doc.OuterXml);
}

方案二：改进ChannelFactory的使用方式 #

若偏好WCF风格的调用，可通过生成契约接口+动态地址的方式实现，解决原代码中的逻辑问题。

前置步骤：生成契约接口 #

使用svcutil.exe工具从WSDL生成契约接口（仅用于定义服务契约，不硬编码地址）：

svcutil.exe http://localhost/SCTSBJAX/ServiciosVEXJx?wsdl /language:C# /out:ServiciosVEXContract.cs

代码示例 #

private readonly IConfiguration _configuration;

public YourServiceClass(IConfiguration configuration)
{
    _configuration = configuration;
}

private async Task CallWithChannelFactoryAsync()
{
    string serviceUrl = _configuration["SoapService:Url"] ?? "http://localhost/SCTSBJAX/ServiciosVEXJx";
    BasicHttpBinding binding = new BasicHttpBinding();
    EndpointAddress endpoint = new EndpointAddress(serviceUrl);

    // 使用生成的契约接口（示例为IServiciosVEX，需替换为实际生成的接口名）
    ChannelFactory<IServiciosVEX> factory = new ChannelFactory<IServiciosVEX>(binding, endpoint);
    IServiciosVEX client = factory.CreateChannel();

    try
    {
        // 强类型构造请求参数，避免手动拼接XML的错误
        ConsultaCobroReq request = new ConsultaCobroReq
        {
            sesionReq = new SesionReq
            {
                sesionId = "57301",
                userId = "8",
                hashSesion = "008B5AAD0643AE56C721CDF71AFE7D82A04F6C95031B650EA888FD7D512E9C95",
                codTran = "1",
                codigoCanal = "1"
            },
            servicioAdq = new ServicioAdq
            {
                codigoEmpresaAdq = "1",
                codigoAplicacionAdq = "VEX",
                // 补充其他必填参数
            },
            // 补充其他请求参数
        };

        // 直接调用服务方法
        ConsultaCobroResp response = await client.ConsultarSaldosCobrosAsync(request);
        // 处理响应逻辑
    }
    finally
    {
        // 正确释放Channel资源
        if (((IClientChannel)client).State == CommunicationState.Faulted)
        {
            ((IClientChannel)client).Abort();
        }
        else
        {
            ((IClientChannel)client).Close();
        }
        factory.Close();
    }
}

原代码问题说明 #

1. 无需手动下载WSDL，ChannelFactory会自动处理契约匹配逻辑
2. 原代码中Message.CreateMessage传入StringReader的方式不符合SOAP规范，需包裹完整的SOAP Envelope
3. 未实现从环境变量动态读取地址的逻辑

关键注意事项 #

• 环境变量配置：可在appsettings.{Environment}.json中配置不同环境的服务地址，或直接设置系统环境变量，通过IConfiguration统一读取
• 命名空间匹配：请求体中的XML命名空间必须与WSDL定义完全一致，否则服务会返回错误
• 异常处理：添加网络异常、SOAP Fault等捕获逻辑，避免服务崩溃
• HttpClient复用：生产环境推荐使用IHttpClientFactory管理HttpClient实例，提升性能与稳定性

内容的提问来源于stack exchange，提问作者David Ortega