Hi.

Your problem is probably that ports aren't qualified names, just local
names. In your deploy.xml you've set a namespace prefix for the two ports
that get invoked. I'll had a little check so that next time, a more explicit
exception gets thrown.

Ok, so, following what you said, I'm now using the following description :

<process name="tns:GetConvertedStockValue">
<active>true</active> <provide partnerLink="tns:client">
       <service name="tns:GetConvertedStockValueService" 
port="GetConvertedStockValue"/>
     </provide>
     <invoke partnerLink="tns:Stock">
<service name="stock:StockService" port="StockServiceSOAP11port_http" /> </invoke>
      <invoke partnerLink="tns:Convert">
<service name="convert:ConverterService" port="ConverterServiceSOAP11port_http" /> </invoke>
   </process>
 </deploy>


The loader basically throw the same exception. I'm trying to create a lab session about WSOA using ODE in my engineering school, so it's a quite huge problem ... :'(

--
 Sebastian

Reply via email to