[
http://issues.ops4j.org/jira/browse/CONFMAN-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11813#action_11813
]
Jens Borrmann commented on CONFMAN-10:
--------------------------------------
Hello Alin,
being an ops4j newbie I have some questions you can maybe answer.
1) Is there some kind of automatic code formatting (maybe for eclipse)
available ot enforce the ops4j coding style conventions?
2) In my first hack I had deleted all code referring to NullArgumentException.
Then I tried to repair this and found the ops4j-base-lang-Bundle in the
repository. Is it possible that there are Import-Package directives missing for
org.ops4j.lang? By now we have never encountered NoClassDefFoundErrors but It
seems to me that something is wrong there, or am I getting something wrong?
3) You asked me to write an email to the general list. Looking into the general
list archives I found our conversation on this issue. Did the subscribers of
the general list also get notifications of our discussion do the archives
contain more than just the general list?
4) If our proposal for enhancing the ConfMan is accepted, how long will it
(approximately) take until a new official version will be available?
Thanks a lot for your help.
Jens
> 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
