Exception Handling in WCF using Fault Contract

本文通过实例介绍如何在WCF应用程序中使用SOAP故障消息来处理服务方法中的错误,并创建一个可与客户端交互的故障合约。

Introduction

In all managed applications, processing errors are represented by Exception objects. In WCF applications, service methods communicate processing error information using SOAP fault messages. SOAP faults are message types that are included in the metadata for a service operation and, therefore, create a fault contract that clients can use to make their operation more interactive. In addition, because SOAP faults are expressed to clients in XML form, they are highly interoperable.

To be more concrete, let us start with an example:

Create an empty solution in VS2005 called "IndigoException". Add one project called "IndigoService". Next a dd a reference to System.ServiceModel and then a dd an interface.

using System;

using System.Collections.Generic;

using System.Text;

using System.ServiceModel;

using System.Runtime.Serialization;

namespace Indigo

{

    [ServiceContract()]

    public interface IService

    {

        [OperationContract]

        [FaultContract(typeof (MyFaultException))]

        string GetMessage();

    }
}

Add one more class as follows:


using
System;

using System.Text;

using System.Runtime.Serialization;

namespace Indigo

{

    [DataContract]

    public class MyFaultException

    {

        private string _reason;

 

        [DataMember]

        public string Reason

        {

            get { return _reason; }

            set { _reason = value ; }

        }

    }

}

Add one class "Service" and a reference to System.ServiceModel

using System;

using System.Collections.Generic;

using System.Text;

using System.ServiceModel;

namespace Indigo

{

    public class Service : IService

    {

        #region IService Members

         public string GetMessage()

        {

            try

            {

                int i, j, k;

                j = 1;

                 k = 0;

                i = j / k;

            }

            catch (Exception exp)

            {

                MyFaultException theFault = new MyFaultException();

                 theFault.Reason = "Some Error " + exp.Message.ToString();

                throw new FaultException<MyFaultException>(theFault);

            }

            return "No Error" ;

        }

 

        #endregion

    }

}  

Build the project.

Now add another project "Host" and add reference to "IndigoService" project and to System.ServiceModel

using System;

using System.Collections.Generic;

using System.Text;

using System.ServiceModel;

 

namespace Indigo

{

    class IndigoHost

    {

 

        internal static ServiceHost myServiceHost = null ;

        static void Main(string [] args)

        {

             StartService();

            Console .WriteLine("Service at your service" );

            Console .ReadKey();

            StopService();

        }

        internal static void StartService()

        {

            myServiceHost = new ServiceHost(typeof (Indigo.Service));

            myServiceHost.Open();

        }

 

        internal static void StopService()

        {

            //Call StopService from your shutdown logic (i.e. dispose method)

            if (myServiceHost.State != CommunicationState.Closed)

                myServiceHost.Close();

        }

    }

}

Add app.config with the following XML:

<? xml version = "1.0 " encoding = "utf-8 " ?>

< configuration >

  < system.serviceModel >

    < services >

      < service behaviorConfiguration = "MyServiceTypeBehaviors " name = "Indigo.Service ">

        < endpoint address = "Service "  binding = "wsHttpBinding " contract = "Indigo.IService " />

        < host >

          < baseAddresses >

            < add baseAddress = "http://localhost:1111/Indigo " />

          </ baseAddresses >

        </ host >

      </ service >

    </ services >

    < behaviors >

      < serviceBehaviors >

        < behavior name = "MyServiceTypeBehaviors ">

          < serviceMetadata httpGetEnabled = "true " />

          < serviceDebug includeExceptionDetailInFaults = "true " />

        </ behavior >

      </ serviceBehaviors >

    </ behaviors >

  </ system.serviceModel >
</ configuration >

Build the project. Run Host.exe from VS2005 command prompt. You should get the message at the command prompt as follows:



Add another project "IndigoClient" and add System.ServiceModel

Now add service refrence to the service URL (i.e. http://localhost:1111/Indigo )

It will create localhost.cs in service reference.

Add a class Program.cs as follows:

using System;

using System.Collections.Generic;

using System.Text;

using System.ServiceModel;

 

namespace Indigo

{

    class Program

    {

        static void Main(string [] args)

        {

            string result = "" ;

            try

            {

                IndigoClient.localhost.IService ww = new IndigoClient.localhost.ServiceClient
                ();

                result = ww.GetMessage();

            }

            catch (FaultException<IndigoClient.localhost.MyFaultException> ee)

            {

                result = "Exception: " + ee.Detail.Reason;

            }

            Console .WriteLine(result);

            Console .ReadLine();            

        }

    }

}


Add app.config with following XML


<?
xml version = "1.0 " encoding = "utf-8 " ?>

< configuration >

  < system.serviceModel >

    < bindings >

      < wsHttpBinding >

        < binding name = "WSHttpBinding_IService " closeTimeout = "00:01:00 "

            openTimeout = "00:01:00 " receiveTimeout = "00:10:00 " sendTimeout = "00:01:00 "

            bypassProxyOnLocal = "false " transactionFlow = "false " hostNameComparisonMode = "StrongWildcard "

            maxBufferPoolSize = "524288 " maxReceivedMessageSize = "65536 "

            messageEncoding = "Text " textEncoding = "utf-8 " useDefaultWebProxy = "true "

            allowCookies = "false ">

          < readerQuotas maxDepth = "32 " maxStringContentLength = "8192 " maxArrayLength = "16384 "

              maxBytesPerRead = "4096 " maxNameTableCharCount = "16384 " />

          < reliableSession ordered = "true " inactivityTimeout = "00:10:00 "

              enabled = "false " />

          < security mode = "Message ">

            < transport clientCredentialType = "Windows " proxyCredentialType = "None "

                realm = "" />

            < message clientCredentialType = "Windows " negotiateServiceCredential = "true "

                algorithmSuite = "Default " establishSecurityContext = "true " />

          </ security >

        </ binding >

      </ wsHttpBinding >

    </ bindings >

    < client >

      < endpoint address = "http://localhost:1111/Indigo/Service " binding = "wsHttpBinding "

          bindingConfiguration = "WSHttpBinding_IService " contract = "IndigoClient.localhost.IService "

          name = "WSHttpBinding_IService ">

        < identity >

          < userPrincipalName value = "name@domain.com " />

        </ identity >

      </ endpoint >

    </ client >

  </ system.serviceModel >

</ configuration >

Note: Please add your username and domain name under userPrincipalName

Now run the client project; you should get following error message:



You can now see the detailed error message returned from the service.

内容概要:本文介绍了一个基于多传感器融合的定位系统设计方案,采用GPS、里程计和电子罗盘作为定位传感器,利用扩展卡尔曼滤波(EKF)算法对多源传感器数据进行融合处理,最终输出目标的滤波后位置信息,并提供了完整的Matlab代码实现。该方法有效提升了定位精度与稳定性,尤其适用于存在单一传感器误差或信号丢失的复杂环境,如自动驾驶、移动采用GPS、里程计和电子罗盘作为定位传感器,EKF作为多传感器的融合算法,最终输出目标的滤波位置(Matlab代码实现)机器人导航等领域。文中详细阐述了各传感器的数据建模方式、状态转移与观测方程构建,以及EKF算法的具体实现步骤,具有较强的工程实践价值。; 适合人群:具备一定Matlab编程基础,熟悉传感器原理和滤波算法的高校研究生、科研人员及从事自动驾驶、机器人导航等相关领域的工程技术人员。; 使用场景及目标:①学习和掌握多传感器融合的基本理论与实现方法;②应用于移动机器人、无人车、无人机等系统的高精度定位与导航开发;③作为EKF算法在实际工程中应用的教学案例或项目参考; 阅读建议:建议读者结合Matlab代码逐行理解算法实现过程,重点关注状态预测与观测更新模块的设计逻辑,可尝试引入真实传感器数据或仿真噪声环境以验证算法鲁棒性,并进一步拓展至UKF、PF等更高级滤波算法的研究与对比。
内容概要:文章围绕智能汽车新一代传感器的发展趋势,重点阐述了BEV(鸟瞰图视角)端到端感知融合架构如何成为智能驾驶感知系统的新范式。传统后融合与前融合方案因信息丢失或算力需求过高难以满足高阶智驾需求,而基于Transformer的BEV融合方案通过统一坐标系下的多源传感器特征融合,在保证感知精度的同时兼顾算力可行性,显著提升复杂场景下的鲁棒性与系统可靠性。此外,文章指出BEV模型落地面临大算力依赖与高数据成本的挑战,提出“数据采集-模型训练-算法迭代-数据反哺”的高效数据闭环体系,通过自动化标注与长尾数据反馈实现算法持续进化,降低对人工标注的依赖,提升数据利用效率。典型企业案例进一步验证了该路径的技术可行性与经济价值。; 适合人群:从事汽车电子、智能驾驶感知算法研发的工程师,以及关注自动驾驶技术趋势的产品经理和技术管理者;具备一定自动驾驶基础知识,希望深入了解BEV架构与数据闭环机制的专业人士。; 使用场景及目标:①理解BEV+Transformer为何成为当前感知融合的主流技术路线;②掌握数据闭环在BEV模型迭代中的关键作用及其工程实现逻辑;③为智能驾驶系统架构设计、传感器选型与算法优化提供决策参考; 阅读建议:本文侧重技术趋势分析与系统级思考,建议结合实际项目背景阅读,重点关注BEV融合逻辑与数据闭环构建方法,并可延伸研究相关企业在舱泊一体等场景的应用实践。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值