[TUSCANY-1413] WSDL and BPEL resolving

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: Java-SCA-1.0
• Component/s: Java SCA BPEL Implementation Extension
• Patch Info: Patch Available
• Assignee: Unassigned
• Reporter: Matthieu Riou
• Created: 05/Jul/07 23:45
• Updated: 19/Sep/10 11:26
• Resolved: 06/Jul/07 05:29

Description

I've done a few additional stuff on the BPEL implementation allowing a BPEL file to be compiled by ODE upon deployment. The implementation is therefore created and initialized with most of what would be needed by the runtime. However there's still a couple of problems with resolution and finding my way inside Tuscany code isn't that easy.

To resolve the WSDL implemented by the process I've been trying to go through the resolution mechanism and declare the implementation I return in the read() method of the processor as unresolved. However the resolve() method is never called afterward and this results in a NullPointerException in Tuscany. From what I could make out of the code, it seems that the resolution mechanism happens for Interface processors but not of implementations, but I could be wrong.

This patch adds the BPEL compilation and demonstrates the problem using the test case. Please have a look at BPELImplementationProcessor, you'll see how the implementation is built. You'll also see that the BPEL file from now is directly loaded using an additional "file" attribute. Ideally that should go as well to use the same type of resolving as for the WSDL (when it will work).