Hi, I recently came across situations where I wanted components to have multiple run-time defined references. For a single reference this can be achieved using a service tracker (on the referenced component) which creates the component through a component factory with the proper <reference>.target property.
Unfortunately, when multiple references of this kind are in place the service tracker approach - which ensures that the dynamic reference can be satisfied - fails, as one cannot easily track multiple targets at the same time. At first, I thought that the component activation should be delayed until the references are satisfied (opposed to throwing an exception when no immediate activation is possible) but later realized that this won't help much (e.g., a reference which is not the one tracked may go away and come back). The specification is also pretty clear on this. The proper solution to this problem seems to be a component factory with different semantics, where the created component follows the regular component lifecycle. Any thoughts on this? Does this seem feasible? Could this be a reasonable addition to the DS spec? with best regards Moritz Bechler -- AgNO3 GmbH & Co. KG, Sitz Tübingen, Amtsgericht Stuttgart HRA 728731 Persönlich haftend: Metagesellschaft mbH, Sitz Tübingen, Amtsgericht Stuttgart HRB 744820, Vertreten durch Joachim Keltsch
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
