I don't believe an OperationContext.Current is available at the point where a custom UserNamePasswordValidator is called. This could be why no scope could be obtained. Is it possible to choose a different lifestyle.
-craig On May 14, 2012, at 8:04 AM, Fabrice wrote: > > Hello, > > I've a problem with WcfPerOperation lifestyle after upgraded my project from > Castle 2.5.2 to Castle 3.0 > I've posted on StackOverflow and only after I thinked it could be better to > post here... > > But anyway here is the link: > http://stackoverflow.com/questions/10579236/componentresolutionexception-after-upgrading-to-castle-3-0 > > > Thank you for any help! > Fabrice > > -- > 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.
