[Users] petals-se-orchestra 1.0.1 and petals-standalone-2.2.1

[alouis]

Hi, 
You can not send any text to a bpel process, you have to conform the wsdl (and have a valid wsdl regarding bpel spec : document/ rpc, litteral.. and so on) 
I think that learning BPEL by yourself is not an easy thing; you should learn from tutorial, use cases find on the web or trainings. 

Good luck ;-) 


De : nguyen [mailto:petals-components at ebmwebsourcing.com] 
Envoyé : mardi 21 octobre 2008 10:39
À : petals-components at ebmwebsourcing.com
Objet : Re: petals-se-orchestra 1.0.1 and petals-standalone-2.2.1 


Hi,

I try deploy an easy "echo" bpel process using petals-se-orchestra-1.0.1 on petals-quikstart-2.2.
When I execute this sample in the "Petals - Sample client" with any input in the syntaxe any text, I got on output the error :

FAULT : soapenv:Serverhttp://exemple.bpel.acoss.fr/exemple1


My process.bpel :


targetNamespace="http://exemple.bpel.acoss.fr/exemple1"
suppressJoinFailure="yes"
xmlns:tns="http://exemple.bpel.acoss.fr/exemple1"
xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable"



importType="http://schemas.xmlsoap.org/wsdl/" />








partnerLinkType="tns:bpelTest"
myRole="bpelTestProvider"
/>









messageType="tns:bpelTestRequestMessage"/>


Reference to the message that will be returned to the requester -->
messageType="tns:bpelTestResponseMessage"/>










Note: This maps to operation defined in processName.wsdl  -->

portType="tns:bpelTest"
operation="process" variable="input"
createInstance="yes"/>



$input.payload/tns:input
$output.payload/tns:result





partnerLink="client"
portType="tns:bpelTest"
operation="process" 
variable="output"
/>




My process.wsdl :



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. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> MESSAGE TYPE DEFINITION - Definition of the message types used as  part of the port type defintions ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> PORT TYPE DEFINITION - A port type groups a set of operations into a logical service unit. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --> BINDING DEFINITION  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->   targetNamespace="http://exemple.bpel.acoss.fr/exemple1"  xmlns:tns="http://exemple.bpel.acoss.fr/exemple1"  xmlns:petals="http://petals.objectweb.org/"  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/"  >        targetNamespace="http://exemple.bpel.acoss.fr/exemple1"  xmlns="http://www.w3.org/2001/XMLSchema">                                                                        transport="http://schemas.xmlsoap.org/soap/http" />     <soap:operation  soapAction="{http://exemple.bpel.acoss.fr/exemple1}process" />      namespace="http://exemple.bpel.acoss.fr/exemple1" />         namespace="http://exemple.bpel.acoss.fr/exemple1" />          SERVICE DEFINITION  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->              PARTNER LINK TYPE DEFINITION ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->                         -------------------- m2f --------------------   Read this forum topic online here:  http://petals.ebmwebsourcing.com/forum/viewtopic.php?p=262#262 (http://petals.ebmwebsourcing.com/forum/viewtopic.php?p=262#262)   -------------------- m2f --------------------




-------------------- m2f --------------------

Read this forum topic online here:
http://petals.ebmwebsourcing.com/forum/viewtopic.php?p=263#263

-------------------- m2f --------------------


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://forum-list.petalslink.org/pipermail/users/attachments/20110316/ec69289f/attachment.htm>