Community
Participate
Working Groups
+ Create a new partner link. + In its properties, click Browse. + Click Add WSDL. + Choose File and select a WSDL file on your disk. + End up the wizard to complete the definition of the partner link. Save the BPEL process. An error appears in both the BPEL (port type not found) and in the WSDL Artifacts (the newly imported WSDL could not be parsed). The error in fact is due to an invalid referencement. As an example, here is what was in my WSDL Artifacts: <import location="D:\BackupBureau\WSDLs\tuxDroid.wsdl" namespace="http://tuxdroid.ebmwebsourcing.com/"/> instead of <import location="file:/D:/BackupBureau/WSDLs/tuxDroid.wsdl" namespace="http://tuxdroid.ebmwebsourcing.com/"/> The BPEL Designer should reference files by URL and not by file paths, as it is not supported in WSDL imports.
Hi Vincent, For adding wsdl, in the wizard page, we can select wsdl by resource, file, url, wsil, four ways. I test it on my machine, it can work well as using file options to add wsdl file. Could you upload your wsdl files, let me test? Thanks! Grid
Created attachment 200689 [details] A WSDL to test the file import.
Hi, I added a WSDL from a file. The error on my side was just the import location which was not an URL. I can attach my WSDL if you want. I had planned to fix this problem myself, but I did not find time for this (yet).
Ok, I will try to test, and leave the issue to you. Haha.
Confirmed on the last repo.
As a complement, the problem occurs when the WSDL cannot be localized relatively to the BPEL file (e.g. if the WSDL is picked up on other disk partition). Fixed.
