Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>EDIT:</strong> Updated the post with a proper custom json error handler</p> <h2>The quick but non-preffered way.</h2> <pre><code>&lt;serviceDebug includeExceptionDetailInFaults="true"/&gt; </code></pre> <p>In Your service behavior will give you all the details you need.</p> <h2>The Nice way</h2> <p>All exceptions from the application are converted to an <code>JsonError</code> and serialized using a <code>DataContractJsonSerializer</code>. The <code>Exception.Message</code> is used directly. FaultExceptions provide the FaultCode and other exception are threated as unknown with faultcode -1.</p> <p>FaultException are sent with HTTP status code 400 and other exceptions are HTTP code 500 - internal server error. This not nescessary as the faultcode can be used to decide if it is and unknown error. It was however convenient in my app.</p> <p><strong>The error handler</strong></p> <pre><code>internal class CustomErrorHandler : IErrorHandler { public bool HandleError(Exception error) { //Tell the system that we handle all errors here. return true; } public void ProvideFault(Exception error, System.ServiceModel.Channels.MessageVersion version, ref System.ServiceModel.Channels.Message fault) { if (error is FaultException&lt;int&gt;) { FaultException&lt;int&gt; fe = (FaultException&lt;int&gt;)error; //Detail for the returned value int faultCode = fe.Detail; string cause = fe.Message; //The json serializable object JsonError msErrObject = new JsonError { Message = cause, FaultCode = faultCode }; //The fault to be returned fault = Message.CreateMessage(version, "", msErrObject, new DataContractJsonSerializer(msErrObject.GetType())); // tell WCF to use JSON encoding rather than default XML WebBodyFormatMessageProperty wbf = new WebBodyFormatMessageProperty(WebContentFormat.Json); // Add the formatter to the fault fault.Properties.Add(WebBodyFormatMessageProperty.Name, wbf); //Modify response HttpResponseMessageProperty rmp = new HttpResponseMessageProperty(); // return custom error code, 400. rmp.StatusCode = System.Net.HttpStatusCode.BadRequest; rmp.StatusDescription = "Bad request"; //Mark the jsonerror and json content rmp.Headers[HttpResponseHeader.ContentType] = "application/json"; rmp.Headers["jsonerror"] = "true"; //Add to fault fault.Properties.Add(HttpResponseMessageProperty.Name, rmp); } else { //Arbitraty error JsonError msErrObject = new JsonError { Message = error.Message, FaultCode = -1}; // create a fault message containing our FaultContract object fault = Message.CreateMessage(version, "", msErrObject, new DataContractJsonSerializer(msErrObject.GetType())); // tell WCF to use JSON encoding rather than default XML var wbf = new WebBodyFormatMessageProperty(WebContentFormat.Json); fault.Properties.Add(WebBodyFormatMessageProperty.Name, wbf); //Modify response var rmp = new HttpResponseMessageProperty(); rmp.Headers[HttpResponseHeader.ContentType] = "application/json"; rmp.Headers["jsonerror"] = "true"; //Internal server error with exception mesasage as status. rmp.StatusCode = System.Net.HttpStatusCode.InternalServerError; rmp.StatusDescription = error.Message; fault.Properties.Add(HttpResponseMessageProperty.Name, rmp); } } #endregion } </code></pre> <p><strong>Webbehaviour used to install the above error handler</strong></p> <pre><code>internal class AddErrorHandlerBehavior : WebHttpBehavior { protected override void AddServerErrorHandlers(ServiceEndpoint endpoint, EndpointDispatcher endpointDispatcher) { base.AddServerErrorHandlers(endpoint, endpointDispatcher); //Remove all other error handlers endpointDispatcher.ChannelDispatcher.ErrorHandlers.Clear(); //Add our own endpointDispatcher.ChannelDispatcher.ErrorHandlers.Add(new CustomErrorHandler()); } } </code></pre> <p><strong>The json error data contract</strong></p> <p>Specifies the json error format. Add properties here to change the error format.</p> <pre><code>[DataContractFormat] public class JsonError { [DataMember] public string Message { get; set; } [DataMember] public int FaultCode { get; set; } } </code></pre> <p><strong>Using the error handler</strong></p> <p>Self-hosted</p> <pre><code>ServiceHost wsHost = new ServiceHost(new Webservice1(), new Uri("http://localhost/json")); ServiceEndpoint wsEndpoint = wsHost.AddServiceEndpoint(typeof(IWebservice1), new WebHttpBinding(), string.Empty); wsEndpoint.Behaviors.Add(new AddErrorHandlerBehavior()); </code></pre> <p>App.config</p> <pre><code>&lt;extensions&gt; &lt;behaviorExtensions&gt; &lt;add name="errorHandler" type="WcfServiceLibrary1.ErrorHandlerElement, WcfServiceLibrary1" /&gt; &lt;/behaviorExtensions&gt; &lt;/extensions&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POReturning Error Details from AJAX-Enabled WCF Service
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USFedearne
    1. USFedearne
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POReturning Error Details from AJAX-Enabled WCF Service
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMost of the articles I've read seem to frown upon including exception details in production settings since it's exposing information about your service's implementation. That said, none of those same articles seem to offer a "better" solution to returning error information.
      singulars
      1. PO
      1. USAwesomeTown
    2. COIt should be noted that there is a bug in WCF that when adding the assembly information to the behaviorExtension tag, you need to use the fully qualified name (tack on `, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null` if the code is in the same assembly as your services).
      singulars
      1. PO
      1. USJustin Niessner
    3. COI do not know why, but the simple `<serviceDebug includeExceptionDetailInFaults="true" />` in the service behaviour in my Web.config didn't work for me. But when I added the same directive into my code file (as `[ServiceBehavior(IncludeExceptionDetailInFaults = true)]` above the class declaration, from [this question](http://stackoverflow.com/q/7404478/575530)) it worked.
      singulars
      1. PO
      1. USdumbledad
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload