Comments on: Request/Response Service Layer: Synchronous Client-Side Usage http://davybrion.com/blog/2009/11/requestresponse-service-layer-synchronous-client-side-usage/ inquisitive: adjective. given to inquiry, research, or asking questions; eager for knowledge; intellectually curious Wed, 08 Feb 2012 11:42:42 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Davy Brionhttp://davybrion.com/blog/2009/11/requestresponse-service-layer-synchronous-client-side-usage/comment-page-1/#comment-98675 Davy Brion Mon, 14 Mar 2011 21:05:00 +0000 http://davybrion.com/blog/?p=1806#comment-98675 nope, sorry... the support is limited to the IOC container for now :)glad to hear it works! nope, sorry… the support is limited to the IOC container for now :)

glad to hear it works!

]]> By: Filip Kinskyhttp://davybrion.com/blog/2009/11/requestresponse-service-layer-synchronous-client-side-usage/comment-page-1/#comment-98674 Filip Kinsky Mon, 14 Mar 2011 20:57:00 +0000 http://davybrion.com/blog/?p=1806#comment-98674 Thanks for your response - I already created my own IRequestProcessor implementation which depends on IWcfRequestProcessor, which is registered as standard WCF service using Castle WCF facility. Than I set this class as ClientConfiguration.RequestProcessorImplementation - I can resolve IRequestDispatcher using Windsor now and everything works including the WCF Integration. Quite easy stuff - I was just expecting built-in support for the WCF facility when you support Windsor... Thanks for your response – I already created my own IRequestProcessor implementation which depends on IWcfRequestProcessor, which is registered as standard WCF service using Castle WCF facility. Than I set this class as ClientConfiguration.RequestProcessorImplementation – I can resolve IRequestDispatcher using Windsor now and everything works including the WCF Integration. Quite easy stuff – I was just expecting built-in support for the WCF facility when you support Windsor…

]]> By: Davy Brionhttp://davybrion.com/blog/2009/11/requestresponse-service-layer-synchronous-client-side-usage/comment-page-1/#comment-98673 Davy Brion Mon, 14 Mar 2011 20:29:00 +0000 http://davybrion.com/blog/?p=1806#comment-98673 i haven't used Windsor's WCF integration facility yet so i can't really help you with that yetwhat are the changes you need to make to use the WCF integration facility?btw, it would be better if we'd resume this discussion on the agatha mailing list: http://groups.google.com/group/agatha-rrsl i haven’t used Windsor’s WCF integration facility yet so i can’t really help you with that yet

what are the changes you need to make to use the WCF integration facility?

btw, it would be better if we’d resume this discussion on the agatha mailing list:
http://groups.google.com/group/agatha-rrsl

]]> By: Filip Kinskyhttp://davybrion.com/blog/2009/11/requestresponse-service-layer-synchronous-client-side-usage/comment-page-1/#comment-98668 Filip Kinsky Mon, 14 Mar 2011 13:59:00 +0000 http://davybrion.com/blog/?p=1806#comment-98668 Is there any simple method how to register client side request processor using Castle Windsor WCF integration facility? I'm using my standard WCF services like this:container.Register(WcfClient.ForChannels( new DefaultClientModel( WcfEndpoint.ForContract() .BoundTo(wcfConfigurator.GetServiceBinding()) .At(wcfConfigurator.GetServiceEndpointAddress("RequestProcessor.svc")) )));(wcfConfigurator is a helper class to get rid of WCF XML configuration hell)Now I'd like to slowly migrate my WCF services to Agatha, but still use Windsor WCF integration. At the moment I'm thinking about implementing my own IRequestProcessor and IAsyncRequestProcessor. Both depending on IWcfRequestProcessor and so utilizing the WCF integration facility. Is it right approach or is there any easier method I just overlooked?Anyway thanks for great framework :) Is there any simple method how to register client side request processor using Castle Windsor WCF integration facility? I’m using my standard WCF services like this:

container.Register(WcfClient.ForChannels(
new DefaultClientModel(
WcfEndpoint.ForContract()
.BoundTo(wcfConfigurator.GetServiceBinding())
.At(wcfConfigurator.GetServiceEndpointAddress(“RequestProcessor.svc”))
)));

(wcfConfigurator is a helper class to get rid of WCF XML configuration hell)

Now I’d like to slowly migrate my WCF services to Agatha, but still use Windsor WCF integration. At the moment I’m thinking about implementing my own IRequestProcessor and IAsyncRequestProcessor. Both depending on IWcfRequestProcessor and so utilizing the WCF integration facility. Is it right approach or is there any easier method I just overlooked?

Anyway thanks for great framework :)

]]>