BPEL Web Service Exceptions ORABPEL 08000 - 08033

BPEL Web Service Exceptions ORABPEL 08000 - 08033
Web Service Exceptions 08000 - 08033

<>Parameters: 0: SOAPHeaderElement's QName 1: operation Name 2: SOAPException message
ORABPEL-08000
severity: 10
type: error
name: Failed to set soap header
description: Failed to set SOAPHeaderElement \"{0}\" when invoking operation \"{1}\". Reason is \"{2}\".

ORABPEL-08001
severity: 10
type: error
name: Failed to set soap header
description: Failed to set soap header \"{0}\" for operation \"{1}\", because \"{2}\".

ORABPEL-08002
severity: 10
type: error
name: Failed to read wsdl
description: Error happened when reading wsdl at \"{0}\", because \"{1}\".
fix: Make sure wsdl exists at that URL and is valid.

ORABPEL-08003
severity: 10
type: error
name: Failed to read wsdl
description: Failed to read wsdl at \"{0}\", because \"{1}\".
fix: Make sure wsdl is valid. You may need to start the OraBPEL server, or make sure the related bpel process is deployed correctly.

ORABPEL-08004
severity: 10
type: error
name: WSDL type map not registered
description: Cannot find registered typeMap for WSDL definition \"{0}\".
fix: TypeMapping should be registered before it can be used by the WebService layer. This is a system exception, please report to admin.

ORABPEL-08005
severity: 10
type: error
name: Failed to get type for wrapper
description: Failed to get type for elment \"{1}\" of wrapper type \"{0}\".
fix: Please verify that element \"{1}\" of wrapper type \"{0}\" is defined with the valid XML type.

ORABPEL-08006
severity: 10
type: error
name: Failed to read WSDL
description: Failed to read wsdl at \"{0}\" because \"{1}\".
fix: Please verify that WSDL at location \"{0}\" is valid.

<>{ "exception.08007 .fix", "Please verify that there is a port that implements portType \"{0}\" in the WSDL service \"{1}\"." },
ORABPEL-08007
severity: 10
type: error
name: Failed get wsdl port
description: Failed to get WSDL port that implements portType \"{0}\" from WSDL service \"{1} \".

ORABPEL-08008
severity: 10
type: error
name: Failed get wsdl service definition
description: Failed to get WSDL service \"{0}\" from WSDL definition \"{1}\".
fix: Please verify that WSDL service \"{0}\" is correctly defined in the WSDL file.

ORABPEL-08009
severity: 10
type: error
name: Failed get wsdl service definition
description: Failed to get a WSDL service that support the portType \"{0}\" in WSDL definition \"{1}\".
fix: Please verify that WSDL portType \"{0}\" is supported by a service in WSDL file.

ORABPEL-08010
severity: 10
type: error
name: Failed get operation definition
description: Failed to get the WSDL operation definition of \"{0}\" in portType \"{1}\".
fix: Please verify that operation \"{0}\" is defined in portType \"{1}\".

ORABPEL-08011
severity: 10
type: error
name: Cannot find parterRole
description: Failed to get partnerRole \"{0}\" of partnerLink \"{1}\" in partnerLinkType \"{2} \".
fix: Please verify that partnerRole \"{0}\" is defined in partnerLinkType \"{2}\".

ORABPEL-08012
severity: 10
type: error
name: Cannot find parterRole
description: Failed to resolve the java class for type \"{2}\" of part \"{1}\" of messageType \"{0}\".
fix: Please make sure the XML type \"{2}\" is defined in WSDL or XSD.

ORABPEL-08013
severity: 10
type: error
name: Cannot find partnerLinkType
description: PartnerLinkType \"{1}\" of partnerLink \"{0}\" is not found in either partner WSDL at \"{2}\" and process WSDL at \"{3}\".
fix: Please make sure the partnerLinkType is defined in the WSDL.

ORABPEL-08014
severity: 10
type: error
name: No such operation
description: Cannot find operation.
fix: The WSDL might have been changed and you might need to recompile your process.

ORABPEL-08015
severity: 10
type: error
name: No such operation
description: Cannot find operation \"{0}\" of portType \"{1}\" in WSDL at \"{2}\".
fix: The WSDL at \"{2}\" might have been changed and you might need to recompile and deploy the caller process.

ORABPEL-08016
severity: 10
type: error
name: Cannot find partnerLinkType 2
description: PartnerLinkType \"{0}\" is not found in WSDL at \"{1}\".
fix: Please make sure the partnerLinkType is defined in the WSDL.

ORABPEL-08017
severity: 10
type: error
name: Cannot find partnerLink
description: PartnerLink \"{0}\" has not been defined in the process \"{1}\" (revision \"{2} \").

ORABPEL-08018
severity: 10
type: error
name: Cannot send jms message
description: The process \"{0}\" (revision \"{1}\") was unable to send a message to jms partner \"{2}\"; the exception is: {3}
fix: Please check that the messaging service for the application server has been configured properly.

ORABPEL-08019
severity: 10
type: error
name: Cannot create subscriber
description: The process \"{0}\" (revision \"{1}\") was unable to create a subscriber for jms partner \"{2}\"; the exception is: {3}

ORABPEL-08020
severity: 10
type: error
name: Cannot shutdown subscriber
description: The process \"{0}\" (revision \"{1}\") was unable to close the subscriber for jms partner \"{2}\"; the exception is: {3}
fix: Please check the MOM Server for the connector has been running properly or not.

ORABPEL-08021
severity: 10
type: error
name: Cannot find partner wsdl
description: parnterLink \"{0}\" is not found in process \"{1}\" (revision \"{2}\")
fix: Please check the deployment descriptor of the process to find the correct partnerLink name

ORABPEL-08022
severity: 10
type: error
name: Cannot find binding operation
description: in WSDL located at \"{0}\", cannot find a binding operation of \"{2}\", portType \"{1}\"
fix: Please make sure the WSDL is valid

ORABPEL-08032
severity: 10
type: error
name: Failed get wsdl portType definition
description: Failed to get WSDL portType \"{0}\" from WSDL definition \"{1}\".
fix: Please verify that WSDL portType \"{0}\" is correctly defined in the WSDL file.

ORABPEL-08033
severity: 10
type: error
name: EJB Transaction Error
description: EJB exception happened while invoking the partner
fix: Please verify partner service.