[
http://issues.ops4j.org/jira/browse/CONFMAN-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11815#action_11815
]
Alin Dreghiciu commented on CONFMAN-10:
---------------------------------------
1. https://scm.ops4j.org/repos/ops4j/projects/community/resources/ checkout
eclipse or idea for IDEs and checkstyle. And for projects we already have them
setup to be checked by using maven checkstyle plugin
2. If you look into osgi.bnd file you will find out that all transitive
dependencies are embeded into the confman bundle, meaning that during the build
process the ops4j base lang jar is copied into the confman jar and the
Bundle-ClassPath is set to take this jar into consideration. That is why you do
not get the CNF exception. You can verify that by looking inside confman jar.
3. Looks like the jira updates are also sent to general list, list which is the
one used to general discussions. So, no need to sent it again. But it is easier
for people to reply to emails then adding comments to jira issue. I do not
recall when thsi was changed but it used to only be sent to notify.
4. We release as often as required. So, if your change gets in ConfMan we can
release it right away.
> Service for updating single managed services
> --------------------------------------------
>
> Key: CONFMAN-10
> URL: http://issues.ops4j.org/jira/browse/CONFMAN-10
> Project: Pax ConfMan
> Issue Type: New Feature
> Components: PropsLoader
> Affects Versions: 0.2.2
> Reporter: Jens Borrmann
> Assignee: Alin Dreghiciu
>
> In our project we need the capability to update an already installed managed
> service (e.g. change log level at runtime) without reconfiguring other
> services. For this purpose we extended ConfMan 0.2.2. This new service
> IConfigurationUpdater offers just a single service method
> void updateConfiguration(String servicePid);
> The implementation consists in essence of a single line:
> this.adminFacade.registerConfigurations(servicePid, true);
> Our changes are almost non-invasive. There are two new files (the service
> interface and the implementation). Besides that we only have to register the
> service in Activator.start() und unregister in stop().
> Are you interested in integrating this into the official version? Otherwise
> we would write our own ConfigurationManager bundle by copying and extending
> your bundle.
> If you are interested in our solution, what is the best way to show you our
> solution? We also found some strange passages (errors?) in the existing code
> - mainly in ConfigurationAdminFacade.createConfigurationForFile() - and made
> minor changes that maybe should be discussed.
> Regards, Jens
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
