Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 361550

Summary:	Pattern for asynchronous invocations
Product:	z_Archived	Reporter:	Sandrine Beauche <sandrine.beauche>
Component:	BPEL	Assignee:	Project Inbox <bpel.default-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	mistria, vincent.zurczak
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Sandrine Beauche

2011-10-20 10:15:27 EDT

Build Identifier: 

This is a suggestion for the bpel designer. We should create new communication with a asynchronous pattern as a wizard or tool in the palette. 

Reproducible: Always

Comment 1 Vincent Zurczak

2011-10-20 10:29:04 EDT

Hi,

In the wizard, there is a template for asynchronous processes. What is missing in this template?

Otherwise, I don't think it would make sense in the palette, since you can build such a process by combining invoke activities.

Comment 2 Mickael Istria

2011-10-21 08:04:33 EDT

I think the general idea is to provide a kind of registry of patterns (including asynchronous call), and to provide the ability to integrate one of these patterns in the BPEL editor via the palette.
Sandrine, is this OK?

Comment 3 Sandrine Beauche

2011-10-21 08:29:47 EDT

(In reply to comment #2)
> I think the general idea is to provide a kind of registry of patterns
> (including asynchronous call), and to provide the ability to integrate one of
> these patterns in the BPEL editor via the palette.
> Sandrine, is this OK?

Hi,

Yes, the current wizard to have asynchronous calls creates in the same time a new BPEL. I suggest that we can add an asynchrone invocation in an existing bpel, as with a tool from the palette.