Hi Clement, Thanks for the clarification on iPOJO. I have to admit, that I once looked at it (a long time ago, just before I decided to implement Config Admin :-) ) and was not happy with it regarding configurability. I found (at that time) that Config Admin together with Declarative Service would suite my needs much better than iPOJO.
And yes, I think, the management API should be pure Java, where as JMX and support for the shell should be optional additions. Regards Felix Am Montag, den 03.12.2007, 10:24 +0100 schrieb Clement Escoffier: > Hi Felix, > > iPOJO provides a different way to analyze configurations. Each instance (ie > component in the API) can be "introspectable" by activating an Architecture > handler allowing the administrator to know the instance state (unresolved > dependencies, service properties, created object, used objects ...). However, > as iPOJO is extensible this representation need to be extensible too (in the > sense where every handler can participate to the instance introspection). > > However, The proposed API makes sense for iPOJO in the sense where > Architecture does not allow to start/stop/reconfigure instances. We had > develop a special M-BEAN (on M-OSGi) to create / modify / delete instances. > This mechanism was ad-hoc, and so the API is clearer than what we developed. > Moreover, having a common view of every service component seems to me a good > idea despite the different features of each component model. > > Regards, > > Clement > > > -----Message d'origine----- > > De : Felix Meschberger [mailto:[EMAIL PROTECTED] > > Envoyé : dimanche 2 décembre 2007 19:23 > > À : dev@felix.apache.org > > Objet : RE: [jira] Commented: (FELIX-284) Add Management API > > > > Hi Clement, > > > > Cool. Now the question is of course, whether the API is of any use to > > iPOJO ? For DS it allows inspecting the configuration and just > > enabling/disabling of components, which is about anything you might > > want > > to do anyway. > > > > Not sure about iPOJO, though. > > > > Regards > > Felix > > > > Am Sonntag, den 02.12.2007, 14:25 +0100 schrieb Clement Escoffier: > > > Hello, > > > > > > I just look the proposed API. This API can be totally supported by > > iPOJO (except perhaps Reference.getTarget()).The vocabulary is a little > > different from what I use in iPOJO, but a mapping can be found easily > > (as DISABLED <=> STOPPED, UNSATISFIED <=> INVALID, ACTIVE <=> VALID > > ...). > > > > > > Clement > > > > > > > -----Message d'origine----- > > > > De : Felix Meschberger (JIRA) [mailto:[EMAIL PROTECTED] > > > > Envoyé : vendredi 23 novembre 2007 09:20 > > > > À : dev@felix.apache.org > > > > Objet : [jira] Commented: (FELIX-284) Add Management API > > > > > > > > > > > > [ https://issues.apache.org/jira/browse/FELIX- > > > > 284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment- > > > > tabpanel#action_12544939 ] > > > > > > > > Felix Meschberger commented on FELIX-284: > > > > ----------------------------------------- > > > > > > > > After discussion the potential merger of the management API with > > the > > > > needs of dependency manager, we came to the conclusion, that I > > should > > > > go forward with the proposed implementation of the API. > > > > > > > > The reason for this is, that the issue at hand requires more > > > > discussions: We have currently three projects around component and > > > > service management in Felix: Dependency Manager, SCR and IPOJO. It > > > > might be worth investigating, whether there exists some possible > > > > convergence of the three. Only after having found possible > > convergence > > > > (or not), can a possible combined Management API be discussed. > > > > > > > > > Add Management API > > > > > ------------------ > > > > > > > > > > Key: FELIX-284 > > > > > URL: https://issues.apache.org/jira/browse/FELIX- > > 284 > > > > > Project: Felix > > > > > Issue Type: New Feature > > > > > Components: Declarative Services, Dependency Manager > > > > > Reporter: Felix Meschberger > > > > > Assignee: Felix Meschberger > > > > > Fix For: 1.0.0 > > > > > > > > > > Attachments: FELIX-284.tgz > > > > > > > > > > > > > > > Currently, it is not directly visible, what state a component has > > and > > > > what references are satisified. > > > > > The intent is to define a simple API - along the lines of the > > > > ServiceBinder architecure interfaces. > > > > > These interfaces may then be used to implement integrations into > > > > management applications such as the Felix shell or JMX. > > > > > > > > -- > > > > This message is automatically generated by JIRA. > > > > - > > > > You can reply to this email to add a comment to the issue online. > > > >
