A Problem of Aggressive Cleanup
Just been working on an internal proof of concept and came across some very irritating behaviour in BPEL Designer in JDeveloper 10.1.3.3. I deleted a Partner Link and accepted the suggestion of JDeveloper BPEL Designer to delete the associated WSDL file. Unfortunately it turns out that this deletes not only the partner link specific WSDL file but also a shared WSDL file (DBAdapterOutboundHeader.wsdl) that is used by all DB Adapter Partner Links in the project. Net result is that this breaks all the remaining DB Adapter based Partner Links in the project. Fortunately there is a simple solution. Copy the DBAdapterOutboundHeader.wsdl from any other project with a DB Adapter in it into the project/bpel directory and your problems will be solved.For a view of some of the problems this may cause have a look at this blog.
