The last couple of weeks we’ve been playing around with the BPEL Designer plugin for JDeveloper 10.1.2. As BPEL is mostly used to integrate existing webservices, that’s what we started with.
To call an existing service, you need to use a partnerlink. Using the BPEL designer tool, you specify the WSDL file of the webservice to be called. This can be done using the url to the WSDL file online, but it’s better to download a copy of the WSDL and store it locally, since everytime the tool needs some information form the WSDL, the tool becomes unresponse; it seems to go online and parse the file every time. Using a local copy of the WDSL keeps the tools response snappy.
Most webservices I’ve tried to use do not provide any partnerlink information in their WSDL descriptions, which is required to make any calls using BPEL. Fortunately the tool caters for this and creates the required information in an extra file that imports the original WSDL of the webservice.
Yesterday I needed to validate some XML against a schema definition. I had a tool for that at hand, but alas, it failed to work. Looking for another way to do it I came across this site where you can check the validity of the xml online.
Steve Muench wrote up a superb overview of the most commonly used classes, interfaces & their methods in the ADF BC framework (formerly known as BC4J). You might want to check this out as it leads you straight to the stuff you need to write your apps, without getting lost in the JavaDoc…