search

osgi / bugzilla-archive

Archive of OSGi Alliance Specification Bugzilla bugs. The Specification Bugzilla system was decommissioned with the move to GitHub. The issues in this repository are imported from the Specification Bugzilla system for archival purposes.
0 stars 1 forks source link

[rfc 0134] DS - allow activate to take configuration properties as a parameter #679

Closed bjhargrave closed 15 years ago

bjhargrave commented 16 years ago

Original bug ID: BZ#780 From: @bjhargrave Reported version: R4 V4.2

bjhargrave commented 16 years ago

Comment author: @bjhargrave

Carsten Ziegeler <cziegeler@ apache.org> wrote to speccomments on 2008/09/12 03:40:59 AM:

Hi,

I've read the suggest for updates to DS and I like them :) Section 3.2 is talking about alternative activate/deactivate method signatures. While it is great to have alternatives, the current suggestion does not allow to implement services which are not tied to the OSGi if the service wants to access a possible configuration.

Therefore, what about adding another argument to the list for activate (and perhaps deactivate):

At least in my case, the information I need most from the component context are the configuration properties.

Regards Carsten -- Carsten Ziegeler cziegeler@ apache.org

bjhargrave commented 16 years ago

Comment author: @bjhargrave

CPEG mtg: We agreed to do this but we want to use Map instead of Dictionary.

John Wells also suggests that bind/unbind be changed to have a variation that takes 2 arguments: service object and service properties (Map).

bjhargrave commented 16 years ago

Comment author: @bjhargrave

I updated RFC 134 to add Map for the activate, deactivate, bind and unbind methods.

bjhargrave commented 15 years ago

Comment author: @bjhargrave

Included in the current RFC 134 draft.