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] Work started: (FELIX-324) Framework constructor should take a non-mutable property resolver
Date Wed, 11 Jul 2007 19:01:06 GMT

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

Work on FELIX-324 started by Richard S. Hall.

> Framework constructor should take a non-mutable property resolver
> -----------------------------------------------------------------
>                 Key: FELIX-324
>                 URL: https://issues.apache.org/jira/browse/FELIX-324
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: 1.0.0
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>             Fix For: 1.0.0
> As part of our effort to improve Felix' public API for the 1.0.0 release, I think we
should probably change the constructor to take a PropertyResolver instead of a MutablePropertyResolver.
I believe the original choice of MutablePropertyResolver was to avoid having to copy the passed
in configuration properties, but it is probably safer if the framework makes its own copy,
which will prevent attempts to externally modify the configuration properties at run time.

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

View raw message