Hi, I am interested in the use of the sling console to manage OSGi configurations.
Currently, only managed services with datatypes are managed by sling. For bundles that provide Managed Services, but no metatypes, I think it would be interesting also to : - Display the current configuration. - offer the possibility to change the property values - offer the possibility to add a new property or remove a property. Is there any work foreseen in that direction ? Regards, Anne -----Message d'origine----- De : Bertrand Delacretaz (JIRA) [mailto:[EMAIL PROTECTED] Envoyé : mardi 25 septembre 2007 11:30 À : sling-dev@incubator.apache.org Objet : [jira] Commented: (SLING-23) Use correct namespaces (for nodetypes, taglibs etc) [ https://issues.apache.org/jira/browse/SLING-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530073 ] Bertrand Delacretaz commented on SLING-23: ------------------------------------------ Maybe add a constant prefix before QUALIFIER? For example htttp://sling.apache.org/ns/... This would allow adding pages to our website under /ns/ to describe the namespaces later, if needed, by reserving this "ns" website path for this purpose. > Use correct namespaces (for node types, taglibs etc) > ---------------------------------------------------- > > Key: SLING-23 > URL: https://issues.apache.org/jira/browse/SLING-23 > Project: Sling > Issue Type: Bug > Reporter: Carsten Ziegeler > > As recently discussed, all namespace for sling should start with > "http://sling.apache.org/"; (and not use the jackrabbit namespace), followed > by an intermediate path denoting the type (like taglib, jcr namespace etc), > followed by the version, so we'll have: > http://sling.apache.org/taglibs/sling/1.0 > http://sling.apache.org/jcr/sling/1.0 > etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
