I am desperately trying to run a simple BPEL Process by invoking a simple WebService. But I always the response "xmlns:axis2ns4="XXX://docs.oasis-open.org/wsbpel/2.0/process/executable">axis2ns4:selectionFailure</faultstring>" and I did not get any solution based on a lot of searches within the net.
(Unfortunately I had to replace http via XXX ;((
<!-- ================================================================= -->
<!-- PARTNERLINKS -->
<!-- List of services participating in this BPEL process -->
<!-- ================================================================= -->
<bpel:partnerLinks>
<!-- The 'client' role represents the requester of this service. -->
<bpel:partnerLink name="client"
partnerLinkType="tns:Test"
myRole="TestProvider"
/>
<!-- ================================================================= -->
<!-- VARIABLES -->
<!-- List of messages and XML documents used within this BPEL process -->
<!-- ================================================================= -->
<bpel:variables>
<!-- Reference to the message passed as input during initiation -->
<bpel:variable name="input"
messageType="tns:TestRequestMessage"/>
<!--
Reference to the message that will be returned to the requester
-->
<bpel:variable name="output"
messageType="tns:TestResponseMessage"/>
<bpel:variable name="file" type="ns1:string">
<bpel:from>
<bpel:literal xml:space="preserve"><![CDATA[]]></bpel:literal>
</bpel:from>
</bpel:variable>
<bpel:variable name="transactionID" type="ns1:long">
<bpel:from>
<![CDATA[111]]>
</bpel:from>
</bpel:variable>
<bpel:variable name="VirusLinkResponse" messageType="ns:scanFileResponse">
<bpel:from>
<bpel:literal xml:space="preserve"><tns:scanFileResponse xmlns:tns="XXX://virusInspectors.sipimport.feu.de/" xmlns:xsi="XXX://www.w3.org/2001/XMLSchema-instance">
<viruscheck>true</viruscheck>
</tns:scanFileResponse>
</bpel:literal>
</bpel:from>
</bpel:variable>
<bpel:variable name="VirusLinkRequest" messageType="ns:scanFile">
<bpel:from>
<bpel:literal xml:space="preserve"><tns:scanFile xmlns:tns="XXX://virusInspectors.sipimport.feu.de/" xmlns:xsi="XXX://www.w3.org/2001/XMLSchema-instance">
<file_path>xxx</file_path>
<transactionIdWEB>111</transactionIdWEB>
</tns:scanFile>
</bpel:literal>
</bpel:from>
</bpel:variable>
</bpel:variables>
<!-- ================================================================= -->
<!-- ORCHESTRATION LOGIC -->
<!-- Set of activities coordinating the flow of messages across the -->
<!-- services integrated within this business process -->
<!-- ================================================================= -->
<bpel:sequence name="main">
<!-- Receive input from requester.
Note: This maps to operation defined in Test.wsdl
--><bpel:receive name="receiveInput" partnerLink="client" portType="tns:Test" operation="process" variable="input" createInstance="yes" />
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TYPE DEFINITION - List of types participating in this BPEL process
The BPEL Designer will generate default request and response types
but you can define or import any XML Schema type and use them as part
of the message types.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<plnk:partnerLinkType name="VirusPLT">
<plnk:role name="VirusRole" portType="wsdl:VirusScanner"/>
</plnk:partnerLinkType>
<import location="ImportVirusScanner.wsdl" namespace="XXX://virusInspectors.sipimport.feu.de/"/>
<types>
<schema xmlns="XXX://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="XXX://localhost.test">
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MESSAGE TYPE DEFINITION - Definition of the message types used as
part of the port type defintions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<message name="TestRequestMessage">
<part element="tns:TestRequest" name="payload"/>
</message>
<message name="TestResponseMessage">
<part element="tns:TestResponse" name="payload"/>
</message>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PORT TYPE DEFINITION - A port type groups a set of operations into
a logical service unit.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<!-- portType implemented by the Test BPEL process -->
<portType name="Test">
<operation name="process">
<input message="tns:TestRequestMessage"/>
<output message="tns:TestResponseMessage"/>
</operation>
</portType>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PARTNER LINK TYPE DEFINITION
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<plnk:partnerLinkType name="Test">
<plnk:role name="TestProvider" portType="tns:Test"/>
</plnk:partnerLinkType>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BINDING DEFINITION - Defines the message format and protocol details
for a web service.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<binding name="TestBinding" type="tns:Test">
<soap:binding style="document" transport="XXX://schemas.xmlsoap.org/soap/XXX"/>
<operation name="process">
<soap:operation soapAction="XXX://localhost.test/process"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SERVICE DEFINITION - A service groups a set of ports into
a service unit.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<service name="TestService">
<port binding="tns:TestBinding" name="TestPort">
<soap:address location="XXX://localhost:8080/ode/processes/Test"/>
</port>
</service>
</definitions>
and the second one:
<?xml version="1.0" encoding="UTF-8"?><!-- Published by JAX-WS RI at XXX://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.4-b01-. --><!-- Generated by JAX-WS RI at XXX://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.4-b01-. --><definitions xmlns:soap="XXX://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="XXX://virusInspectors.sipimport.feu.de/" xmlns:xsd="XXX://www.w3.org/2001/XMLSchema" xmlns="XXX://schemas.xmlsoap.org/wsdl/" targetNamespace="XXX://virusInspectors.sipimport.feu.de/" name="VirusScannerService">
<types>
<xsd:schema>
<xsd:import namespace="XXX://virusInspectors.sipimport.feu.de/" schemaLocation="ImportVirusScanner.xsd"></xsd:import>
</xsd:schema>
</types>
<message name="scanFile">
<part name="parameters" element="tns:scanFile"></part>
</message>
<message name="scanFileResponse">
<part name="parameters" element="tns:scanFileResponse"></part>
</message>
<portType name="VirusScanner">
<operation name="scanFile">
<input message="tns:scanFile"></input>
<output message="tns:scanFileResponse"></output>
</operation>
</portType>
<binding name="VirusScannerBinding" type="tns:VirusScanner">
<soap:binding transport="XXX://schemas.xmlsoap.org/soap/XXX" style="document"></soap:binding>
<operation name="scanFile">
<soap:operation soapAction=""></soap:operation>
<input>
<soap:body use="literal"></soap:body>
</input>
<output>
<soap:body use="literal"></soap:body>
</output>
</operation>
</binding>
<service name="VirusScannerService">
<port name="VirusScanner" binding="tns:VirusScannerBinding">
<soap:address location="XXX://localhost:8080/Import-1.7.3-SNAPSHOT/ImportVirusScanner"></soap:address>
</port>
</service>
</definitions>
It would be really, really great if you could help me!!!
Robert Brodt Messages: 343 Registered: August 2010 Location: Colorado Springs, CO
Senior Member
The selectionFault usually indicates that a complex variable was not initialized in an <assign> (not the case here, as far as I can tell) but have a look here:
Also, I did not see the ImportVirusScanner.xsd that is imported in your second wsdl, so I tried replacing the <import> with just simple "xs:string" types for the missing elements, like so: