have you checked the JIRAs to see if a similar problem was reported? I am not too familiar with C++, but that maybe a starting point.
On 7/9/08, Julien Bigot <[EMAIL PROTECTED]> wrote: > > Le Mercredi 09 Juillet 2008 à 15:27, Julien Bigot a écrit : > > Hi, > > > > I'm new to SCA and I've tried to implement a first composite with a few > > inner components. > > These components are written in C++ and use a legacy library that needs > > each user to be identified by a unique ID. > > I've therefore set the scope of the only interface of my component > > connected to this library as "composite" so that it doesn't connect twice > > with the same ID. > > It seems however that this is not taken into account and that many > > instances of the component are build. > > Is it a known behaviour or is the problem in my code ? > > > > Thanks, > > Julien > > After reading tuscany code it seems there's a difference between the > documentation as found in > > http://www.osoa.org/download/attachments/35/SCA_ClientAndImplementationModelforCpp_V0.95.pdf?version=1 > and the actual implementation and that the scope attribute should go to the > implementation.cpp node rather than to the interface.cpp as stated in the > documentation. > > Am I using an outdated documentation or doing another mistake ? > > Thanks, > Julien > >
