此内容没有您所选择的语言版本。

Chapter 30. Generic Fault Handling


Abstract

The JAX-WS specification defines two types of faults. One is a generic JAX-WS runtime exception. The other is a protocol specific class of exceptions that is thrown during message processing.

30.1. Runtime Faults

Overview

Most of the JAX-WS APIs throw a generic javax.xml.ws.WebServiceException exception.

APIs that throw WebServiceException

Table 30.1, “APIs that Throw WebServiceException lists some of the JAX-WS APIs that can throw the generic WebServiceException exception.
Table 30.1. APIs that Throw WebServiceException
APIReason
Binding.setHandlerChain()There is an error in the handler chain configuration.
BindingProvider.getEndpointReference()The specified class is not assigned from a W3CEndpointReference.
Dispatch.invoke()There is an error in the Dispatch instance's configuration or an error occurred while communicating with the service.
Dispatch.invokeAsync()There is an error in the Dispatch instance's configuration.
Dispatch.invokeOneWay()There is an error in the Dispatch instance's configuration or an error occurred while communicating with the service.
LogicalMessage.getPayload()An error occurred when using a supplied JAXBContext to unmarshall the payload. The cause field of the WebServiceException contains the original JAXBException.
LogicalMessage.setPayload()An error occurred when setting the payload of the message. If the exception is thrown when using a JAXBContext, the cause field of the WebServiceException contains the original JAXBException.
WebServiceContext.getEndpointReference()The specified class is not assigned from a W3CEndpointReference.
Red Hat logoGithubRedditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

© 2024 Red Hat, Inc.