fix: Resolve IMessageInspector2 Using Scope Resolver

----IMessageInsector2 is being Added as Scope Service, However, it is being resolve as Sington Service
DigDes · Dec 13, 2023 · 58afbb9 · 58afbb9
1 parent c419020
commit 58afbb9
Showing 1 changed file with 7 additions and 2 deletions.
diff --git a/src/SoapCore/SoapEndpointMiddleware.cs b/src/SoapCore/SoapEndpointMiddleware.cs
@@ -460,10 +460,15 @@ private async Task<Message> ProcessMessage(Message requestMessage, SoapMessageEn
 				throw new ArgumentException($"Unable to handle request without a valid action parameter. Please supply a valid soap action.");
 			}
 
-			var messageInspector2s = serviceProvider.GetServices<IMessageInspector2>();
 			var correlationObjects2 = default(List<(IMessageInspector2 inspector, object correlationObject)>);
 
-			correlationObjects2 = messageInspector2s.Select(mi => (inspector: mi, correlationObject: mi.AfterReceiveRequest(ref requestMessage, _service))).ToList();
+			using (IServiceScope scope = serviceProvider.CreateScope())
+			{
+				var messageInspector2s = scope.ServiceProvider.GetServices<IMessageInspector2>();
+				correlationObjects2 = messageInspector2s.Select(mi =>
+					(inspector: mi, correlationObject: mi.AfterReceiveRequest(ref requestMessage, _service)))
+					.ToList();
+			}
 
 			// for getting soapaction and parameters in (optional) body
 			// GetReaderAtBodyContents must not be called twice in one request