WLS 10.3: <WS data binding error>OperationFailedException is not understood because there is no type mapping for exception class...

(Doc ID 1129824.1)

Last updated on APRIL 26, 2018

Applies to:

Oracle Weblogic Server - Version: 10.3 and later   [Release: and later ]
Information in this document applies to any platform.


When using Webservices that use custom exceptions it was found that the webservice deploys successfully but while starting the service the below error is seen in the standard out of the server.
 <WS data binding error>com.xxx.iconfig.components.exception.OperationFailedException is not understood because there is no type mapping for exception class
<WS data binding error>While processing <exception-mapping> for wsdlMessageName='{com.xxx.iconfig}OperationFailedException', wsdlMessagePartElement='{com.xxx.iconfig.components.exception}string'. Unable to find a BindingType in the binding file for javaTypeName ='com.xxx.iconfig.components.exception.OperationFailedException', xmlTypeName='e=string@com.xxx.iconfig.components.exception'. The cause of this error is likely because an <exception-mapping> specified for {com.xxx.iconfig}OperationFailedExceptionrequires that a <java-xml-type-mapping> exist for java




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms