felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-2815) Difference between "instance" and "provides"
Date Mon, 07 Feb 2011 00:51:30 GMT

    [ https://issues.apache.org/jira/browse/FELIX-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991249#comment-12991249

Richard S. Hall commented on FELIX-2815:

Well, I was doing it from memory. :-)

There are lot of concepts, so it is difficult to get everything organized perfectly. In truth,
iPOJO is probably our best documented subproject...thanks to Clement! Still, everything can
be improved.

Regarding @Provides, yes, you are correct, you must be explicit to say what, if any, services
a component provides. Just because a component implements an interface, that doesn't mean
that it is necessarily a service. However, the default for @Provides is to assume all implemented
interfaces are services, but it also allows you to explicit specify which of the implemented
interfaces should be exposed as services.

> Difference between "instance" and "provides"
> --------------------------------------------
>                 Key: FELIX-2815
>                 URL: https://issues.apache.org/jira/browse/FELIX-2815
>             Project: Felix
>          Issue Type: Bug
>          Components: iPOJO
>            Reporter: Andriyko
>            Assignee: Clement Escoffier
>              Labels: documentation, felix,, ipojo
> In the documentation on iPOJO Services:
> http://felix.apache.org/site/providing-osgi-services.html#ProvidingOSGiservices-Instancereconfiguration
> There is no clear explanation of what is the difference between <provides> and
> It is not clear why "instance" is needed at all.
> Under the "Service Properties" heading on the page, the two are used interchangeably
in the examples.
> For example, first "property" is configured with <provides>:
> <component classname="...FooProviderType1">
>             <provides>
>                         <property name="foo" field="m_foo" value="Foo"/>
>                         <property name="static" type="java.lang.String" value="this
is a static property"/>
>             </provides>
> </component>
> and then immediately, with no explanation what-so-ever and <intsance> is used,
with a tiny explanation that "The value can be given in the instance configuration":
> <instance component="...FooProviderType1">
>    <property name="foo" value="My New Foo Value"/>
>    <property name="static" value="My Value For Static"/>
> </instance>

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message