Originally CCPP-50

Target: C & C++ C&I Specifications

Description: Add additional APIs to support Assembly's @wiredByImpl

The Assembly 1.0 specification defines the following attribute on a
reference element:

"wiredByImpl (optional) - a boolean value, "false" by default, which
indicates that the implementation wires this reference dynamically. If
set to "true" it indicates that the target of the reference is set at
runtime by the implementation code (eg by the code obtaining an endpoint
reference by some means and setting this as the target of the reference
through the use of programming interfaces defined by the relevant Client
and Implementation specification). If "true" is set, then the reference
should not be wired statically within a composite, but left unwired."

This implies that the C/C++ APIs should provide a mechanism for setting
the service that would be associated with a reference, however the
current ComponentContext API (in C++) only provides a "getService()"
method.

A simple "setService()" call may not be sufficient, as the state rules
may require multiple instances of the service to exist.

Proposal:

none

Raised to the OASIS Service Component Architecture / C and C++ (SCA-C-C++) TC in the e-mail at http://lists.oasis-open.org/archives/sca-c-cpp/200809/msg00004.html