blocks|key|3326379|text|Castle+WCF集成工具使您能够通过使用DynamicProxy代理来实现这一点(在许多有用的功能中)。看看here吧。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3326380|关于它的文档不多，所以有关如何使用它的文档，最好看看它的测试。|3326381|entityMap|0|LINK|mutability|MUTABLE|url|http://www.castleproject.org/container/facilities/trunk/wcf/index.html^0|1K|4|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Castle WCF integration facility enables you to do just that (among many useful things) by using DynamicProxy proxies.
Take a look <a href="http://www.castleproject.org/container/facilities/trunk/wcf/index.html" rel="nofollow noreferrer">here</a>.

There's not much documentation on it, so for docs on how to use it it's best to take a look at its tests.

blocks|key|345289|text|我花了很长时间，但我确实找到了一种比找到并艰难地浏览整个合同更好的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|345290|string+action+=+operationContext.IncomingMessageHeaders.Action;
DispatchOperation+operation+=+
++++operationContext.EndpointDispatcher.DispatchRuntime.Operations.FirstOrDefault(o+=>
++++++++o.Action+==+action);
//+Insert+your+own+error-handling+here+if+(operation+==+null)
Type+hostType+=+operationContext.Host.Description.ServiceType;
MethodInfo+method+=+hostType.GetMethod(operation.Name);|code-block|syntax|javascript|345291|你就来了。您可以获取属性或执行其他任何您喜欢的操作。|345292|注意:您可能会尝试在DispatchRuntime中使用OperationSelector。我发现的问题是，在我的例子中，在处理的特定阶段，OperationSelector是一个空引用。如果您可以访问此属性，那么使用它可能比像上面那样“扫描”OperationCollection更快、更可靠。|345293|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

It took me forever, but I did find a way that's better than finding and slogging through the entire contract:

<pre><code>string action = operationContext.IncomingMessageHeaders.Action;
DispatchOperation operation = 
 operationContext.EndpointDispatcher.DispatchRuntime.Operations.FirstOrDefault(o =&gt;
 o.Action == action);
// Insert your own error-handling here if (operation == null)
Type hostType = operationContext.Host.Description.ServiceType;
MethodInfo method = hostType.GetMethod(operation.Name);
</code></pre>

And there you are. You can get the attributes or do whatever else you like.

Note: You might be tempted to try to use the OperationSelector in the DispatchRuntime. The problem I found was that in my case, at the particular stage of processing, the OperationSelector was a null reference. If you have access to this property, it's probably faster and more reliable to use than "scanning" the OperationCollection as above.

blocks|key|345303|text|如果OperationContext.CurrentIncomingMessageHeaders.Action为null，您可以这样做--这有点简洁：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|345304|string+actionName+=+OperationContext.Current.IncomingMessageProperties["HttpOperationName"]+as+string;
Type+hostType+=+operationContext.Host.Description.ServiceType;
MethodInfo+method+=+hostType.GetMethod(actionName);|code-block|syntax|javascript|345305|entityMap^0|2|1H|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

If <code>OperationContext.CurrentIncomingMessageHeaders.Action</code> is null, you can do this -- it's a bit terser:

<pre><code>string actionName = OperationContext.Current.IncomingMessageProperties["HttpOperationName"] as string;
Type hostType = operationContext.Host.Description.ServiceType;
MethodInfo method = hostType.GetMethod(actionName);
</code></pre>

blocks|key|3113570|text|基于@航空和@TimDog的回答，以及this+SO+question，我提出了一个解决方案，即应该同时适用于REST和SOAP。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3113571|///<summary>Returns+the+Method+info+for+the+method+(OperationContract)+that+is+called+in+this+WCF+request.</summary>
System.Reflection.MethodInfo+GetActionMethodInfo(System.ServiceModel.OperationContext+operationContext+){
++++string+bindingName+=+operationContext.EndpointDispatcher.ChannelDispatcher.BindingName;
++++string+methodName;
++++if(bindingName.Contains("WebHttpBinding")){
++++++++++++//REST+request
++++++++++++methodName+=+(string)+operationContext.IncomingMessageProperties["HttpOperationName"];
++++}else{
++++++++++++//SOAP+request
++++++++++++string+action+=+operationContext.IncomingMessageHeaders.Action;
++++++++++++methodName+=+operationContext.EndpointDispatcher.DispatchRuntime.Operations.FirstOrDefault(o+=>o.Action+==+action).Name;
++++}
++++//+Insert+your+own+error-handling+here+if+(operation+==+null)
++++Type+hostType+=+operationContext.Host.Description.ServiceType;
++++return+hostType.GetMethod(methodName);
}|code-block|syntax|javascript|3113572|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/3179863/wcf-destinguish-between-rest-and-soap-requests-using-the-operationcontext^0|1C|G|J|G|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@$9|V|A|W|1|X]]|E|$]]|$1|F|3|G|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

Based on @Aaronaught and @TimDog 's answers, and <a href="https://stackoverflow.com/questions/3179863/wcf-destinguish-between-rest-and-soap-requests-using-the-operationcontext">this SO question</a> I came up with a solution that should work for both REST and SOAP.

<pre><code>///&lt;summary&gt;Returns the Method info for the method (OperationContract) that is called in this WCF request.&lt;/summary&gt;
System.Reflection.MethodInfo GetActionMethodInfo(System.ServiceModel.OperationContext operationContext ){
 string bindingName = operationContext.EndpointDispatcher.ChannelDispatcher.BindingName;
 string methodName;
 if(bindingName.Contains("WebHttpBinding")){
 //REST request
 methodName = (string) operationContext.IncomingMessageProperties["HttpOperationName"];
 }else{
 //SOAP request
 string action = operationContext.IncomingMessageHeaders.Action;
 methodName = operationContext.EndpointDispatcher.DispatchRuntime.Operations.FirstOrDefault(o =&gt;o.Action == action).Name;
 }
 // Insert your own error-handling here if (operation == null)
 Type hostType = operationContext.Host.Description.ServiceType;
 return hostType.GetMethod(methodName);
}
</code></pre>

Is there an elegant way to get the method that will be executed on a service instance from MessageInspector/AuthorizationPolicy/some other extension point? I could use

<blockquote>
 OperationContext.Current.IncomingMessageHeaders.Action
</blockquote>

but I hope there's some way to do it without manually matching SOAP actions with OperationContracts.

What I'm trying to do is examine the method's attributes before it executes.

WCF: Retrieving MethodInfo from OperationContext

有没有一种优雅的方法可以从MessageInspector/AuthorizationPolicy/其他扩展点获取将在服务实例上执行的方法？我可以用 OperationContext.Current.IncomingMessageHeaders.Action但我希望有一些方法可以做到这一点，而不需要手动将SOAP操作与...

问WCF:从OperationContext检索MethodInfo
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WCF:从OperationContext检索MethodInfoEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WCF:从OperationContext检索MethodInfo
EN