AW: [wsbpel] usage of <partner> in BPEL?

[Frank.Leymann@t-online.de (Frank Leymann)]

Alex,

a "real" partner (in the sense of an organization, e.g.) will typically
provide multiple endpoints where he offers the services to participate in a
given process. Finding an appropriate partner (during deployment time, e.g.)
requires to collectively determine/bind the corresponding endpoints. By
grouping <partnerLink>s the <partner> construct supports that - amongst
other usages.

But have to admit that one can view this as a deployment issue. Or as an
issue about specifying mutual dependencies between "partners" (sets of
endpoints) to support an interaction - something some folks called "global
models" in the past.

Frank



-----Ursprüngliche Nachricht-----
Von: Alex Yiu [mailto:alex.yiu@oracle.com] 
Gesendet: Tuesday, June 29, 2004 1:20 AM
An: wsbpel@lists.oasis-open.org
Cc: Alex Yiu
Betreff: [wsbpel] usage of <partner> in BPEL?


Hi all,

We define <partnerLink> and <partner> in BPEL.
The usage of <partnerLink> is very clear in BPEL. (e.g. invoke relies on 
partnerLink).

However, the usage of <partner> is not clear.
Is it more like a deployment related information?
Should it be a part of WSDL binding?
There are not other BPEL construct make uses of <partner> declaration.

I have done a very informal poll to a number of vendors last week at 
BPEL F2F in SF.
It seems to me that no particular vendor is actively making use of <partner>

Any further thoughts?

Thanks!


Regards,
Alex Yiu




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.