[jira] Created: (SLING-774) Components without configuration are listed in the Felix configuration dropdown
Components without configuration are listed in the Felix configuration dropdown --- Key: SLING-774 URL: https://issues.apache.org/jira/browse/SLING-774 Project: Sling Issue Type: Improvement Components: General Reporter: Mike Pfaff Priority: Minor These two components are currently listed in the Felix Configuration dropdown, but do not have anything that can be configured: org.apache.sling.scripting.javascript.internal.RhinoJavaScriptEngineFactory org.apache.sling.runmode.impl.RunModeImpl Adding metatype=false to the @scr.component definition should do the trick and remove them from the dropdown. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-775) Use consistent labeling for Sling components
Use consistent labeling for Sling components Key: SLING-775 URL: https://issues.apache.org/jira/browse/SLING-775 Project: Sling Issue Type: Improvement Components: General Reporter: Mike Pfaff Priority: Minor Currently not all Sling components use an @scr.component label that begins with Sling . Therefore all the Sling components are not listed together in the Felix Configuration dropdown. I therefore suggest that all Sling components use a label that begins with the same string. It seems that the currently used label-prefix is Sling . Maybe it would be good from a usability point of view to use Sling - as a prefix instead. This would separate the Software Name and the Component Name visually. With the configuration dropdown being very small and containing a lot of entries, a visual separation would be good IMHO. These components currently USE the Sling prefix: org.apache.sling.servlets.get.DefaultGetServlet org.apache.sling.commons.log.LogManager org.apache.sling.commons.log.LogManager.factory.config.* org.apache.sling.commons.log.LogManager.factory.writer.* org.apache.sling.servlets.post.impl.SlingPostServlet org.apache.sling.runmode.impl.RunModeImpl org.apache.sling.servlets.resolver.SlingServletResolver org.apache.sling.samples.pathbasedrtp.DefaultResourceTypeProvider These component-factories currently USE the Sling prefix: org.apache.sling.commons.log.LogManager.factory.config org.apache.sling.commons.log.LogManager.factory.writer These components currently do NOT USE the Sling prefix: org.apache.sling.event.impl.DistributingEventHandler org.apache.sling.i18n.impl.JcrResourceBundleProvider org.apache.sling.scripting.jsp.JspScriptEngineFactory org.apache.sling.scripting.java.JavaScriptEngineFactory org.apache.sling.event.impl.JobEventHandler org.apache.sling.jcr.classloader.internal.RepositoryClassLoaderProviderImpl org.apache.sling.engine.impl.auth.SlingAuthenticator org.apache.sling.engine.impl.log.RequestLogger org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl org.apache.sling.jcr.webdav.impl.servlets.SimpleWebDavServlet These components currently do NOT HAVE A LABEL at all: org.apache.sling.event.impl.EventingThreadPool org.apache.sling.scripting.javascript.internal.RhinoJavaScriptEngineFactory This component-factory currently does NOT USE the Sling prefix: org.apache.sling.engine.impl.log.RequestLoggerService -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-624) ignoreImportProviders cannot have more than one value
[ https://issues.apache.org/jira/browse/SLING-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Pfaff closed SLING-624. Resolution: Cannot Reproduce It now works with the double-quotes, therefore closing this issue. ignoreImportProviders cannot have more than one value - Key: SLING-624 URL: https://issues.apache.org/jira/browse/SLING-624 Project: Sling Issue Type: Bug Components: JCR Contentloader Affects Versions: JCR Contentloader 2.0.4 Reporter: Mike Pfaff Assignee: Carsten Ziegeler Fix For: JCR Contentloader 2.0.4 When using the following initial content configuration for the maven-bundle-plugin, only json files are ignored, but xml files are evaluated. The underlying problem is that ignoreImportProviders (which is part of a single Sling-Initial-Content entry) expects a comma-separated list and the Sling-Initial-Content expects a comma-separated list of entries. Sling-Initial-Content CQ-INF/content/apps/xyz/docroot;overwrite:=true;path:=/apps/xyz/docroot;ignoreImportProviders:=json,xml, CQ-INF/content/apps/xyz/components;overwrite:=true;path:=/apps/xyz/components, CQ-INF/content/apps/xyz/templates;overwrite:=true;path:=/apps/xyz/templates /Sling-Initial-Content -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-694) Initial Content does not load initial content from a file
Initial Content does not load initial content from a file -- Key: SLING-694 URL: https://issues.apache.org/jira/browse/SLING-694 Project: Sling Issue Type: Bug Components: JCR Contentloader Reporter: Mike Pfaff At the moment it is not possible to use the initial content feature to create a node based on a single JSON file.The initial content rule CQ-INF/content/etc/designs/xyz.json;overwrite:=true;path:=/etc/designs/xyz which should take the xyz.json file from the bundle and import it at /etc/designs/xyz does not work. In the log one can see entries which indicate that the content loader does not find the xyz.json file (maybe because the content loader thinks xyz.json is a folder name?). As we want to create (or overwrite, if it already exists) the /etc/designs/xyz node but leave all other existing content under /etc/designs intact, we have to use the xyz.json file and cannot define the whole designs-folder as initial content. It would be great and help us a lot if this bug was fixed for load 29. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-694) Initial Content does not load initial content from a file
[ https://issues.apache.org/jira/browse/SLING-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12639111#action_12639111 ] Mike Pfaff commented on SLING-694: -- Just tried it with this config: CQ-INF/content/etc/designs/xyz.json;overwrite:=true;path:=/etc/designs The import did NOT work, but i got the following xyz.json related messages in the error.log: 13.10.2008 18:56:52.262 *INFO* [Background Updatecom.customerxy.xyz-cq.xyz-cq-components (96)] org.apache.sling.jcr.contentloader.internal.Loader install: No initial content entries at CQ-INF/content/etc/designs/xyz.json 13.10.2008 18:56:57.214 *INFO* [FelixPackageAdmin] org.apache.sling.jcr.contentloader.internal.Loader install: No initial content entries at CQ-INF/content/etc/designs/xyz.json Initial Content does not load initial content from a file -- Key: SLING-694 URL: https://issues.apache.org/jira/browse/SLING-694 Project: Sling Issue Type: Bug Components: JCR Contentloader Reporter: Mike Pfaff At the moment it is not possible to use the initial content feature to create a node based on a single JSON file.The initial content rule CQ-INF/content/etc/designs/xyz.json;overwrite:=true;path:=/etc/designs/xyz which should take the xyz.json file from the bundle and import it at /etc/designs/xyz does not work. In the log one can see entries which indicate that the content loader does not find the xyz.json file (maybe because the content loader thinks xyz.json is a folder name?). As we want to create (or overwrite, if it already exists) the /etc/designs/xyz node but leave all other existing content under /etc/designs intact, we have to use the xyz.json file and cannot define the whole designs-folder as initial content. It would be great and help us a lot if this bug was fixed for load 29. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-694) Initial Content does not load initial content from a file
[ https://issues.apache.org/jira/browse/SLING-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12639219#action_12639219 ] Mike Pfaff commented on SLING-694: -- You might also want to discuss this bug/feature with Felix, as he helped me with the initial content setup on our project and might have some more background info. Initial Content does not load initial content from a file -- Key: SLING-694 URL: https://issues.apache.org/jira/browse/SLING-694 Project: Sling Issue Type: Bug Components: JCR Contentloader Reporter: Mike Pfaff At the moment it is not possible to use the initial content feature to create a node based on a single JSON file.The initial content rule CQ-INF/content/etc/designs/xyz.json;overwrite:=true;path:=/etc/designs/xyz which should take the xyz.json file from the bundle and import it at /etc/designs/xyz does not work. In the log one can see entries which indicate that the content loader does not find the xyz.json file (maybe because the content loader thinks xyz.json is a folder name?). As we want to create (or overwrite, if it already exists) the /etc/designs/xyz node but leave all other existing content under /etc/designs intact, we have to use the xyz.json file and cannot define the whole designs-folder as initial content. It would be great and help us a lot if this bug was fixed for load 29. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-624) ignoreImportProviders cannot have more than one value
[ https://issues.apache.org/jira/browse/SLING-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12625682#action_12625682 ] Mike Pfaff commented on SLING-624: -- I also tried that, but unfortunately it did not work. IIRC it even confused the importer. ignoreImportProviders cannot have more than one value - Key: SLING-624 URL: https://issues.apache.org/jira/browse/SLING-624 Project: Sling Issue Type: Bug Components: JCR Contentloader Affects Versions: JCR Contentloader 2.0.4 Reporter: Mike Pfaff Assignee: Carsten Ziegeler Fix For: JCR Contentloader 2.0.4 When using the following initial content configuration for the maven-bundle-plugin, only json files are ignored, but xml files are evaluated. The underlying problem is that ignoreImportProviders (which is part of a single Sling-Initial-Content entry) expects a comma-separated list and the Sling-Initial-Content expects a comma-separated list of entries. Sling-Initial-Content CQ-INF/content/apps/xyz/docroot;overwrite:=true;path:=/apps/xyz/docroot;ignoreImportProviders:=json,xml, CQ-INF/content/apps/xyz/components;overwrite:=true;path:=/apps/xyz/components, CQ-INF/content/apps/xyz/templates;overwrite:=true;path:=/apps/xyz/templates /Sling-Initial-Content -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-624) ignoreImportProviders cannot have more than one value
ignoreImportProviders cannot have more than one value - Key: SLING-624 URL: https://issues.apache.org/jira/browse/SLING-624 Project: Sling Issue Type: Bug Components: Maven Plugins Reporter: Mike Pfaff When using the following initial content configuration for the maven-bundle-plugin, only json files are ignored, but xml files are evaluated. The underlying problem is that ignoreImportProviders (which is part of a single Sling-Initial-Content entry) expects a comma-separated list and the Sling-Initial-Content expects a comma-separated list of entries. Sling-Initial-Content CQ-INF/content/apps/xyz/docroot;overwrite:=true;path:=/apps/xyz/docroot;ignoreImportProviders:=json,xml, CQ-INF/content/apps/xyz/components;overwrite:=true;path:=/apps/xyz/components, CQ-INF/content/apps/xyz/templates;overwrite:=true;path:=/apps/xyz/templates /Sling-Initial-Content -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-624) ignoreImportProviders cannot have more than one value
[ https://issues.apache.org/jira/browse/SLING-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12624045#action_12624045 ] Mike Pfaff commented on SLING-624: -- Workaround: Put the whole tree, for which you do not want the xml/json auto-import, into a zip. The importer will then automatically extract the zip contents, but he will leave the json and xml files alone. ignoreImportProviders cannot have more than one value - Key: SLING-624 URL: https://issues.apache.org/jira/browse/SLING-624 Project: Sling Issue Type: Bug Components: JCR Contentloader Affects Versions: JCR Contentloader 2.0.4 Reporter: Mike Pfaff Assignee: Carsten Ziegeler Fix For: JCR Contentloader 2.0.4 When using the following initial content configuration for the maven-bundle-plugin, only json files are ignored, but xml files are evaluated. The underlying problem is that ignoreImportProviders (which is part of a single Sling-Initial-Content entry) expects a comma-separated list and the Sling-Initial-Content expects a comma-separated list of entries. Sling-Initial-Content CQ-INF/content/apps/xyz/docroot;overwrite:=true;path:=/apps/xyz/docroot;ignoreImportProviders:=json,xml, CQ-INF/content/apps/xyz/components;overwrite:=true;path:=/apps/xyz/components, CQ-INF/content/apps/xyz/templates;overwrite:=true;path:=/apps/xyz/templates /Sling-Initial-Content -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
