Agatha 1.2 Is Available

9 commentsWritten on September 28th, 2010 by
Categories: agatha

Agatha 1.2 is now available... keep in mind that this version targets .NET 4 and Silverlight 4 only. The most important change in this version is by far the client-side caching support, but there are some other improvements as well. These are the changes that were made between 1.1 and 1.2:

  • Client-side caching (BREAKING CHANGE: EnableResponseCachingAttribute no longer exists, use the EnableServiceResponseCachingAttribute instead) -> this is not supported in the in-process model
  • RequestProcessor now has an AfterHandle(request, response) virtual method which is called after the request has been handled by the handler
  • ReceivedResponses now has a Responses property which returns all of the retrieved responses
  • ExceptionInfo now has a FaultCode property (string) which will be automatically filled in as long as your BusinessException type contains a FaultCode property (thanks to a patch from Huseyin Tufekcilerli)
  • Agatha.Spring has been included (thanks to a patch from Jernej Logar)
  • Agatha.StructureMap.Container has been fixed so that it instructs StructureMap to use the default constructors of RequestProcessorProxy and AsyncRequestProcessorProxy (thanks to a patch by Bart Deleye)
  • Added BeforeResolvingRequestHandler virtual method to the RequestProcessor which gets called right before a RequestHandler is resolved through the container
  • Fixed logging of WCF messages where some requests were logged as "... stream ..." (thanks to patch by Bart Deleye)
  • Added Agatha.Ninject.Silveright (thanks to patch by Bart Deleye)
  • Updated Agatha.Unity and Agatha.Unity.Silverlight to use the 2.0 version of Unity
  • Applied patch from Andrew Rea to improve REST support (xml and json)

Thanks to everyone who contributed to this release. It's very nice to see the list of contributors growing with each release :)

You can download the source code or the binaries here.

  • Pingback: Tweets that mention Agatha 1.2 Is Available | The Inquisitive Coder – Davy Brion's Blog -- Topsy.com

  • Daniel

    why only support for .net 4.0?
    .net 3.5 is still widely used, more than 4.0

  • http://davybrion.com Davy Brion

    @Daniel

    we already depend on some WCF4 features for the REST support

  • Pingback: The Morning Brew - Chris Alcock » The Morning Brew #696

  • bennyb

    No support for .NET 3.5?
    Which features in WCF4 do you depend on (for REST) that is not in the WCF REST Contrib project?

  • http://davybrion.com Davy Brion

    @BennyB

    i have no idea which exact feature it was… it was in a patch contributed by Andrew Rea and since i know little of the REST stuff (learning about it is on my TODO list though ;) ) i didn’t bother to see if it could be done with the WCF REST Contrib project

    As for the decision to only target .NET 4, it was mentioned when i announced 1.1 that it would be the last version to support 3.5 and before that, i asked the question on the Agatha mailinglist. In either case, nobody objected to it back then so the decision was made, for better or worse.

  • Mark

    Thanks for the StructureMap fix. Glad to see such good continued progress.

  • ashraf

    Thanks Davy. How you handle scenario such as response contains business violations (ex: data annotation violation we use in ASP.NET MVC) not the actual result? I am considering to have a Violation property on Response class.

    • http://davybrion.com Davy Brion

      yeah, we used to do something similar… we had a ValidationSummary on our base response class which we’d use to store such messages