I have a PartnerLink defined in my process that is not used in any Invoke or
Receive activities.  Because it is not actually used (imagine a process that
is being developed incrementally), I don't bind that PartnerLink to an
endpoint (may or may not be known yet) in deploy.xml.    When I deploy I get
an exception:  "... Caused by: java.lang.IllegalArgumentException:
EchoService must be bound to an endpoint in deloy.xml"

>From the User Guide:
"Every partner link used with a <receive> activity must be matched with a
<provide> element, and every partnerLink used in an <invoke> activity must
be matched with an <invoke> element in deploy.xml (unless that partnerLink
has initializePartnerRole="false")."

I tried setting initializePartnerRole="false" and it doesn't seem to make a
difference.

My question is, should I be able to have an unused (in BPEL) and unbound (in
deploy.xml) PartnerLink in my process at all?  Is this a bug or expected
behavior?  I can write up an issue to either fix the code, or update the
user guide.  Just want to understand what type of issue it is first.

Second question: Is the dev list the right place to ask a question like
this, or should I have sent it to the user list?

Thanks,
Rich Taylor

Reply via email to