Re: Resolving files, getting the component interface

[Raymond Feng]

Hi,

By reading the spec, the "process" attribute specifies the target QName of 
an executable WS-BPEL process. We can follow the QName resolving approach to 
figure out which BPEL file to use. During the processing of a SCA 
contribution, we can create a BPELImplementation w/ the QName and mark it 
unresolved. For each BEPL file, we can record an entry to associate an BPEL 
file with the QName of the process. After resolving the QName of a process 
to a BPEL model, we can use the QName of the portType from the partLinkType 
in BEPL file to tell the WSDLs.

Thanks,
Raymond

----- Original Message ----- 
From: "Matthieu Riou" <[EMAIL PROTECTED]>
To: <tuscany-dev@ws.apache.org>
Sent: Monday, July 02, 2007 9:27 AM
Subject: Resolving files, getting the component interface


Hi guys,

I'm continuing on the ODE / Tuscany integration and I have a few more
riddles. Say that I have to following composite:

<composite xmlns="http://www.osoa.org/xmlns/sca/1.0"; targetNamespace="
http://bpel";
   xmlns:sc="http://bpel"; xmlns:c="http://bpel"; name="bpel">

   <service name="BPELHelloWorldService" 
promote="BPELHelloWorldComponent">
         <interface.wsdl
                 interface="
http://tuscany.apache.org/implementation/bpel/example/helloworld.wsd#wsdl.interface(HelloPortType)"
/>
   </service>

   <component name="BPELHelloWorldComponent">
       <implementation.bpel process="bpel-process"/>
   </component>
</composite>


I have 2 problems here:

1. How can I retrieve the WSDL interface associated with the BPEL
implementation? I need basic information about that WSDL to be able to 
load
the BPEL file and register it in ODE.
2. How do I load the BPEL file? I could add a specific attribute for the
file name but it's not so nice. Is there something that I can reuse that's
already been implemented? I think you automatically load all the WSDLs 
from
a contribution for example and then check from the namespace when you need
to retrieve something. Can I plug into that resolution mechanism?

I've been looking a bit at the code but a lot of the WSDL-related work is
done in binding components that seem to reuse common binding-specific 
code.

Thanks!
Matthieu



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]