Closed bjhargrave closed 14 years ago
Comment author: Tim Diekmann <tdiekman@tibco.com>
As discussed at BundleFest in Montpellier and during the RFC 119 author's call on 11/05/08, there is a problem with the way a TCK can certify a DSW implementation without mandating the use of a Discovery service. The TCK needs a mechanism to trigger the proxy creation on the client side for testing purposes. If the DSW implementation integrates with the Discovery service, this can be done easily with a mock implementation. However, the use of the Discovery service is optional and not mandated to pass the TCK.
The proposed solution to the dilemma is to come up with an initialization phase (mechanism) executed by the TCK test cases before running the tests. This mechanism can then be implemented and specified by the DSW to ensure proper deployment of bundles and configuration of services. In the case of the DSW RI from Progress, this will only mean that the Discovery RI is deployed and started as part of the TCK.
The mechanism will be defined by the TCK in cooperation with the RI implementors and Peter Kriens.
Comment author: Tim Diekmann <tdiekman@tibco.com>
First proposal for such a mechanism:
Use the existing mechanism provided by the bnd build of osgi. bnd.bnd has a directive '-runbundles', where any user of the TCK can/should/needs to list additional bundles that need to be started as part of the TCK execution. For the DSW RI we simply list the Discovery implementation, but some other user of the TCK may put in different bundles.
Additionally, the TCK provides a test service, which it registers. The information about the service (name, class, properties, etc) are documented such that the DSW can provide its own mechanism to trigger the service discovery. I don't think there needs to be a programmable way to pass this information, documentation should be sufficient.
Comment author: @bosschaert
Fixed
Original bug ID: BZ#879 From: Tim Diekmann <tdiekman@tibco.com> Reported version: R4 V4.2