我已经在CXF客户端上使用了jaxrs-in-interceptor,提供者和异常映射器。在我的情况下,我通过in-interceptor捕获来自客户端的错误响应,然后我想中止cxf总线链并抛出错误。不幸的是我无法做到这一点,因为在每种情况下,拦截器抛出的异常只被记录,但是主要错误(错误的json格式)被传播到异常映射器。我想避免异常映射器,但我不知道如何。我使用WebClient来实现这样的拦截器:
@Component
public class MyInterceptor extends AbstractPhaseInterceptor<Message> {
public MyInterceptor() {
super(POST_STREAM);
}
@Override
public void handleMessage(Message message) throws Fault {
if (message != null) {
//message.getExchange().setOneWay(true);
//message.getExchange().put(Exception.class, new MyException());
//message.getInterceptorChain().abort();
//message.setContent(Exception.class, new MyException());
//Endpoint ep = message.getExchange().get(Endpoint.class);
//message.getInterceptorChain().abort();
//if (ep.getInFaultObserver() != null) {
// ep.getInFaultObserver().onMessage(message);
//}
//throw new WebApplicationException( new MyException());
//message.setContent(Response.class, response);
throw new Fault(new MyException());
}
}
我读到我应该实现jaxrs-filter导致拦截器抛出的异常不会传播到异常映射器。由于WebClient的实现,在java中是否可以这样做?
S client = create(url, clazz, list(jsonProvider(), providers));
WebClient.getConfig(client).getInInterceptors().add(new MyInterceptor());
我也试图在拦截器上使用不同的阶段,但它也没有用。
答案 0 :(得分:5)
我一直在研究和测试您的问题。问题是从CXF拦截器抛出的异常逃脱了JAX-RS流(CXF团队的see the answer)
拦截器生成的Fault
可以在拦截器本身中实现handleFault
public void handleFault(Message message) {
Exception e = message.getContent(Exception.class);
}
或实施FaultListener
并在CXF Bus
WebClient.getConfig(client).getBus().getProperties().put("org.apache.cxf.logging.FaultListener",new MyFaultListener());
public class MyFaultListener implements FaultListener{
public boolean faultOccurred(final Exception exception,final String description,final Message message) {
//return false to avoid warning of default CXF logging interceptor
return false;
}
}
但您无法从拦截器返回自定义响应或向客户端回复故障。
我发现实现所需行为的解决方法包括使用可以通过常规方法调用处理的自定义对象替换Response,例如exceptionMapper 见CXF/ JAX-RS : Return Custom response from interceptor
进入Interceptor.handleMessage
检查您需要的条件,并创建一个包含自定义状态和实体的Response
。在此之后,停止链
public class MyInterceptor extends AbstractPhaseInterceptor<Message> {
public MyInterceptor() {
super(Phase.POST_STREAM);
}
@Override
public void handleMessage(Message message) throws Fault {
if (message != null) {
//check the condition to raise the error
//build the custom Response replacing service call
Response response = Response
.status(Response.Status.BAD_REQUEST)
.entity("custom error")
.build();
message.getExchange().put(Response.class, response);
//abort interceptor chain in you want to stop processing or throw a Fault (catched by handleFault)
//message.getInterceptorChain().abort();
//throw new Fault (new MyException());
}
public void handleFault(Message messageParam) {
}
}
在创建JAXRS客户端时将ResponseExceptionMapper添加为提供程序
providers.add(new ResponseExceptionMapper<WebApplicationException>() {
@Override
public WebApplicationException fromResponse(Response r) {
return new WebApplicationException(r);
}
});
YourService proxy = JAXRSClientFactory.create(url, clazz,providers);
Client client = WebClient.client(proxy);
WebClient.getConfig(client).getInInterceptors().add(new MyInterceptor());
在此之后,如果执行拦截器检查,对proxy.yourService()
的调用将引发WebApplicationException
。你可以用理想的方式捕获它或重新抛出
try{
proxy.yourService();
}catch (WebApplicationException e){
}
希望这有帮助
答案 1 :(得分:0)
我完全同意以前的回答。我的实现如下:
@Component
public class ServiceFailureInterceptor extends AbstractPhaseInterceptor<Message> {
private static final Logger LOG = LoggerFactory.getLogger(ServiceFailureInterceptor.class);
public ServiceFailureInterceptor() {
super(PRE_STREAM);
}
@Override
public void handleMessage(Message message) {
if (message != null) {
int responseCode = (int) message.get(Message.RESPONSE_CODE);
LogicException logicException = ErrorMapper.HTTP_STATUS_CODE_MAPPER.get(responseCode);
InputStream is = b2stream(MapperUtils.json().toBytes(logicException));
// clear old message & exchange
Exchange exchange = message.getExchange();
for (Class<?> contentFormat : message.getContentFormats()) {
message.setContent(contentFormat, null);
}
resetOrigInterceptorChain(message);
resetFault(exchange);
message.setContent(InputStream.class, is);
Message outMessage = createOutMessage(exchange, is);
prepareMessage(outMessage);
prepareMessage(message);
}
}
private void prepareMessage(Message message) {
message.put(Message.REQUESTOR_ROLE, true);
message.put(HttpHeaders.CONTENT_TYPE, MediaType.APPLICATION_JSON);
}
private Message createOutMessage(Exchange exchange, InputStream logicException) {
Endpoint ep = exchange.get(Endpoint.class);
Message outMessage = ep != null ? ep.getBinding().createMessage() : new MessageImpl();
outMessage.setContent(InputStream.class, logicException);
exchange.setOutMessage(outMessage);
outMessage.setExchange(exchange);
return outMessage;
}
private void resetFault(Exchange exchange) {
exchange.put(Exception.class, null);
}
private void resetOrigInterceptorChain(Message message) {
InterceptorChain chain = message.getInterceptorChain();
if (chain != null) {
for (Interceptor<?> interceptor : chain) {
chain.remove(interceptor);
}
chain.reset();
}
}
}
手动设置此异常之后,我将进入ExceptionMapper实现,其中消耗了LogicException并且正在构建具有异常的响应。当通过WebClient声明为提供者时,我无法避免异常映射器,所以我决定使用它并稍后重新映射Exception。