I hope this is not the wrong place to post this
I just updated to the newer version of the Apache ODE 1.1.
Im using Eclipse BPEL Plugin to create my BPEL Files. I am getting an error
from axis that I didnt get in the prior release of ODE. Any help would be
appreciated. Eclipse Creates the BPEL and WSDL with the exception of the
Service and Binding and I manually created the deploy file. Im running on
Apache Tomcat and Windows XP
### ERROR ####
12:04:29,133 ERROR [WSDL11ToAxisServiceBuilder] RPC-literal type message
part payload should have a
type attribute
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
RPC-literal type me
ssage part payload should have a type attribute
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addPartToElement(WSDL11ToAxisServ
iceBuilder.java:1992)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.getNewComplextType(WSDL11ToAxisSe
rviceBuilder.java:1879)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.createSchemaForPorttype(WSDL11ToA
xisServiceBuilder.java:1544)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.generateWrapperSchema(WSDL11ToAxi
sServiceBuilder.java:1431)
at
org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServi
ceBuilder.java:255)
at
org.apache.ode.axis2.hooks.ODEAxisService.createService(ODEAxisService.java:79)
at org.apache.ode.axis2.ODEServer.createService(ODEServer.java:299)
at
org.apache.ode.axis2.BindingContextImpl.activateMyRoleEndpoint(BindingContextImpl.java:59
)
at
org.apache.ode.bpel.engine.BpelProcess.activate(BpelProcess.java:442)
at
org.apache.ode.bpel.engine.BpelEngineImpl.registerProcess(BpelEngineImpl.java:221)
at
org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:275)
at org.apache.ode.axis2.ODEServer.handleEvent(ODEServer.java:526)
at org.apache.ode.axis2.ODEServer.access$100(ODEServer.java:70)
at
org.apache.ode.axis2.ODEServer$ProcessStoreListenerImpl.onProcessStoreEvent(ODEServer.jav
a:512)
at
org.apache.ode.store.ProcessStoreImpl.fireEvent(ProcessStoreImpl.java:501)
at
org.apache.ode.store.ProcessStoreImpl.fireStateChange(ProcessStoreImpl.java:507)
at
org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:284)
at
org.apache.ode.axis2.deploy.DeploymentPoller.check(DeploymentPoller.java:144)
at
org.apache.ode.axis2.deploy.DeploymentPoller.access$300(DeploymentPoller.java:55)
at
org.apache.ode.axis2.deploy.DeploymentPoller$PollingThread.run(DeploymentPoller.java:188)
### WSDL ###
<?xml version="1.0"?>
<definitions name="Test4"
targetNamespace="Test4"
xmlns:tns="Test4"
xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype";
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-->
<types>
<schema attributeFormDefault="unqualified"
elementFormDefault="qualified"
targetNamespace="Test4"
xmlns="http://www.w3.org/2001/XMLSchema";>
<element name="Test4Request">
<complexType>
<sequence>
<element name="input" type="string"/>
</sequence>
</complexType>
</element>
<element name="Test4Response">
<complexType>
<sequence>
<element name="result" type="string"/>
</sequence>
</complexType>
</element>
</schema>
</types>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MESSAGE TYPE DEFINITION - Definition of the message types used as
part of the port type defintions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-->
<message name="Test4RequestMessage">
<part name="payload" element="tns:Test4Request"/>
</message>
<message name="Test4ResponseMessage">
<part name="payload" element="tns:Test4Response"/>
</message>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PORT TYPE DEFINITION - A port type groups a set of operations into
a logical service unit.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-->
<!-- portType implemented by the Test4 BPEL process -->
<portType name="Test4">
<operation name="process">
<input message="tns:Test4RequestMessage" />
<output message="tns:Test4ResponseMessage"/>
</operation>
</portType>
<binding name="Test4SOAPBinding" type="tns:Test4">
<soap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http"; />
<operation name="process">
<soap:operation soapAction="Test4/process" />
<input>
<soap:body use="literal" namespace="Test4" />
</input>
<output>
<soap:body use="literal" namespace="Test4" />
</output>
</operation>
</binding>
<service name="Test4Service">
<port name="Test4Port" binding="tns:Test4SOAPBinding">
<soap:address
location="http://localhost:8080/ode/processes/Test4"/>
</port>
</service>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PARTNER LINK TYPE DEFINITION
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-->
<plnk:partnerLinkType name="Test4">
<plnk:role name="Test4Provider" portType="tns:Test4"/>
</plnk:partnerLinkType>
</definitions>
### BPEL ###
!-- Test4 BPEL Process [Generated by the Eclipse BPEL Designer] -->
<process name="Test4"
targetNamespace="Test4"
suppressJoinFailure="yes"
xmlns:tns="Test4"
xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable";
>
<!-- Import the client WSDL -->
<import location="Test4.wsdl" namespace="Test4"
importType="http://schemas.xmlsoap.org/wsdl/"; />
<!-- =================================================================
-->
<!-- PARTNERLINKS
-->
<!-- List of services participating in this BPEL process
-->
<!-- =================================================================
-->
<partnerLinks>
<!-- The 'client' role represents the requester of this service. -->
<partnerLink name="client"
partnerLinkType="tns:Test4"
myRole="Test4Provider"
/>
</partnerLinks>
<!-- =================================================================
-->
<!-- VARIABLES
-->
<!-- List of messages and XML documents used within this BPEL process
-->
<!-- =================================================================
-->
<variables>
<!-- Reference to the message passed as input during initiation -->
<variable name="input"
messageType="tns:Test4RequestMessage"/>
<!--
Reference to the message that will be returned to the requester
-->
<variable name="output"
messageType="tns:Test4ResponseMessage"/>
</variables>
<!-- =================================================================
-->
<!-- ORCHESTRATION LOGIC
-->
<!-- Set of activities coordinating the flow of messages across the
-->
<!-- services integrated within this business process
-->
<!-- =================================================================
-->
<sequence name="main">
<!-- Receive input from requester.
Note: This maps to operation defined in Test4.wsdl
-->
<receive name="receiveInput" partnerLink="client"
portType="tns:Test4"
operation="process" variable="input"
createInstance="yes"/>
<!-- Generate reply to synchronous request -->
<reply name="replyOutput"
partnerLink="client"
portType="tns:Test4"
operation="process"
variable="output"
/>
</sequence>
</process>
### DEPLOY ###
<deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03";
xmlns:pns="Test4"
xmlns:wns="Test4">
<process name="pns:Test4">
<active>true</active>
<provide partnerLink="client">
<service name="wns:Test4Service" port="Test4Port"/>
</provide>
</process>
</deploy>
--
View this message in context:
http://www.nabble.com/Problems-with-ODE-1.1-Release-tf4355659.html#a12411954
Sent from the Apache Ode User mailing list archive at Nabble.com.
