在Blazor中使用JsonPatchDocument发生意外错误

如何解决在Blazor中使用JsonPatchDocument发生意外错误

我正在使用Blazor WebAssembly(WASM)客户端通过.NET Core REST API执行更新。为此,我通过HTTP PATCH请求发送了JsonPatchDocument<T>,其中T是我应用程序的数据传输对象(DTO)之一。

它不起作用。我在Blazor应用程序中返回了500个内部服务器错误状态代码。我在Postman中了解了更多细节,但不足以让我理解问题。

这是我的Blazor WASM应用程序中的调用代码:

@code
{
[Parameter]
public int BookId { get; set; } = 101;

private async Task HandleClickAsync()
{
    string newTitle = "How to make JsonPatchDocument work with Blazor - Second Edition";

    var patchDocument = new JsonPatchDocument<Book>()
        .Replace(c => c.Title,newTitle);

    var json = JsonSerializer.Serialize(patchDocument);
    var content = new StringContent(json,Encoding.UTF8,"application/json-patch+json");
    var response = await HttpClient.PatchAsync($"https://localhost:44367/api/books/{BookId}",content);


    if (response.IsSuccessStatusCode)
    {
        // Handle success
    }
    else if (response.StatusCode == HttpStatusCode.NotFound)
    {
        // Handle not found
    }
    else
    {
        // Handle unexpected failures
    }
}
}

这是我的控制器方法:

[ApiController]
[Route("api/[controller]")]
public class BooksController : ControllerBase
{
    [HttpPatch("{id:int}")]
    public async Task<ActionResult> PatchAsync(
        int id,[FromBody] JsonPatchDocument<Book> patch)
    {
        // We're just going to fake an asynchronous database call and return a 200 status code to the client
        await Task.FromResult(true);
        return Ok();
    }
}

这是我的DTO:

public class Book
{
    public int Id { get; set; }

    public string Title { get; set; }
}

我发送的补丁文档序列化为JSON时,如下所示:

{"Operations":[{"value":"How to make JsonPatchDocument work with Blazor - Second Edition","OperationType":2,"path":"/Title","op":"replace","from":null}],"ContractResolver":{}}

我在邮递员中看到的错误详细信息是:

System.NotSupportedException: Deserialization of interface types is not supported. Type 'Newtonsoft.Json.Serialization.IContractResolver'
   at System.Text.Json.ThrowHelper.ThrowNotSupportedException_DeserializeCreateObjectDelegateIsNull(Type invalidType)
   at System.Text.Json.JsonSerializer.HandleStartObject(JsonSerializerOptions options,ReadStack& state)
   at System.Text.Json.JsonSerializer.ReadCore(JsonSerializerOptions options,Utf8JsonReader& reader,ReadStack& readStack)
   at System.Text.Json.JsonSerializer.ReadCore(JsonReaderState& readerState,Boolean isFinalBlock,ReadOnlySpan`1 buffer,JsonSerializerOptions options,ReadStack& readStack)
   at System.Text.Json.JsonSerializer.ReadAsync[TValue](Stream utf8Json,Type returnType,CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Mvc.Formatters.SystemTextJsonInputFormatter.ReadRequestBodyAsync(InputFormatterContext context,Encoding encoding)
   at Microsoft.AspNetCore.Mvc.Formatters.SystemTextJsonInputFormatter.ReadRequestBodyAsync(InputFormatterContext context,Encoding encoding)
   at Microsoft.AspNetCore.Mvc.ModelBinding.Binders.BodyModelBinder.BindModelAsync(ModelBindingContext bindingContext)
   at Microsoft.AspNetCore.Mvc.ModelBinding.ParameterBinder.BindModelAsync(ActionContext actionContext,IModelBinder modelBinder,IValueProvider valueProvider,ParameterDescriptor parameter,ModelMetadata metadata,Object value)
   at Microsoft.AspNetCore.Mvc.Controllers.ControllerBinderDelegateProvider.<>c__DisplayClass0_0.<<CreateBinderDelegate>g__Bind|0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeInnerFilterAsync>g__Awaited|13_0(ControllerActionInvoker invoker,Task lastTask,State next,Scope scope,Object state,Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|24_0(ResourceInvoker invoker,Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next,Scope& scope,Object& state,Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker,Task task,IDisposable scope)
   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint,Task requestTask,ILogger logger)
   at Microsoft.AspNetCore.Builder.Extensions.MapWhenMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

HEADERS
=======
Accept: */*
Accept-Encoding: gzip,deflate,br
Cache-Control: no-cache
Connection: keep-alive
Content-Length: 175
Content-Type: application/json
Host: localhost:44367
User-Agent: PostmanRuntime/7.26.3
Postman-Token: b4444f41-b80f-4ef5-92d5-2416d68d471e

我的项目中没有一个直接依赖Newtonsoft。我不知道我引用的Microsoft库是否依赖于Newtonsoft。该错误表明也许他们这样做。

该行为可以在GitHub上的这个小存储库中观察到: https://github.com/BenjaminCharlton/JsonPatchDocumentWithBlazor

请问有人知道为什么它不起作用和/或会解决什么问题吗?

谢谢

解决方法

我设法解决了这一难题,Pavel和Enet的输入都很有用,谢谢。

对于其他遇到相同问题的人,这是您需要解决的问题:

  1. 截至目前(2020年末),将.NET Core从Newtonsoft.Json移至System.Text.Json的努力还没有完成。软件包Microsoft.AspNetCore.JsonPatch仍然取决于Newtonsoft.Json

  2. .NET Core开发团队意识到GitHub在报告此问题方面存在很多问题。但是他们都没有采取任何行动而被关闭。显然,将Microsoft.AspNetCore.JsonPatch切换到System.Text.Json涉及很多工作。

  3. 要将Newtonsoft用于JsonPatch,而不能将其他there is a nice little hack described here用于Web API /服务器项目的Startup类中。特别注意在GetJsonPatchInputFormatter

    内部调用的Startup.ConfigureServices辅助方法的使用
  4. 但是,单独使用它可能无法解决Blazor WASM /客户端项目将收到的50X和40X HTTP错误,因为如果使用JsonPatch序列化System.Text.Json,它将添加一个空的ContractResolver对象到JSON字符串的末尾(看起来像,"ContractResolver":{} ),它在服务器端中断。由于某种原因,该请求与您所执行的任何控制器路由都不匹配。

  5. 要解决此问题,您还必须在Blazor客户端上使用Newtonsoft.Json。您不必将其用于所有内容;您只需要使用它来序列化所有JsonPatch。与Newtonsoft.Json相比,System.Text.Json的代码行多了几行,但是我做了一个扩展方法,因此不会在各处重复。扩展方法如下:

     public static class HttpClientExtensions
     {
         public static async Task<HttpResponseMessage> PatchAsync<T>(this HttpClient client,string requestUri,JsonPatchDocument<T> patchDocument)
         where T : class
     {
         var writer = new StringWriter();
         var serializer = new JsonSerializer();
         serializer.Serialize(writer,patchDocument);
         var json = writer.ToString();
    
         var content = new StringContent(json,Encoding.UTF8,"application/json-patch+json");
         return await client.PatchAsync(requestUri,content);
     }
    

    }

就是这样。此解决方法对我有用,我希望对您也有用。

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-
参考1 参考2 解决方案 # 点击安装源 协议选择 http:// 路径填写 mirrors.aliyun.com/centos/8.3.2011/BaseOS/x86_64/os URL类型 软件库URL 其他路径 # 版本 7 mirrors.aliyun.com/centos/7/os/x86
报错1 [root@slave1 data_mocker]# kafka-console-consumer.sh --bootstrap-server slave1:9092 --topic topic_db [2023-12-19 18:31:12,770] WARN [Consumer clie
错误1 # 重写数据 hive (edu)&gt; insert overwrite table dwd_trade_cart_add_inc &gt; select data.id, &gt; data.user_id, &gt; data.course_id, &gt; date_format(
错误1 hive (edu)&gt; insert into huanhuan values(1,&#39;haoge&#39;); Query ID = root_20240110071417_fe1517ad-3607-41f4-bdcf-d00b98ac443e Total jobs = 1
报错1:执行到如下就不执行了,没有显示Successfully registered new MBean. [root@slave1 bin]# /usr/local/software/flume-1.9.0/bin/flume-ng agent -n a1 -c /usr/local/softwa
虚拟及没有启动任何服务器查看jps会显示jps,如果没有显示任何东西 [root@slave2 ~]# jps 9647 Jps 解决方案 # 进入/tmp查看 [root@slave1 dfs]# cd /tmp [root@slave1 tmp]# ll 总用量 48 drwxr-xr-x. 2
报错1 hive&gt; show databases; OK Failed with exception java.io.IOException:java.lang.RuntimeException: Error in configuring object Time taken: 0.474 se
报错1 [root@localhost ~]# vim -bash: vim: 未找到命令 安装vim yum -y install vim* # 查看是否安装成功 [root@hadoop01 hadoop]# rpm -qa |grep vim vim-X11-7.4.629-8.el7_9.x
修改hadoop配置 vi /usr/local/software/hadoop-2.9.2/etc/hadoop/yarn-site.xml # 添加如下 &lt;configuration&gt; &lt;property&gt; &lt;name&gt;yarn.nodemanager.res