Hi, On 10.11.2011, at 10:04, [email protected] wrote:
> Hi, > > Related to the iPojo "Service Dependancy management" > > > Actually > Thanks to "requires.filters" property it is possible to override the > filter attribute for a <requires ..>. > > Thanks to the policy attribute it is possible to define the binding > policy, but it not possible to override the attribut "policy". > > Thanks to the "comparator" attribute it is possible to override the > default implementation for sorting a service provider. > > > IPojo manages the non-functionalies for requiring and 'aggregating' services. > But the cardinality (non functional propertie) is not managed, and > must be implemented by the "pojo". > > What is your opinion to add/improve , features here after > i) The binding policy is overridable (taken eexample as requires.filters) This can be tricky is you set the policy to 'static'. Indeed, that would mean that whoever was already injected it must be frozen. If we decide to 'reset' the set of injected services, then it should be ok. > ii) The "requires" manages the cardinality , and the cardinality is > overridable too. > iii) Having the cardinality feature, the "Dynamic-priority" policy would also > be improved in order to respect the cardinality . This would be proposed as a > new attribute by example. As Richard, I'm a bit lost here. Do you mean that a component can specify it wants only 2 services (instead of n) ? Regards, Clement > > Best regards > Denis > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
