faultexception

问题 I have a question on how to send a custom exception as FaultException. It works when I use a system Exception like ArgumentException, but if I change it to my custom exception "TestException" it fails. I can’t get the configuration for the service reference, when I try to add it. Works: [OperationContract] [FaultContract(typeof(ArgumentException))] [TransportChannel TestMethod (); public Void TestMethod() { throw new FaultException<ArgumentException>(new ArgumentException("test"), new

问题 1)In my windows application client, call the multiple wcf services using the ChannelFactory method. In one of client method call the multiple service one by one, after idle timeout I create a channel for one service object whenever Faulted event fire but how can i maintain the other service channel which is also faulted the same time? Or in More simple words 2)In my windows application client, consume the wcf service using the ChannelFactory method, can i catch the Faultexception in service

问题 I'm trying to create some custom FaultException . I've made a DataContract class called CreateFault . [DataContract] public class CreateFault { private string report; public CreateFault(string message) { this.report = message; } [DataMember] public string Message { get { return this.report; } set { this.report = value; } } } I'm then throwing the fault in a service method. In IService1.cs [OperationContract] [FaultContract(typeof(CreateFault))] void TestFaultException(); and in Service1.cs

问题 I understand that WCF will convert an exception into a fault and send it back as a SOAP message, but I was wondering if this is truly interoperable. I guess I'm having a tough time trying to figure out this possible scenario: Client (Java) calls a WCF Service (LoginService). Server checks for proper authorization, user authorization fails. Server throws an UnauthorizedAccessException. WCF converts this into a Fault somehow. (* - See Below As Well) Client has to be able to know how to read

问题 I've read all there is to read on this, but maybe I'm missing something (well, definitely I'm missing something otherwise it would be working already) I'm throwing some exception error inside my server business layer: public class RfcException : Exception { public RfcException(string _m, Exception _inner) : base(_m, _inner) { } public Dictionary<string, string> ExtendedProperties { get { return extendedProperties; } protected set { extendedProperties = value; } } private Dictionary<string,

问题 So I'm trying to use Enterprise Library in my WCF service to do some of the exception-related work for me. My idea is to set up a " Custom Exception Handler " for say "NullReferenceException" and in the "Custom Exception Handler" create FaultException exception. My understanding is that this "new" exception will then make it across the wire and I will catch it at the client. Some code for better understanding: WCF service: [ServiceContract(Name="MyService", ConfigurationName="MyNamespace

问题 A single tier application can distinguish exceptions by: Exception ex; if (ex is System.DirectoryServices.AccountManagement.PasswordException) ... where ex is just a generic exception. When you move to WCF for multi-tier, you lose all this and you need to use the FaultException mechanism. The problem is that I can't find any way to do the above. In my client I want to catch the FaultException types and then distinguish between them i.e. something like: catch (FaultException ex) { if

问题 I have a simple IPC mechanism that uses WCF and named pipes. My goal is to propagate exception details (including the stacktrace) to the client for logging purposes (the rest of the application logging is located on the client). If I use the following code I am able to catch FaultException<Exception> on the client and see exception details: Contract: [ServiceContract] public interface IService { [OperationContract] [FaultContract(typeof(Exception))] void DoSomething(); } Implementation:

问题 I have a WCF service being called as part of a transaction. If the service is called twice (often happening during debugging) I want a FaultException to be thrown by the service but the overall transaction must succeed . throw new FaultException("Duplicate action not allowed for " + msgIn.ActionType, new FaultCode("DUPE_ACTION")); Since I'm throwing a FaultException the transaction will vote to abort right? I'm considering doing this (setting the transaction complete - and then throwing the

问题 When building a WCF service, if I don't include my contract for the FaultException in the service, I'm able to create a WCF service reference on the client with all of the members included in the Reference.cs file. If I include my FaultException contract, two things happen. In the WCF test client, I have a red "X" next to the contract name (CreateFaultMessage) When I create the WCF service reference, not all of the members are included in the Reference.cs file. I am hoping somebody will be