Eclipse Community Forums: Equinox » Declarative Services re-use implementation class

Home » Eclipse Projects » Equinox » Declarative Services re-use implementation class

Declarative Services re-use implementation class [message #991640]

Wed, 19 December 2012 17:35

Eclipse User

Today we were reviewing a project that extensively uses declarative services.
We noticed that several component definitions were pointing to the same implementation class.

For instance:
* BundleA defines and exports a class AImpl with interface A.
* BundleB1
- imports AImpl's package
- defines a component C1 with implementation class AImpl and registers service A.
* BundleB2
- imports AImpl's package
- defines a component C2 with implementation class AImpl and registers service A.

Other bundles select the desired services by filtering on the registration properties of A from B1 and B2.

Question:
Re-using this same implementation class seemed odd to us.
Is there any real objection against using the same implementation class for multiple components?

The spec doesn't say anything about it afaik.
Does the Equinox implementation have any issues with it?

Thanks,
Johan

[Updated on: Wed, 19 December 2012 17:36] by Moderator

Re: Declarative Services re-use implementation class [message #991903 is a reply to message #991640]

Thu, 20 December 2012 08:01

Eclipse User

From a spec point of view, there is no issue with using the same impl class for multiple component descriptions. The Equinox DS impl needs to deal with this. If it does not, then please file a bug.

Previous Topic:	Building from source?
Next Topic:	Debugging Declarative Services resolution

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 26 02:12:16 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter