This content has been marked as final. Show 2 replies
I noticed in a previous post of yours that you were using WebSphere Integration Developer - is that still the case with this issue ?
This forum is primarily for OpenESB / GlassFishESB and JavaCAPS6
Unlike WID, they (the first two) are free to download and evaluate and the support within the community is readily available.
....I'm sure you'd get help with this particular problem if it was using one of the above.
I'm not sure I understand the first part of your question. Do you want to place some sort of interceptor between a WS client and the BPEL engine that receives requests from that client (via a binding component)? If so, there are various ways to do this, depending on the protocol used, and your purposes in using such an interceptor (debugging or application function?)
As for the error you got: your process would appear to need correlation sets, and simply adding a <receive> activity breaks the correlation rules of WS-BPEL. The problem arises from the fact that you can have multiple instances of the same process running at once. A <receive> activity needs to be able to figure out which instance an incoming message belongs to. The is called correlation: some piece (or pieces) of the incoming message must uniquely match a correlation key (or keys) for a running process instance.
For more information see the WS-BPEL 2.0 Primer, at [http://docs.oasis-open.org/wsbpel/2.0/Primer/wsbpel-v2.0-Primer.pdf|http://docs.oasis-open.org/wsbpel/2.0/Primer/wsbpel-v2.0-Primer.pdf] .