The problem in fact was that the implementation.composite was not
referencing the composite correctly .
To correct it, update RestaurantComposite.composite with:
<sca:implementation.composite name="sample:BillServiceComposite"/>
(put the right composite name)
and make sure the "sample" namespace prefix is bound to the following URL
http://eclipse.org/stp/sca/sample/restaurant-ic/bill
which is the target namespace of the composite used as implementation.
Vincent.
Sebastián Groh a écrit :
Hi,
I found a solution for resolving the warnings and with the solution I
run the example properly.
My solution:
I changed two files, BillServiceComposite.composite, and
RestaurantComposite.composite (see them at last part).
The basic problem was that the Composite have the following service
(*1) <sca:service name="BillService"
promote="BillServiceComponent/BillService"/>
in where , I think that promoting was enough (please correct me if it
is wrong), because in BillServiceComponent is defined:
<sca:service name="BillService">
<sca:interface.java
interface="restaurant_implemcomposite.api.BillService"/>
</sca:service>
Mi solution was redefine sca:service (*1) tag as follows:
<sca:service name="BillService"
promote="BillServiceComponent/BillService">
<sca:interface.java
interface="restaurant_implemcomposite.api.BillService"/>
</sca:service>
In RestaurantComposite I redefine:
<sca:service name="RestaurantService"
promote="RestaurantServiceComponent/RestaurantService"/>
for:
<sca:service name="RestaurantService"
promote="RestaurantServiceComponent/RestaurantService">
<sca:interface.java
interface="restaurant_implemcomposite.api.RestaurantService"/>
</sca:service>
With this changes the project works correctly.
Someone in this mail list, can tell me if it is nonexistent
functionally in Tuscany 1.4 version or is my interpretation error of OSOA
specification? have Any suggestion?
Thanks,
Sebastián.
--
Vincent Zurczak
EBM WebSourcing
+33 (0) 4 38 12 16 77
