ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anup Chandran <anup.chand...@3ds.com>
Subject Binding defines non-element document literal part(s)
Date Wed, 08 Aug 2007 21:47:43 GMT

My WSDL is :

<?xml version="1.0"?>
<definitions name="ECRProcess"
	targetNamespace="http://eclipse.org/bpel/sample"
	xmlns:tns="http://eclipse.org/bpel/sample"
	xmlns:plnk="http://schemas.xmlsoap.org/ws/2004/03/partner-link/"
	xmlns="http://schemas.xmlsoap.org/wsdl/"
	xmlns:p="http://www.w3.org/2001/XMLSchema"
	xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">

	<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
		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://eclipse.org/bpel/sample"
			xmlns="http://www.w3.org/2001/XMLSchema">

			<element name="ECRProcessResponse" type="string" />

			<complexType name="ECRRequestMessage">
				<sequence>
					<element name="username" type="string"></element>

					<element name="password" type="string"></element>

					<element name="type" type="string"></element>

					<element name="name" type="string"></element>

					<element name="revision" type="string"></element>

					<element name="policy" type="string"></element>

				</sequence>
			</complexType>
		</schema>
	</types>

	<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
		MESSAGE TYPE DEFINITION - Definition of the message types used as 
		part of the port type defintions
		~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
	<message name="ECRProcessRequestMessage">
		<part name="payload" type="tns:ECRRequestMessage" />
	</message>

	<message name="ECRProcessResponseMessage">
		<part name="payload" element="tns:ECRProcessResponse" />
	</message>


	<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
		PORT TYPE DEFINITION - A port type groups a set of operations into
		a logical service unit.
		~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
	<!-- portType implemented by the ECRProcess BPEL process -->
	<portType name="ECRProcess">
		<operation name="receiveIssue">
			<input message="tns:ECRProcessRequestMessage"
				name="RequestMessage" />
		</operation>
	</portType>

	<!-- portType implemented by the requester of ECRProcess BPEL process 
		for asynchronous callback purposes
	-->
	<portType name="ECRProcessCallback">
		<operation name="onResult">
			<input message="tns:ECRProcessResponseMessage" />
		</operation>
	</portType>


	<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
		PARTNER LINK TYPE DEFINITION
		the ECRProcess partnerLinkType binds the provider and
		requester portType into an asynchronous conversation.
		~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
	<plnk:partnerLinkType name="ECRProcess">
		<plnk:role name="ECRProcessProvider" portType="tns:ECRProcess" />
		<plnk:role name="ECRProcessRequester"
			portType="tns:ECRProcessCallback" />
	</plnk:partnerLinkType>


	<binding name="ECRProcessSoapBinding" type="tns:ECRProcess">
		<soap:binding style="document"
			transport="http://schemas.xmlsoap.org/soap/http" />
		<operation name="receiveIssue">
			<soap:operation soapAction="" style="document" />
			<input>
				<soap:body
					namespace="http://sample.bpel.org/bpel/sample" use="literal" />
			</input>
		</operation>
	</binding>

	<binding name="ECRProcessResponseSoapBinding"
		type="tns:ECRProcessCallback">
		<soap:binding style="document"
			transport="http://schemas.xmlsoap.org/soap/http" />
		<operation name="onResult">
			<soap:operation soapAction="" style="document" />
			<input>
				<soap:body
					namespace="http://sample.bpel.org/bpel/sample" use="literal" />
			</input>
		</operation>

	</binding>


	<service name="ECRProcessInvokeService">
		<documentation>
			Receives request for the invocation of ECR
		</documentation>
		<port name="ECRProcessPort"
			binding="tns:ECRProcessSoapBinding">
			<soap:address
				location="http://localhost:8080/ode/processes/ecrProcess" />
		</port>
	</service>

	<service name="ECRProcessResponderService">
		<documentation>Return message</documentation>
		<port name="ECRProcessCallbackPort"
			binding="tns:ECRProcessResponseSoapBinding">
			<soap:address
				location="http://localhost:8080/ode/processes/ecrProcessResponse" />
		</port>
	</service>


</definitions>



My testRequest.SOAP is :

<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
  <!-- test soap message -->
  <SOAP-ENV:Body>
      <ns1:receiveIssue xmlns:ns1="http://sample.bpel.org/bpel/sample"> 
      <ns1:username xmlns:ns1="http://sample.bpel.org/bpel/sample">Test
Everything </ns1:username>
      <ns1:password xmlns:ns1="http://sample.bpel.org/bpel/sample">1234
</ns1:password>
      <ns1:type xmlns:ns1="http://sample.bpel.org/bpel/sample">ECR
</ns1:type>
      <ns1:name xmlns:ns1="http://sample.bpel.org/bpel/sample">ECR01001
</ns1:name>
      <ns1:revision
xmlns:ns1="http://sample.bpel.org/bpel/sample">-</ns1:revision>
      <ns1:policy xmlns:ns1="http://sample.bpel.org/bpel/sample">ECR
(Standard)</ns1:policy>
      </ns1:receiveIssue>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>


The error is :

Input: name=RequestMessage
Message: name={http://eclipse.org/bpel/sample}ECRProcessRequestMessage
Part: name=payload
typeName={http://eclipse.org/bpel/sample}ECRRequestMessage,Operation:
name=recei
veIssue
style=ONE_WAY,0
Input: name=RequestMessage
Message: name={http://eclipse.org/bpel/sample}ECRProcessRequestMessage
Part: name=payload
typeName={http://eclipse.org/bpel/sample}ECRRequestMessage)
17:32:21,178 DEBUG [MessageExchangeImpl]
Mex[hqejbhcnphr2hqohqgam6t].setPortOp(P
ortType: name={http://eclipse.org/bpel/sample}ECRProcess
Operation: name=receiveIssue
style=ONE_WAY,0
Input: name=RequestMessage
Message: name={http://eclipse.org/bpel/sample}ECRProcessRequestMessage
Part: name=payload
typeName={http://eclipse.org/bpel/sample}ECRRequestMessage,Operation:
name=recei
veIssue
style=ONE_WAY,0
Input: name=RequestMessage
Message: name={http://eclipse.org/bpel/sample}ECRProcessRequestMessage
Part: name=payload
typeName={http://eclipse.org/bpel/sample}ECRRequestMessage)
DEBUG - GeronimoLog.debug(66) | ODE routed to operation Operation:
name=receiveI
ssue
style=ONE_WAY,0
Input: name=RequestMessage
Message: name={http://eclipse.org/bpel/sample}ECRProcessRequestMessage
Part: name=payload
typeName={http://eclipse.org/bpel/sample}ECRRequestMessage from service
{http://
eclipse.org/bpel/sample}ECRProcessInvokeService
17:32:21,178 DEBUG [ODEService] ODE routed to operation Operation:
name=receiveI
ssue
style=ONE_WAY,0
Input: name=RequestMessage
Message: name={http://eclipse.org/bpel/sample}ECRProcessRequestMessage
Part: name=payload
typeName={http://eclipse.org/bpel/sample}ECRRequestMessage from service
{http://
eclipse.org/bpel/sample}ECRProcessInvokeService
ERROR - GeronimoLog.error(108) | Exception occured while invoking ODE
org.apache.ode.axis2.OdeFault: Binding defines non-element document literal
part
(s); nested exception is:
        java.lang.IllegalArgumentException: Binding defines non-element
document
 literal part(s)
        at
org.apache.ode.axis2.util.SoapMessageConverter.extractSoapBodyParts(S
oapMessageConverter.java:379)
        at
org.apache.ode.axis2.util.SoapMessageConverter.parseSoapRequest(SoapM
essageConverter.java:292)

What is wrong with my SOAP request?

Thanks
Anup
-- 
View this message in context: http://www.nabble.com/Binding-defines-non-element-document-literal-part%28s%29-tf4239227.html#a12062295
Sent from the Apache Ode User mailing list archive at Nabble.com.


Mime
View raw message