My Oracle Support Banner

Unable to Deploy ESB Web Services: Failed to parse the WSDL (Doc ID 828393.1)

Last updated on SEPTEMBER 05, 2018

Applies to:

Oracle ESB - Version: 10.1.3.3 to 10.1.3.3.1 - Release: AS10gR3 to AS10gR3
Information in this document applies to any platform.
***Checked for relevance on 04-Aug-2011***

Symptoms

ESB 10.1.3.3.0/10.1.3.3.1. When attempting to deploy an ESB Process the following error occurs in log.xml file:

May 18, 2009 11:35:01 AM oracle.tip.esb.console.util.XMLGenerator buildOperationXML
SEVERE: Failed to parse the WSDL at esb:///ESB_Projects/Web Services_GetFares/GetFares.wsdl.
Ensure that the WSDL is well formed and syntactically valid
May 18, 2009 11:35:01 AM oracle.tip.esb.console.util.XMLGenerator addRequest
SEVERE: WSDL for the service operation :{GetFares} is invalid
May 18, 2009 11:35:01 AM oracle.tip.esb.console.util.XMLGenerator addReply
SEVERE: WSDL for the service operation :{GetFares} is invalid
09/05/18 11:35:01 oracle.tip.esb.console.exception.SchemaValidationException: The metadata XML
that was processed does not comply with the ESB Metadata XML Schema. Cause: Invalid text
'esb:///ESB_Projects/Web Services_GetFares/GetFares.wsdl' in element: 'wsdlURL'.
If you are manually editing the Import Files, ensure that the metadata is valid and well formed.
Otherwise, this is an Internal Error. Contact Oracle Support.

And the following is displayed in JDEV:
Exception= HttpClient executeMethod (PostMethod) returned status = 400


Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
  Symptoms
  Cause
  Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.