I'm sorry to revive such an old post, but the posibilities mentioned here
about providing an "implementation" of services based only on interceptors
sound great.
Did you ever make this work? Was it included in the Wcf Facility?
El jueves, 4 de febrero de 2010 12:50:02 UTC-3, fredlegrain escribió:
> I'd like to customize WCF Integration Facility to make capable of
> exposing a service host based on a provided ServiceContract interface
> and handling calls through a provided interceptor.
>
> Let's say I have a ServiceContract interface :
>
> [ServiceContract]
> public interface IHelloService {
> [OperationContract]
> string SayHello(string message);
> }
>
> Let's says I don't have (and don't want to have) any implementation of
> IHelloService.
> But I have an interceptor (let's call it HelloServiceInterceptor)
> which knows how to answer the service calls.
>
> I'd like to have my init code look like this :
>
> container.Register(Component
> .For(typeof(IHelloService))
> .Interceptors(typeof(HelloServiceInterceptor)).First
> .ActAs(new DefaultServiceModel()
> .AddEndpoints(WcfEndpoint
> .BoundTo(new BasicHttpBinding())
> .At("http://localhost:6080/HelloService/";)
> )
> )
> );
>
> Do you expect that be feasible?
> How can I customize Windsor and/or WCF Integration Facility to achieve
> that?
> Maybe a custom ServiceModel would allow me to do the job?
>
> Cheers,
> Frédéric
>
>
--
You received this message because you are subscribed to the Google Groups
"Castle Project Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/castle-project-users/-/Wun36V0xlAQJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-users?hl=en.
