[osgi-dev] Declarative Services: ComponentFactory Question

Felix Meschberger fmeschbe at gmail.com
Tue Jun 3 02:09:06 EDT 2008


Hi,

Thanks for the clarification.

Am Montag, den 02.06.2008, 21:05 -0400 schrieb BJ Hargrave:
> No DS imlementation can require a factory component to have a service
> element. 
> 
> A factory component cannot be an immediate component since an instance
> of the component cannot be created until a call is made to the
> factory. From 112.2.2: 
> 
> "A component is an immediate component if it is not a factory compo- 
> nent ..." 
> 
> I think the confusion may lay in the description of the immediate
> attribute in 112.4.3: 
> 
> "immediate - Controls whether component configurations must be 
> immediately activated after becoming satisfied or whether activation 
> should be delayed. The default value is false if the service element
> is 
> specified and true otherwise. If this attribute is specified, its
> value must 
> be true unless the service element is also specified." 
> 
> which does not take into account factory components. 
> 
> A better description would be: 
> 
> "immediate - Controls whether component configurations must be 
> immediately activated after becoming satisfied or whether activation 
> should be delayed. The default value is false if the factory attribute
> or if the service element is 
> specified and true otherwise. If this attribute is specified, its
> value must be false if the factory attribute is also specified or
> must 
> be true unless the service element is also specified." 
> 
> 

I was in fact tricked into assuming a default (and required) value for
component factories, which is not in this sense.

In this case the Apache Felix implementation has a bug (which I am going
to fix) and the specification should be clarified which I am going to
bug.

Regards
Felix



More information about the osgi-dev mailing list