spring boot 全局异常处理可以通过实现 graphqlexceptionresolver 接口来捕获 graphql 解析异常。具体做法是创建一个实现了该接口的 bean,在 resolveexception 方法中判断异常类型是否为 graphqlsyntaxerror 或 validationerror,如果是则返回自定义的 executionresult 对象,从而将解析错误转化为标准的 graphql 错误响应。

如何区分语法错误和验证错误
通过检查异常的具体类名可以区分这两类错误。GraphQLSyntaxError 通常发生在查询字符串无法被解析时,而 ValidationError 发生在查询语法正确但字段不存在或参数不匹配时。在 resolveException 方法中,可以使用 instanceof 关键字进行类型判断,分别构建不同的错误消息。

import graphql.GraphQL;
import graphql.ExecutionInput;
import graphql.ExecutionResult;
import graphql.schema.GraphQLSchema;
import graphql.servlet.GraphQlExceptionResolver;
import graphql.servlet.core.GraphQLInvocationInputFactory;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import graphql.error.GraphQLException;
import graphql.language.SourceLocation;
import java.util.Collections;
import java.util.List;
@Configuration
public class GraphQlConfig {
@Bean
public GraphQlExceptionResolver customExceptionResolver(GraphQLInvocationInputFactory invocationInputFactory) {
return (exception, executionInput) -> {
if (exception instanceof graphql.error.GraphQLSyntaxError) {
graphql.error.GraphQLSyntaxError syntaxError = (graphql.error.GraphQLSyntaxError) exception;
SourceLocation location = syntaxError.getSourceLocation();
String message = "Syntax Error at line " + location.getLine() + ", column " + location.getColumn() + ": " + syntaxError.getMessage();
return ExecutionResult.newExecutionResult().addError(syntaxError).build();
} else if (exception instanceof graphql.validation.ValidationError) {
graphql.validation.ValidationError validationError = (graphql.validation.ValidationError) exception;
List<graphql.error.error> errors = validationError.getErrors();
return ExecutionResult.newExecutionResult().errors(errors).build();
}
return null;
};
}
}</graphql.error.error>
如何处理非标准异常并返回统一格式
对于既不是语法错误也不是验证错误的其他异常(如运行时异常),可以在 resolveException 方法的最后返回 null,让 Spring Boot 的全局异常处理器(如 @ControllerAdvice)接管。这样可以确保只有 GraphQL 特有的解析问题被特殊处理,而其他业务异常依然遵循 RESTful 风格或默认的错误处理机制。同时,为了保持 GraphQL 响应的规范性,建议在所有 GraphQL 错误中包含 locations 和 path 信息。

import graphql.ExecutionResult;
import graphql.GraphQL;
import graphql.servlet.GraphQlExceptionResolver;
import graphql.servlet.core.GraphQLInvocationInputFactory;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import graphql.language.SourceLocation;
import java.util.Collections;
import java.util.List;
@Configuration
public class AdvancedGraphQlConfig {
@Bean
public GraphQlExceptionResolver advancedExceptionResolver(GraphQLInvocationInputFactory invocationInputFactory) {
return (exception, executionInput) -> {
// 处理语法错误
if (exception instanceof graphql.error.GraphQLSyntaxError) {
graphql.error.GraphQLSyntaxError err = (graphql.error.GraphQLSyntaxError) exception;
return ExecutionResult.newExecutionResult()
.addError(err)
.build();
}
// 处理验证错误
if (exception instanceof graphql.validation.ValidationError) {
graphql.validation.ValidationError err = (graphql.validation.ValidationError) exception;
return ExecutionResult.newExecutionResult()
.errors(err.getErrors())
.build();
}
// 其他异常交由 Spring 处理
return null;
};
}
}











