Error ORABPEL-10903

Question

Hi,
I am using eclipse version 0.9.13 and working through the creditflow example. I am getting the following error message on Windows 2000 using java 1.4
Buildfile: C:\Documents and Settings\dkunzman\workspace\CreditFlow\build.xml
main:
[bpelc] BPEL validation failed.
[bpelc] BPEL source validation failed, the errors are:
[bpelc]
[bpelc] [Error ORABPEL-10903]: failed to read wsdl
[bpelc] [Description]: in "bpel.xml", Failed to read wsdl.
[bpelc] Error happened when reading wsdl at "C:\Documents%20and%20Settings\dkunzman\workspace\CreditFlow\CreditFlow.wsdl", because "WSDLException: faultCode=INVALID_WSDL: Invalid XML in document at: file:/C:/Documents%20and%20Settings/dkunzman/workspace/CreditFlow/CreditFlow.wsdl: can't declare any more prefixes in this context".
[bpelc] Make sure wsdl exists at that URL and is valid.
[bpelc] .
[bpelc] [Potential fix]: If your site has a proxy server, then you may need to configure your BPEL Server, designer and browser with your proxy server configuration settings (see tech note on http://otn.oracle.com/bpel for instructions).
[bpelc] .
BUILD FAILED
C:\Documents and Settings\dkunzman\workspace\CreditFlow\build.xml:28: Validation error
Total time: 2 seconds
The wsdl exists but I do not know how to validate using free tools. Any idea? Also, I have checked it for well formedness adn that is ok.
Any ideas?
Doug

Answer 1

This is the wsdl
<?xml version="1.0"?>
<definitions name="CreditFlow"
targetNamespace="http://tutorial.oracle.com"
xmlns:tns="http://tutorial.oracle.com"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TYPE DEFINITION - List of services participating in this BPEL process
The default output of the BPEL designer uses strings as input and
output to the BPEL Process. But you can define or import any XML
Schema type and us them as part of the message types.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<types>
<schema attributeFormDefault="unqualified"
elementFormDefault="qualified"
targetNamespace="http://tutorial.oracle.com"
xmlns="http://www.w3.org/2001/XMLSchema"
>
<element name="CreditFlowRequest">
<complexType>
<sequence>
<element name="ssn" type="string" />
</sequence>
</complexType>
</element>
<element name="CreditFlowResponse">
<complexType>
<sequence>
<element name="creditRating" type="int"/>
</sequence>
</complexType>
</element>
</schema>
</types>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MESSAGE TYPE DEFINITION - Definition of the message types used as
part of the port type defintions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<message name="CreditFlowRequestMessage">
<part name="payload" element="tns:CreditFlowRequest"/>
</message>
<message name="CreditFlowResponseMessage">
<part name="payload" element="tns:CreditFlowResponse"/>
</message>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PORT TYPE DEFINITION - A port type groups a set of operations into
a logical service unit.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<!-- portType implemented by the CreditFlow BPEL process -->
<portType name="CreditFlow">
<operation name="initiate">
<input message="tns:CreditFlowRequestMessage"/>
</operation>
</portType>
<!-- portType implemented by the requester of CreditFlow BPEL process
for asynchronous callback purposes
-->
<portType name="CreditFlowCallback">
<operation name="onResult">
<input message="tns:CreditFlowResponseMessage"/>
</operation>
</portType>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PARTNER LINK TYPE DEFINITION
the CreditFlow partnerLinkType binds the provider and
requester portType into an asynchronous conversation.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<plnk:partnerLinkType name="CreditFlow">
<plnk:role name="CreditFlowProvider">
<plnk:portType name="tns:CreditFlow"/>
</plnk:role>
<plnk:role name="CreditFlowRequester">
<plnk:portType name="tns:CreditFlowCallback"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>