Databases
StackOverflow2013
Postsdbo
POUsing Generics to encapsulate common method work
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing Generics to encapsulate common method work
    primarykey
    data
    text
    <p>I've got a number of WebService methods that all include some very boilerplate code of wrapping the actual work in a try/catch/finally and performing the same tasks in the catch/finally. So as a way to encapsulate all of the shared catch/finally stuff I wrote a simple generic.</p> <p>This works and really eliminates a bunch of repetitive code but feels klunky, and the syntax is very obtuse. Every time I come back to this my brain gets twisted trying to figure it out (a clear sign it is not a good design). I'm looking for feedback on whether this is a crazy thing to do, and if there is a better way to approach it.</p> <p>Here is my template:</p> <pre><code>public delegate T2 RestfulServiceRequest&lt;T1, T2&gt;(T1 req); static class RestfulService { public static T2 ExceptionHandler&lt;T1, T2&gt;(RestfulServiceRequest&lt;T1, T2&gt; serviceCall, T1 req) { if (req == null) throw new BadRequestException(new ArgumentNullException("Invalid or missing request object")); try { return serviceCall(req); } catch (RestfulException e) { // log it and rethrow Logger.Write(e); throw; } catch (Exception e) { Logger.Error(e); // wrap in a consistent exception for propagation back to caller throw new InternalServerException(e); } finally { Logger.Debug("Complete"); } } } </code></pre> <p>}</p> <p>And here is a usage of it:</p> <pre><code>public class Initialization : IInitialization { // MyMethod thas uses the template public ApplianceInitResp CreateApplianceServer(ApplianceInitReq req) { return RestfulService.ExceptionHandler&lt;ApplianceInitReq, ApplianceInitResp&gt;(delegate(ApplianceInitReq x) { // do some work return new ApplianceInitResp(); }, req); } } </code></pre> <p>}</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USBrettRobi
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUsing Generics to encapsulate common method work
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POUsing Generics to encapsulate common method work
      1. USPhil H
      1. VTFavorite
    3. VO
      singulars
      1. POUsing Generics to encapsulate common method work
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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