Hi! I looked at this some more, and it appears my first email was correct after all. The types section of the wsdl is added to the definitions, but if the wsdl is not imported the partner link types are not added.
Also, only the wsdl file in the deployment bpel11wsdlFileName is added. -Doug. -----Original Message----- From: Jackson, Douglas [mailto:[EMAIL PROTECTED] Sent: Thursday, December 13, 2007 1:17 PM To: [email protected] Subject: RE: wsdl/partner link errors Hi! I take that back - looking at the wrong level. Sorry. -Doug. -----Original Message----- From: Jackson, Douglas [mailto:[EMAIL PROTECTED] Sent: Thursday, December 13, 2007 1:09 PM To: [email protected] Subject: RE: wsdl/partner link errors Hi! I could be wrong here, but looking at the code it appears that the only way for wsdl files to make it into the WSDLRegistry is to use the import in the bpel process. I see that there are no 1.1 BPEL tests in the source code. That's a bit scary... I updated the partner link type to contain the namespace after I sent the first message, and it still failed. The _definitions Map only contains the BPEL process and no WSDL docs even though there were 2 wsdls in the directory. -Doug.
