OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsbpel] Issue - 112 - Input/Output Elements on Messaging Activities


This also relates to Issue 11 - and creating a binding to an External Validation / Transaction Assembly service.
 
DW.
 
----- Original Message -----
Sent: Thursday, March 25, 2004 6:08 PM
Subject: [wsbpel] Issue - 112 - Input/Output Elements on Messaging Activities

This issue has been added to the wsbpel issue list. The issues list is posted as a Technical Committee document to the OASIS WSBPEL TC pages on a regular basis. The current edition, as a TC document, is the most recent document with the title in the "Issues" folder of the WSBPEL TC document list - the next posting will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.

Issue - 112 - Input/Output Elements on Messaging Activities

Status: open
Categories: Data handling
Date added: 25 Mar 2004
Submitter: Yaron Y. Goland
Date submitted: 25 March 2004
Description:

A common BPEL use case is that a programmer has a number of variables that contain data that will be used to create a message. When sending a message the programmer will create a temporary message variable, copy the values from the variables into the temporary message and then submit the temporary message variable. At which point the temporary message variable is discarded.

Similarly, when receiving a message the programmer may actually want the data in the message to be recorded in a number of variables. Currently the programmer has to create a temporary message variable, receive the message into the temporary message variable just to immediately turn around and pull the data out, record the data into individual variables and then discard the temporary message variable.

In both cases the temporary message variable is a transient storage location whose only purpose is to push data in and pull data out of message activities.

It would be extremely friendly if we could provide a macro that would allow programmers to build up a message as part of an invoke/reply from a set of variables rather than having to create a temporary variable for that purpose. Similarly, it would be great if it were possible on pick/receive to pull data directly out of an incoming message and record the data into variables rather than having to put the data into a temporary message variable whose only purpose is to get ripped to pieces.

To be clear, this is a request for a macro, not for a new BPEL feature.
Changes: 25 Mar 2004 - new issue


To comment on this issue, please follow-up to this announcement on the wsbpel@lists.oasis-open.org list (replying to this message should automatically send your message to that list), or ensure the subject line as you send it starts "Issue - 112 - [anything]" or is a reply to such a message.

To add a new issue, see the issues procedures document (but the address for new issue submission is the sender of this announcement).

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]