Le Jeudi 10 Juillet 2008 à 05:28, haleh mahbod a écrit : > 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.
I have checked the jIRAs for C++ SCA, but found nothing similar. After checking the documentation and the implementation again, I think I have found two problems. I'd really like your help to see if my understanding of * In the documentation, it is stated that the "scope" attribute can be defined for "interface.cpp" nodes while in the implementation, the "scope" attribute is handled when defined for "implementation.cpp" nodes. I can see the rationale behind both of these solutions but it seems to me that the one stated in the documentation is better. Anyway, if the chosen solution has changed, the documentation should be updated. I will open a bug for that. * In the documentation, it is stated that : --- > composite – Service requests are delegated to the same C++ class instance > for _all requests_ within the same “composite”. The lifecycle of a > composite-scoped instance extends from the point where the composite > component is loaded in the SCA runtime such that it is ready to service > requests until the composite is unloaded or stopped. Registry lookups will > return the same composite-scoped service instance for the duration of the > composite. --- The problem here is that "all requests" is not very clear. Does that mean : - All request to the same service ? - All request to the same "logical" component instance ? - All request, really ALL requests, even to a service this component doesn't implement ? The actual implementation has the 3rd behaviour which leads to segfaults. I'd advocate for the 1st or 2nd one depending if the scope is defined on an interface or on an implementation. I actually have a patch for this 2nd behaviour, but before taking time to polish it I'd like to be sure that this is really considered as a bug and that I am not the one misunderstanding the specification. > [...] thanks, Julien
signature.asc
Description: This is a digitally signed message part.
