There are requirements to have a DirectBinding at Exposed Services through which client should communicte. However, having said this is direct binding, it is not possible to test this service in EM as Test button is disabled due to direct binding.
1. For this scenario, we can create one more binding which is Web Service and tie two bindings together to have a single wire to the Component as shown below
The source of the Composite.xml should be like this.
3. Similarly, External References can also have two bindings and wired parallelly as shown above. If anyone is not wired, it throws design time error.
4. It is benefecial when there is any requirement to switch back to Web Service, we just simple change pointer at Invoke activity and everythingelse remains the same.
5. Input/Output variables also need not be changed.
1. For this scenario, we can create one more binding which is Web Service and tie two bindings together to have a single wire to the Component as shown below
The source of the Composite.xml should be like this.
<wire>2. Please note two bindings should not be connected to the component parallally as shown below and one BPEL service cannot have two clients which gives server runtime error.
<source.uri>DirectBindingClient</source.uri>
<target.uri>BPELProcess/DirectBindingClient</target.uri>
</wire>
<wire>
<source.uri>WebServiceClient</source.uri>
<target.uri>BPELProcess/DirectBindingClient</target.uri>
</wire>
3. Similarly, External References can also have two bindings and wired parallelly as shown above. If anyone is not wired, it throws design time error.
4. It is benefecial when there is any requirement to switch back to Web Service, we just simple change pointer at Invoke activity and everythingelse remains the same.
5. Input/Output variables also need not be changed.
