|
|
|
|
| Author |
Message |
|
2006/12/05 02:00
|
|
|
mourovaz
Joined: 2006/12/05
Messages: 2
Offline
|
|
|
|
I've developed a really simple BPMN process, and the idea is to generate the BPEL from it....
I've followed the example that is presented and no problem on that...But now imagine this process.
Start Event -> Receive Task from asynchronous participant -> send task to synchronous participant -> send task to the first asynchronous participant -> End Event
So Client_1 Sends a message to the bpDiagram which will be send to a synchronous client_2. This client will respond and then we'll send it's response back to Client_1.
In the receive task there's no problem, we have the Client1_Partner_link created with the initial_operation and the corresponding variable.
The problem is on the first send task. when we place the second Client2_Partner_link, on the Operation I get "<BPELPortType> not found", and the same on the variable "<BPELOperation> not found". I've defined the porttypes and the roles but i get nothing... can you guys give me any idea?
Thanks in advance
|
|
|
|
 |
| |
|
|
2006/12/05 10:12
|
|
|
Jick
Joined: 2005/04/29
Messages: 2881
Offline
|
|
|
|
Hi mourovaz,
Thank you for your post. Let me summarize your message into two issues:
=== "<BPELPortType> not found" ===
The synchronous participant's PortType may be missing or not match
<wsdl:portType name="{PortType}">...</wsdl:portType>
<plnk:role name="{Provider Role}">
<plnk:portType name="{Prefix}:{PortType}"/>
</plnk:role>
=== "<BPELOperation> not found" ===
Since variable is depend on operation, it will be disappear after set operation
Best regards,
Jick
|
Visual Paradigm International Ltd.
http://www.visual-paradigm.com
Build Quality Applications Faster, Better and Cheaper |
|
|
|
|
| |
|
|
2006/12/05 18:52
|
|
|
mourovaz
Joined: 2006/12/05
Messages: 2
Offline
|
|
|
|
Hi Jick,
Thanks for your quick answer.
I understood your answer but then clarify me in some other matter. The Port Type is included on the .wsdl, and this is generated when creating the synchronous participant right?
In my case I'll have two .wsdl's, one for each service (participant), meaning one which will define the messages in and out, operations, port for Client_1 and another for Client_2, right?
But if they're generated by BP_VA why do they have the same prefix? and the same targetNamespace? it doesn't make sense, right?
If this is true, :S the PortType is there and everything seemsto be ok...Can you give me a hand....?
|
|
|
|
|
| |
|
|
2006/12/05 19:34
|
|
|
Jick
Joined: 2005/04/29
Messages: 2881
Offline
|
|
|
|
Hi mourovaz,
Let me discuss with our team members first. I will reply you as soon as possible.
Best regards,
Jick
|
Visual Paradigm International Ltd.
http://www.visual-paradigm.com
Build Quality Applications Faster, Better and Cheaper |
|
|
|
|
| |
|
|
2006/12/06 10:02
|
|
|
Jick
Joined: 2005/04/29
Messages: 2881
Offline
|
|
|
|
Hi mourovaz,
Q1. The Port Type is included on the .wsdl, and this is generated when creating the synchronous participant right?
Yes, or you can define a similar WSDL your own.
Q2. One which will define the messages in and out, operations, port for Client_1 and another for Client_2, right?
Yes, Client_1 and Client_2 should have their own messages in and out, operations, port etc.
Q3. Why do they have the same prefix? and the same targetNamespace? it doesn't make sense, right?
Each BPEL has one WSDL for describing the process itself for external interaction (WSDL for outside to invoke process),
other WSDLs are describing external application for interacting with them (WSDLs for process to invoke outside).
Within BP-VA, the generated WSDL is used for describing the process itself.
Therefore, we use diagram information (Diagram's pool name) for the generation.
In your case, I guess you generate participant twice within same process.
Since generation information is same, the result should be same.
That's why they got same prefix and targetNamespace.
=== Major points to invoke external process or application ===
1. The external process or application should be existing
2. When creating participant of external process or application, use their WSDL rather then BP-VA generated.
3. While creating partnerLink of external process or application, set the role basic on process. ( Normally, myRole = requester, partnerRole = provider )
Best regards,
Jick
|
Visual Paradigm International Ltd.
http://www.visual-paradigm.com
Build Quality Applications Faster, Better and Cheaper |
|
|
|
|
| |
|
|
|
|
