You're attaching message inspectors from behaviors. But (using WcfFacility) behaviors are resolved trough container. And usually, in behavior you do "new MyMessageInspector()". So, to have your message created by container, you can use a factory injected in behavior. Or either inject in behavior the services required by your message inspector and pass them in inspector's constructor.
Does it make sense? On Thu, Jul 8, 2010 at 4:01 AM, Adam Langley <[email protected]> wrote: > Hi, > > I am using the WcfFacility on the client to create channels. I would > also like to inject a messageinspector, but I would like this > message-inspector to have a reference to a service also managed by the > micro-kernel. Is there a way in the WcfFacility to do this? > The idea is that my Wcf message-inspector can then use a service to > notify the running application of all communications running through the > WCF pipeline... > > Adam Langley > > -- > 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]<castle-project-users%[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.
