Bpel Process invoking different BPEL process

Question

Hi all
We have a situation here. It goes like this.
We have a requirement to call another BPEL process from ours. The calling process is fine. But the called process threw a lot of error due to which we discarded it and created a new process. We have mapped the same to the original calling process. Now,even after undeploying the discarded process, our main process is still calling the old process that is not even there on server and is constantly completinh in an unintended manner.
If anyone has faced this issue previously, kindly throw some light on this.
Vijay

Answer 1

I don't understand "mapped the same to the original calling process." If you created a new callED process with the same name as the original callED process, you will want to replace the callED processl partnerlink and WSDL in the callING process, as another poster suggested.
If the new callED process has the same name and exactly the same WSDL as the old one, you could be able to get away without changing the callING process. You have to be very careful to clear the old/bad callED process from the server. This may be overkill, but I suggest doing this in the BPEL console:
- Select the old/bad process in the BPEL console, go to the Manage tab, select Undeploy.
- Go to the Administration tab, Actions subtab, hit the Clear WSDL Cache button.
- Delete all files from your JDeveloper BPEL project output folder and recompile.
- Deploy your process to the BPEL server.
Good Luck!