You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Anup Chandran <an...@3ds.com> on 2007/08/08 23:47:43 UTC

Binding defines non-element document literal part(s)

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.


Re: Binding defines non-element document literal part(s)

Posted by Alex Boisvert <bo...@intalio.com>.
On 8/9/07, Anup Chandran <an...@3ds.com> wrote:
>
> This exception is an issue in Axis2 1.1 when
> generating a fault with SOAP 1.1.  I would recommend trying out Ode
> 1.1RC1to see what you get with Axis2
> 1.3, or using the patched axis2-kernel-intalio-1.1.1b (discussed
> previously
> on thist list).
>
>
> Alex. Replaced axis2-kernel-1.1.1.jar in
> C:\apache-tomcat-5.5.20\webapps\ode\WEB-INF\lib with
> axis2-kernel-intalio-1.1.1b.jar.
>

My ODE is apache-ode-war-1.0-incubating.
>
> Same error trace :(



You also need to remove axis2.jar since it duplicates classes from
axis2-kernel.


Is there an official distribution of Ode 1.1RC1? and does it have axis2 1.3?


http://people.apache.org/~mriou/ode-1.1-RC1/

it contains axis2-1.3-RC3

alex

Re: Binding defines non-element document literal part(s)

Posted by Anup Chandran <an...@3ds.com>.

This exception is an issue in Axis2 1.1 when
generating a fault with SOAP 1.1.  I would recommend trying out Ode
1.1RC1to see what you get with Axis2
1.3, or using the patched axis2-kernel-intalio-1.1.1b (discussed previously
on thist list).


Alex. Replaced axis2-kernel-1.1.1.jar in
C:\apache-tomcat-5.5.20\webapps\ode\WEB-INF\lib with
axis2-kernel-intalio-1.1.1b.jar.

I got the intalio jar from
http://www.intalio.org/public/maven2/org/apache/axis2/axis2-kernel-intalio/1.1.1b/

My ODE is apache-ode-war-1.0-incubating.

Same error trace :(

Is there an official distribution of Ode 1.1RC1? and does it have axis2 1.3?


Alex Boisvert wrote:
> 
> On 8/9/07, Anup Chandran <an...@3ds.com> wrote:
>>
>> The error is :
>>
>> Aug 9, 2007 10:01:33 AM org.apache.catalina.storeconfig.StoreLoader load
>> INFO: Find registry server-registry.xml at classpath resource
>> Aug 9, 2007 10:01:33 AM org.apache.catalina.startup.Catalina start
>> INFO: Server startup in 24284 ms
>> ERROR - GeronimoLog.error(108) | Servlet.service() for servlet
>> AxisServlet
>> threw exception
>> java.lang.NullPointerException  at
>>
>> org.apache.axis2.engine.AxisEngine.extractFaultInformationFromMessageContext
>> (AxisEngine.java:353)
> 
> 
> 
> Hi Anup,
> 
> Your request looks fine now and I suspect your process is now executing
> but
> somehow triggers a fault.   This exception is an issue in Axis2 1.1 when
> generating a fault with SOAP 1.1.  I would recommend trying out Ode
> 1.1RC1to see what you get with Axis2
> 1.3, or using the patched axis2-kernel-intalio-1.1.1b (discussed
> previously
> on thist list).
> 
> Shouldn't the first element in the request be the method/operation name?
>> followed by elements in the message?
> 
> 
> 
> Not if using a Document-Literal binding.   The operation name only appears
> in the message when using RPC binding.
> 
> BTW, a good tool for generating SOAP messages and inspecting/validating
> WSDLs is http://www.soapui.org/
> 
> alex
> 
> 

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


Re: Binding defines non-element document literal part(s)

Posted by Alex Boisvert <bo...@intalio.com>.
On 8/9/07, Anup Chandran <an...@3ds.com> wrote:
>
> The error is :
>
> Aug 9, 2007 10:01:33 AM org.apache.catalina.storeconfig.StoreLoader load
> INFO: Find registry server-registry.xml at classpath resource
> Aug 9, 2007 10:01:33 AM org.apache.catalina.startup.Catalina start
> INFO: Server startup in 24284 ms
> ERROR - GeronimoLog.error(108) | Servlet.service() for servlet AxisServlet
> threw exception
> java.lang.NullPointerException  at
>
> org.apache.axis2.engine.AxisEngine.extractFaultInformationFromMessageContext
> (AxisEngine.java:353)



Hi Anup,

Your request looks fine now and I suspect your process is now executing but
somehow triggers a fault.   This exception is an issue in Axis2 1.1 when
generating a fault with SOAP 1.1.  I would recommend trying out Ode
1.1RC1to see what you get with Axis2
1.3, or using the patched axis2-kernel-intalio-1.1.1b (discussed previously
on thist list).

Shouldn't the first element in the request be the method/operation name?
> followed by elements in the message?



Not if using a Document-Literal binding.   The operation name only appears
in the message when using RPC binding.

BTW, a good tool for generating SOAP messages and inspecting/validating
WSDLs is http://www.soapui.org/

alex

Re: Binding defines non-element document literal part(s)

Posted by Anup Chandran <an...@3ds.com>.
Here is the wsdl snippet:

	<types>
		<schema attributeFormDefault="unqualified"
			elementFormDefault="qualified"
			targetNamespace="http://eclipse.org/bpel/sample"
			xmlns="http://www.w3.org/2001/XMLSchema">

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

			<element name="ECRRequestMessage">
			<complexType>
			<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>
			</element>
		</schema>
	</types>


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

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


The test request is :

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


The error is :

Aug 9, 2007 10:01:33 AM org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
Aug 9, 2007 10:01:33 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 24284 ms
ERROR - GeronimoLog.error(108) | Servlet.service() for servlet AxisServlet
threw
 exception
java.lang.NullPointerException
        at
org.apache.axis2.engine.AxisEngine.extractFaultInformationFromMessage
Context(AxisEngine.java:353)
        at
org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngi
ne.java:249)
        at
org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.j
ava:317)
        at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:2
77)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
        at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
        at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
        at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:213)
        at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:178)
        at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:126)
        at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:105)
        at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:107)
        at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:148)
        at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:869)
        at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p
rocessConnection(Http11BaseProtocol.java:664)
        at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:527)
        at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
lowerWorkerThread.java:80)
        at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:684)
        at java.lang.Thread.run(Thread.java:595)
10:02:06,806 ERROR [[AxisServlet]] Servlet.service() for servlet AxisServlet
thr
ew exception
java.lang.NullPointerException
        at
org.apache.axis2.engine.AxisEngine.extractFaultInformationFromMessage
Context(AxisEngine.java:353)
        at
org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngi
ne.java:249)
        at
org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.j
ava:317)
        at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:2
77)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
        at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
        at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
        at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:213)
        at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:178)
        at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:126)
        at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:105)
        at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:107)
        at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:148)
        at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:869)
        at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p
rocessConnection(Http11BaseProtocol.java:664)
        at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo
int.java:527)
        at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol
lowerWorkerThread.java:80)
        at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP



Alex im not sure about the testrequest.soap.

Shouldn't the first element in the request be the method/operation name?
followed by elements in the message?

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

Result:


i tried that too....

ERROR - GeronimoLog.error(108) | Servlet.service() for servlet AxisServlet
threw
 exception
java.lang.NullPointerException
        at
org.apache.axis2.engine.AxisEngine.extractFaultInformationFromMessage
Context(AxisEngine.java:353)
        at
org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngi
ne.java:249)
        at
org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.j
ava:317)
        at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:2
77)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
        at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
        at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)



Alex Boisvert wrote:
> 
> On 8/8/07, Anup Chandran <an...@3ds.com> wrote:
>>
>>
>> Alex thanks for the quick response....
>>
>> I changed the wsdl to define the part as element.
>>
>> WSDL modified to:
>>
>>         <message name="ECRProcessRequestMessage">
>>                 <part name="payload" element="tns:ECRRequestMessage" />
>>         </message>
> 
> 
> 
> Did you also change tns:ECRRequestMessage to be an element (of
> complexType)?
> 
> If so, your SOAP request should be:
> 
> <tns:ECRRequestMessage>
>     <tns:receiveIssue> ... </tns:receiveIssue>
>     <tns:username> ...  </tns:username>
>     ....
>     ....
> </tns:ECRRequestMessage>
> 
> alex
> 
> 

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


Re: Binding defines non-element document literal part(s)

Posted by Alex Boisvert <bo...@intalio.com>.
On 8/8/07, Anup Chandran <an...@3ds.com> wrote:
>
>
> Alex thanks for the quick response....
>
> I changed the wsdl to define the part as element.
>
> WSDL modified to:
>
>         <message name="ECRProcessRequestMessage">
>                 <part name="payload" element="tns:ECRRequestMessage" />
>         </message>



Did you also change tns:ECRRequestMessage to be an element (of complexType)?

If so, your SOAP request should be:

<tns:ECRRequestMessage>
    <tns:receiveIssue> ... </tns:receiveIssue>
    <tns:username> ...  </tns:username>
    ....
    ....
</tns:ECRRequestMessage>

alex

Re: Binding defines non-element document literal part(s)

Posted by Anup Chandran <an...@3ds.com>.
Alex thanks for the quick response....

I changed the wsdl to define the part as element.

WSDL modified to:

	<message name="ECRProcessRequestMessage">
		<part name="payload" element="tns:ECRRequestMessage" />
	</message>


And my soapRequest 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 now is :

Input: name=RequestMessage
Message: name={http://eclipse.org/bpel/sample}ECRProcessRequestMessage
Part: name=payload
elementName={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: Unexpected element in SOAP body: message
{http://
sample.bpel.org/bpel/sample}receiveIssue element
{http://eclipse.org/bpel/sample
}ECRRequestMessage.; nested exception is:
        java.lang.IllegalArgumentException: Unexpected element in SOAP body:
mes
sage {http://sample.bpel.org/bpel/sample}receiveIssue element
{http://eclipse.or
g/bpel/sample}ECRRequestMessage.

So basic question that i had if my request message is of complex type as
follows

<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>


then should my message type definition be an "element" instead of "type"???

Or should i use some other binding.... sorry if the question sounds naive...

Regards
Anup 


Alex Boisvert wrote:
> 
> Hi Anup,
> 
> On 8/8/07, Anup Chandran <an...@3ds.com> wrote:
>>
>>                         <complexType name="ECRRequestMessage">
>>                         </complexType>
>>                 </schema>
>>         </types>
>>
>>         <message name="ECRProcessRequestMessage">
>>                 <part name="payload" type="tns:ECRRequestMessage" />
>>         </message>
> 
> 
> <snip>
> 
> 
>         java.lang.IllegalArgumentException: Binding defines non-element
>> document literal part(s)
> 
> 
> 
> A document-literal binding requires that your part (in this case
> ECRProcessRequestMessage's payload)  be an element, not a type.
> 
> alex
> 
> 

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


Re: Binding defines non-element document literal part(s)

Posted by Alex Boisvert <bo...@intalio.com>.
Hi Anup,

On 8/8/07, Anup Chandran <an...@3ds.com> wrote:
>
>                         <complexType name="ECRRequestMessage">
>                         </complexType>
>                 </schema>
>         </types>
>
>         <message name="ECRProcessRequestMessage">
>                 <part name="payload" type="tns:ECRRequestMessage" />
>         </message>


<snip>


        java.lang.IllegalArgumentException: Binding defines non-element
> document literal part(s)



A document-literal binding requires that your part (in this case
ECRProcessRequestMessage's payload)  be an element, not a type.

alex