Problem Description:
In BPEL 1.1, We can achieve the dynamic partnerlink using simple ws-addressing but In BPEL 2.0, its not that simple. If we want to do with only ws-addressing, it will throw the following error:
<selectionFailure xmlns=”h ttp://docs.oasis-open.org/wsbpel/2.0/process/executable”>
<part name=”summary”>
<summary>fromValue is not a sref:service-ref element</summary>
</part>
Solution:
We can achieve the dynamic partnerlink in BPEL 2.0 without the error. For that we have to use EndpointReference element of ws-addressing.xsd and service-ref element of ws-bpel_serviceref.xsd.
Please visit here 12c-soa-bpel-20-dynamic-partner-link for the dynamic partnerlink implementation steps using EndpointReference element of ws-addressing.xsd and service-ref element of ws-bpel_serviceref.xsd.
In BPEL 1.1, We can achieve the dynamic partnerlink using simple ws-addressing but In BPEL 2.0, its not that simple. If we want to do with only ws-addressing, it will throw the following error:
<selectionFailure xmlns=”h ttp://docs.oasis-open.org/wsbpel/2.0/process/executable”>
<part name=”summary”>
<summary>fromValue is not a sref:service-ref element</summary>
</part>
Solution:
We can achieve the dynamic partnerlink in BPEL 2.0 without the error. For that we have to use EndpointReference element of ws-addressing.xsd and service-ref element of ws-bpel_serviceref.xsd.
Please visit here 12c-soa-bpel-20-dynamic-partner-link for the dynamic partnerlink implementation steps using EndpointReference element of ws-addressing.xsd and service-ref element of ws-bpel_serviceref.xsd.
No comments:
Post a Comment