You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (Commented) (JIRA)" <ji...@apache.org> on 2011/11/16 13:08:51 UTC

[jira] [Commented] (FELIX-3227) ManagedService.update must be called with null if configuration exists but is not visilbe

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

Felix Meschberger commented on FELIX-3227:
------------------------------------------

Adapted integration test case to MS.update being called with null for invisible configuration (used to not be called at all previously)
                
> ManagedService.update must be called with null if configuration exists but is not visilbe
> -----------------------------------------------------------------------------------------
>
>                 Key: FELIX-3227
>                 URL: https://issues.apache.org/jira/browse/FELIX-3227
>             Project: Felix
>          Issue Type: Bug
>          Components: Configuration Admin, Specification compliance
>    Affects Versions:  configadmin-1.2.8
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: configadmin-1.4.0
>
>
> R 4.3 Configuration Admin Specification (v1.4) prescribes in Section 104.5.3, that ManagedService.update must be called with null if configuration exists but is not visible to the ManagedService. Currently this call with null is only done according to the R 4.2 (v 1.3) specification if configuration does not exist.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira