[ https://issues.apache.org/jira/browse/TUSCANY-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luciano Resende resolved TUSCANY-1413. -------------------------------------- Resolution: Fixed Fix Version/s: Java-SCA-Next Patch applied under revision #553738 > WSDL and BPEL resolving > ----------------------- > > Key: TUSCANY-1413 > URL: https://issues.apache.org/jira/browse/TUSCANY-1413 > Project: Tuscany > Issue Type: Improvement > Components: Java SCA BEPL Implementation Extension > Reporter: Matthieu Riou > Priority: Minor > Fix For: Java-SCA-Next > > Attachments: patch.txt, patch.zip > > > 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). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]