[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: partner link assignment
Hi,
I have another question that I have been struggling
to resolve while reading the BPEL specification, hopefully someone can shed some
light on it.
The basic question is: what does it mean to assign
one partner link endpoint to another partner link endpoint? Is there an
example BPEL program somewhere which uses this functionality for something or
can someone provide a quick example of a situation in which it could be
used?
As I understand it (and I don't :) ), roles in a
partnerLink just reference one portType each. Each portType has only
one binding so (since the binding is used to create the concrete instances of a
portType) assigning one partner link endpoint (role) to another partner link
endpoint just means copying one port instance over another port instance (where
both instances are equivalent, having been instantiated using the same binding
information). Furthermore, this copying of port instances seems redundant
since which port instance is actually used for an invocation etc is determined
by the correlation sets associated with a port instance.
Do partnerLinks and their endpoint references map
to concrete instances of portTypes? (are
partnerLink endpoint references just port instances?) If so then why are
correlation sets necessary? since the port instance to which a invocation refers
at runtime is defined by the endpoint reference.
If someone has an example BPEL program that
demonstrates both correlation sets and partner link assignment, that would be
help me a lot.
thanks
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]