Return-Path: 
 <dev-return-26727-apmail-felix-dev-archive=felix.apache.org@felix.apache.org>
Delivered-To: apmail-felix-dev-archive@www.apache.org
Received: (qmail 59682 invoked from network); 7 Feb 2011 00:05:52 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 7 Feb 2011 00:05:52 -0000
Received: (qmail 6222 invoked by uid 500); 7 Feb 2011 00:05:51 -0000
Delivered-To: apmail-felix-dev-archive@felix.apache.org
Received: (qmail 6170 invoked by uid 500); 7 Feb 2011 00:05:51 -0000
Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@felix.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@felix.apache.org>
List-Post: <mailto:dev@felix.apache.org>
List-Id: <dev.felix.apache.org>
Reply-To: dev@felix.apache.org
Delivered-To: mailing list dev@felix.apache.org
Received: (qmail 6162 invoked by uid 99); 7 Feb 2011 00:05:51 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Feb 2011 00:05:51 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Feb 2011 00:05:50 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 9F178192488
	for <dev@felix.apache.org>; Mon,  7 Feb 2011 00:05:30 +0000 (UTC)
Date: Mon, 7 Feb 2011 00:05:30 +0000 (UTC)
From: "Andriyko (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: 
 <1109733483.3074.1297037130621.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <144712396.1401.1296533668932.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Reopened: (FELIX-2815) Difference between "instance" and
 "provides"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/FELIX-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andriyko reopened FELIX-2815:
-----------------------------


Sorry, but it is STILL not clear what the "instance" is. Why do we need it?

It is first referred to under the section titled "Service Publication", as:

"The service is published as long as the instance is valid."

What instance??? You never introduced the notion of an instance before, and it is confusing.

> 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 <instance>.
> 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