[jira] Resolved: (FELIX-689) Instance 'name' property should become 'instance.name'

["Clement Escoffier (JIRA)" <ji...@apache.org>]

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

Clement Escoffier resolved FELIX-689.
-------------------------------------

    Resolution: Fixed

Fixed in the revision 687319
The 'name' property is now replaced by 'instance.name'. It allows instances managing their own 'name' property without interfering with the instance name.

> Instance 'name' property should become 'instance.name'
> ------------------------------------------------------
>
>                 Key: FELIX-689
>                 URL: https://issues.apache.org/jira/browse/FELIX-689
>             Project: Felix
>          Issue Type: Improvement
>          Components: iPOJO
>    Affects Versions: iPOJO-0.8.0
>            Reporter: Clement Escoffier
>            Assignee: Clement Escoffier
>
> When creating an instance the 'name' property is mapped to the instance name. However, this could be problematic when the pojo has a 'name' property. In this case this property is used by the POJO and as the instance name. So, this property is misleading.
> The proposed solution is to change this 'name' property to 'instance.name' which makes more sense to indicate the instance name.
> So, when declaring instance, several cases can occur:
> <instance component="..." name="xxx"> works as this attribute is mapped to "instance.name"
> However :
> <instance component="...">
>     <property name="name" value="xxx"/>
> </instance>
> is deprecated if "xxx" is really the instance name. In this case, the instance.name property should be added.
> When creating instances with the API, the instance configuration property should use the 'instance.name' property instead of 'name' to specify the instance name.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.