The WCFFacility helps facilitate the registration of those behaviors. Once registered, its WCF that executes them.
On Mar 21, 2011, at 12:52 PM, Scott_M wrote: > Running WCFIntegration 1.0.3.0 and stumbled into an interesting problem > today. We have a custom ServiceBehavior that uses IServiceBehavior.Validate > to inject Microsoft W.I.F. security token handler configuration before the > service host is opened. Unfortunately, IServiceBehavior.Validate is never > called by WcfIntegration, only ApplyDispatchBehavior is called. The WIF > security token handler stuff has to happen in Validate otherwise it doesn't > work properly. Note, our host > is built by a custom AbstractServiceHostBuilder<M> implementation > (WSTrustServiceHostBuilder, thanks Craig). Is there something special we > have to do get IServiceBehavior.Validate to be called by WcfIntegration? > > > thanks > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Users" group. > 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. -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. 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.
