[jira] Commented: (SLING-611) Save OSGi event properties as JCR properties
[ https://issues.apache.org/jira/browse/SLING-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12622461#action_12622461 ] Carsten Ziegeler commented on SLING-611: Thanks for the pointer - yes this solves the problem partially - the event property could use a namespace like syntax which does not use a known prefix from the repository, like myspecialevent:property, so we might have to escape the colons as well. Save OSGi event properties as JCR properties Key: SLING-611 URL: https://issues.apache.org/jira/browse/SLING-611 Project: Sling Issue Type: Improvement Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 Currently all OSGi event properties are saved in a single JCR property (as serialized java object) If possible the event properties can directly be saved as JCR properties - only props who's name or type is not directly usable get saved as a serialized java object -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-612) When several jobs of the same time are run in parallel, these are tried without a wait time in a cycle
When several jobs of the same time are run in parallel, these are tried without a wait time in a cycle -- Key: SLING-612 URL: https://issues.apache.org/jira/browse/SLING-612 Project: Sling Issue Type: Improvement Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 Each job should be put back in the queue *after* the configured wait time. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-611) Save OSGi event properties as JCR properties
[ https://issues.apache.org/jira/browse/SLING-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-611. -- Resolution: Fixed The approach is very easy: if the name contains a : it's not saved as a property if the value is long, calendar, string, boolean or double the property is saved All other values are saved as a blob as the back conversion would not guarantee to have the same type (Yes, we could store the types in addition and recreate them, but I think that's not worth the effort atm) Save OSGi event properties as JCR properties Key: SLING-611 URL: https://issues.apache.org/jira/browse/SLING-611 Project: Sling Issue Type: Improvement Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 Currently all OSGi event properties are saved in a single JCR property (as serialized java object) If possible the event properties can directly be saved as JCR properties - only props who's name or type is not directly usable get saved as a serialized java object -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-614) Persist job retry count in repository
Persist job retry count in repository - Key: SLING-614 URL: https://issues.apache.org/jira/browse/SLING-614 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 The retry count for jobs is currently only stored in memory -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-612) When several jobs of the same time are run in parallel, these are tried without a wait time in a cycle
[ https://issues.apache.org/jira/browse/SLING-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-612. -- Resolution: Fixed When several jobs of the same time are run in parallel, these are tried without a wait time in a cycle -- Key: SLING-612 URL: https://issues.apache.org/jira/browse/SLING-612 Project: Sling Issue Type: Improvement Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 Each job should be put back in the queue *after* the configured wait time. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-606) Event to cancel a job
[ https://issues.apache.org/jira/browse/SLING-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-606: --- Fix Version/s: Extensions Event 2.0.4 Event to cancel a job - Key: SLING-606 URL: https://issues.apache.org/jira/browse/SLING-606 Project: Sling Issue Type: New Feature Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 It should be possible to cancel a running job by sending a special event. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (SLING-571) JspServletWrapper swallows jsp exceptions if root cause is null
[
https://issues.apache.org/jira/browse/SLING-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reopened SLING-571:
Reopen this bug so we don't forget it
JspServletWrapper swallows jsp exceptions if root cause is null
---
Key: SLING-571
URL: https://issues.apache.org/jira/browse/SLING-571
Project: Sling
Issue Type: Bug
Components: Scripting JSP
Affects Versions: Scripting JSP 2.0.2
Reporter: Tobias Bocanegra
Assignee: Carsten Ziegeler
Fix For: Scripting JSP 2.0.4
Attachments: SLING-571-reloaded.patch, SLING-571-third.patch,
SLING-571.patch
For example for a JSP compile error the 'realException' is null and the
following stack-frame resolution fails:
(JspServletWrapper.java, line 492ff)
// First identify the stack frame in the trace that represents
the JSP
StackTraceElement[] frames = realException.getStackTrace();
StackTraceElement jspFrame = null;
for (int i=0; iframes.length; ++i) {
if (
frames[i].getClassName().equals(this.getServlet().getClass().getName()) ) {
jspFrame = frames[i];
break;
}
}
Suggest to check for (realException == null)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-616) Provide better filter options to search for job
Provide better filter options to search for job --- Key: SLING-616 URL: https://issues.apache.org/jira/browse/SLING-616 Project: Sling Issue Type: New Feature Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 Currently it's only possible to search for all jobs, activate jobs and filter by an exact matching topics. This can be enhanced to allow pattern matching for the job topic - like the OSGi eventing does and to provide a map of properties that must match as well. This map acts like a search template. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-618) Add ResourceUtil.listChildren(Resource)
Add ResourceUtil.listChildren(Resource) --- Key: SLING-618 URL: https://issues.apache.org/jira/browse/SLING-618 Project: Sling Issue Type: Improvement Components: API Affects Versions: API 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: API 2.0.4 Add listChildren(Resource) to ResourceUtil for convenience -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-618) Add ResourceUtil.listChildren(Resource)
[ https://issues.apache.org/jira/browse/SLING-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-618. -- Resolution: Fixed Add ResourceUtil.listChildren(Resource) --- Key: SLING-618 URL: https://issues.apache.org/jira/browse/SLING-618 Project: Sling Issue Type: Improvement Components: API Affects Versions: API 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: API 2.0.4 Add listChildren(Resource) to ResourceUtil for convenience -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-619) Add a java servlet scripting engine
Add a java servlet scripting engine --- Key: SLING-619 URL: https://issues.apache.org/jira/browse/SLING-619 Project: Sling Issue Type: New Feature Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler For easier scripting it would be nice to have a scripting engine that compiles a java servlet out of a java file which is stored in the repository, like /apps/my/app/html.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-620) Use value map to render resources
Use value map to render resources - Key: SLING-620 URL: https://issues.apache.org/jira/browse/SLING-620 Project: Sling Issue Type: Improvement Components: Servlets Get Affects Versions: Servlets Get 2.0.2 Reporter: Carsten Ziegeler The rendering servlets should make use of the resource abstraction and use the value map to render the contents. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-622) JspScriptEngineFactory: reference to repository classloader is not correctly unbound
JspScriptEngineFactory: reference to repository classloader is not correctly unbound Key: SLING-622 URL: https://issues.apache.org/jira/browse/SLING-622 Project: Sling Issue Type: Bug Components: Scripting JSP Affects Versions: Scripting JSP 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Scripting JSP 2.0.4 The order of invocation if a service updates: - bind the new service - unbind the old service -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-622) JspScriptEngineFactory: reference to repository classloader is not correctly unbound
[ https://issues.apache.org/jira/browse/SLING-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-622. -- Resolution: Fixed JspScriptEngineFactory: reference to repository classloader is not correctly unbound Key: SLING-622 URL: https://issues.apache.org/jira/browse/SLING-622 Project: Sling Issue Type: Bug Components: Scripting JSP Affects Versions: Scripting JSP 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Scripting JSP 2.0.4 The order of invocation if a service updates: - bind the new service - unbind the old service -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-623) Update to OSGi R4.1
Update to OSGi R4.1 --- Key: SLING-623 URL: https://issues.apache.org/jira/browse/SLING-623 Project: Sling Issue Type: Improvement Components: General Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-623) Update to OSGi R4.1
[ https://issues.apache.org/jira/browse/SLING-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-623. -- Resolution: Fixed Update to OSGi R4.1 --- Key: SLING-623 URL: https://issues.apache.org/jira/browse/SLING-623 Project: Sling Issue Type: Improvement Components: General Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-619) Add a java servlet scripting engine
[ https://issues.apache.org/jira/browse/SLING-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-619: --- Component/s: Scripting Java Add a java servlet scripting engine --- Key: SLING-619 URL: https://issues.apache.org/jira/browse/SLING-619 Project: Sling Issue Type: New Feature Components: Scripting Java Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler For easier scripting it would be nice to have a scripting engine that compiles a java servlet out of a java file which is stored in the repository, like /apps/my/app/html.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-625) Add support for installing of deployment packages
Add support for installing of deployment packages - Key: SLING-625 URL: https://issues.apache.org/jira/browse/SLING-625 Project: Sling Issue Type: New Feature Components: Launchpad Affects Versions: Launchpad Base 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Launchpad Base 2.0.4 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-625) Add support for installing of deployment packages
[ https://issues.apache.org/jira/browse/SLING-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-625. -- Resolution: Fixed Committed initial version. Add support for installing of deployment packages - Key: SLING-625 URL: https://issues.apache.org/jira/browse/SLING-625 Project: Sling Issue Type: New Feature Components: Launchpad Affects Versions: Launchpad Base 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Launchpad Base 2.0.4 -- 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=12624587#action_12624587 ] Carsten Ziegeler commented on SLING-624: Hi Mike, could you please test if quoting the value works? CQ-INF/content/apps/xyz/docroot;overwrite:=true;path:=/apps/xyz/docroot;ignoreImportProviders:=json,xml, 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] Updated: (SLING-570) Bundles should only be installed for the first time
[ https://issues.apache.org/jira/browse/SLING-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-570: --- Fix Version/s: Launchpad Base 2.0.4 Assignee: Carsten Ziegeler Bundles should only be installed for the first time --- Key: SLING-570 URL: https://issues.apache.org/jira/browse/SLING-570 Project: Sling Issue Type: Improvement Components: Launchpad Affects Versions: Launchpad Base 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Launchpad Base 2.0.4 Currently the launcher scans on startup a directory and installs all bundles - this installation process is done each time. This has the drawback that whenever the user uninstalls a bundle, it gets reinstalled the next time Sling is started. In addition, Sling should check the version before installing a bundle. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-601) Request Inclusion Counter operating too rigid
[ https://issues.apache.org/jira/browse/SLING-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12625645#action_12625645 ] Carsten Ziegeler commented on SLING-601: Yes, I think having both limits makes sense - as pointed out, the current mechanism checks the recursion level where a value of 50 should really be sufficient. In addition couting the total number of includes and limiting them (to 1000) makes sense. However, it would be great to have this configurable - I can imagine that if you're building heavy portal sites the limits should be higher. Request Inclusion Counter operating too rigid - Key: SLING-601 URL: https://issues.apache.org/jira/browse/SLING-601 Project: Sling Issue Type: Bug Components: Engine Affects Versions: Engine 2.0.2 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Engine 2.0.4 The SlingMainServlet implements a recursion level counter to prevent recursions going too deep in the checkRecursionLevel method. What this method does is incrementing a counter stored as a request attribute everytime RequestDispatcher.include is called (by whatever means). The drawback of this mechanism is, that the counter is only incremented and never decremented after an inclusion returns. This in fact is not a recursion level counter but a counter limiting the number of times RequestDispatcher.include may be called. Another drawback of this is, that the implementation is overcomplicated, because the RequestData object created for each request keeps a stack of a inclusions and hence could easily implement a real recursion level checker by just checking the size of the stack. I think, we should drop the SlingMainServlet.checkRecursionLevel method altogether and replace it with a new RequestData.checkAbort method which throws in case any of two cases occurrs: * Recursion Level is too deep (50 seems like useful) * Number of includes exceeds a given number (something like 1000 or more ?) In addition the Exception should be made public in the Sling engine module such that users of any include mechanism could handle it if need be. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-570) Bundles should only be installed for the first time
[ https://issues.apache.org/jira/browse/SLING-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-570. -- Resolution: Fixed Bundles should only be installed for the first time --- Key: SLING-570 URL: https://issues.apache.org/jira/browse/SLING-570 Project: Sling Issue Type: Improvement Components: Launchpad Affects Versions: Launchpad Base 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Launchpad Base 2.0.4 Currently the launcher scans on startup a directory and installs all bundles - this installation process is done each time. This has the drawback that whenever the user uninstalls a bundle, it gets reinstalled the next time Sling is started. In addition, Sling should check the version before installing a bundle. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-497) Keep order of jobs when executing
[ https://issues.apache.org/jira/browse/SLING-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-497: --- Affects Version/s: (was: 2.0.0) Extensions Event 2.0.2 Fix Version/s: Extensions Event 2.0.4 Assignee: Carsten Ziegeler Keep order of jobs when executing - Key: SLING-497 URL: https://issues.apache.org/jira/browse/SLING-497 Project: Sling Issue Type: New Feature Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 Usually jobs are executed in random manner (usually first one, first out), but especially in a cluster this might not be true. For some jobs it might be interesting to keep the order of execution. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-614) Persist job retry count in repository
[ https://issues.apache.org/jira/browse/SLING-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-614. -- Resolution: Fixed Persist job retry count in repository - Key: SLING-614 URL: https://issues.apache.org/jira/browse/SLING-614 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 The retry count for jobs is currently only stored in memory -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-498) Execute jobs only on the instance they were created on
[ https://issues.apache.org/jira/browse/SLING-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-498: --- Affects Version/s: (was: 2.0.0) Extensions Event 2.0.2 Fix Version/s: Extensions Event 2.0.4 Assignee: Carsten Ziegeler Execute jobs only on the instance they were created on -- Key: SLING-498 URL: https://issues.apache.org/jira/browse/SLING-498 Project: Sling Issue Type: New Feature Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 In a clustered environment a job might be executed by the first free node. Usually this should not cause any problems as the job event should contain all necessary information. However in some cases it might not be possible/feasible to put all information into the event. In these cases the job is usually only executable on the cluster node where the job has been created. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-498) Execute jobs only on the instance they were created on
[ https://issues.apache.org/jira/browse/SLING-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-498. -- Resolution: Fixed Add new property EventUtil.PROPERTY_JOB_RUN_LOCAL: if this is specified, the job is only executed on the instance it was created on. Execute jobs only on the instance they were created on -- Key: SLING-498 URL: https://issues.apache.org/jira/browse/SLING-498 Project: Sling Issue Type: New Feature Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 In a clustered environment a job might be executed by the first free node. Usually this should not cause any problems as the job event should contain all necessary information. However in some cases it might not be possible/feasible to put all information into the event. In these cases the job is usually only executable on the cluster node where the job has been created. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-628) Provide separate queues for specific jobs
Provide separate queues for specific jobs - Key: SLING-628 URL: https://issues.apache.org/jira/browse/SLING-628 Project: Sling Issue Type: New Feature Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 It would be great to be able to run specific jobs in a separate queue, instead of using the main queue for all jobs. This queue is running the jobs one after the other. -- 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=12625688#action_12625688 ] Carsten Ziegeler commented on SLING-624: Hi Mike, can you add the whole Sling-Initial-Content config you used here? And what exactly happended? 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] Reopened: (SLING-447) Schedule jobs n times
[ https://issues.apache.org/jira/browse/SLING-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reopened SLING-447: This is not a duplicate! This is for the scheduler while SLING-448 is for event. Schedule jobs n times - Key: SLING-447 URL: https://issues.apache.org/jira/browse/SLING-447 Project: Sling Issue Type: Improvement Components: Commons Scheduler Affects Versions: 2.0.0 Reporter: Carsten Ziegeler Priority: Minor Currently its only possible to schedule a job either ones or forever; it would be nice to schedule a job n times perhaps also starting at a given time etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-339) Implement job acknowledge
[ https://issues.apache.org/jira/browse/SLING-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-339: --- Priority: Blocker (was: Major) Affects Version/s: Extensions Event 2.0.2 Fix Version/s: Extensions Event 2.0.4 Assignee: Carsten Ziegeler Especially, if jobs can't be run in parallel, the first job without a processor stops further processing of these jobs as the finishedJob() method is never called. This can especially happen on startup, when the event listeners haven't been registered yet. Implement job acknowledge - Key: SLING-339 URL: https://issues.apache.org/jira/browse/SLING-339 Project: Sling Issue Type: Improvement Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Priority: Blocker Fix For: Extensions Event 2.0.4 Original Estimate: 0h Remaining Estimate: 0h Currently there is no acknowledge that someone is interested in processing a job. This results in the problem that jobs might end up locked in the repository for ever if there is noone interested in processing this kind of job. This couldbe solved by requiring that a job processor acknowledges the receival of a job and thereby indicates that it will process this job. This could also be used to deny other processors for this job. If a job is not acknowledged during a specified timeout, the job will be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-616) Provide better filter options to search for job
[ https://issues.apache.org/jira/browse/SLING-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626473#action_12626473 ] Carsten Ziegeler commented on SLING-616: I've added the properties templating. Provide better filter options to search for job --- Key: SLING-616 URL: https://issues.apache.org/jira/browse/SLING-616 Project: Sling Issue Type: New Feature Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 Currently it's only possible to search for all jobs, activate jobs and filter by an exact matching topics. This can be enhanced to allow pattern matching for the job topic - like the OSGi eventing does and to provide a map of properties that must match as well. This map acts like a search template. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-628) Provide separate queues for specific jobs
[ https://issues.apache.org/jira/browse/SLING-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-628. -- Resolution: Fixed Own job queues can be created by providing an additional queue name property. Provide separate queues for specific jobs - Key: SLING-628 URL: https://issues.apache.org/jira/browse/SLING-628 Project: Sling Issue Type: New Feature Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 It would be great to be able to run specific jobs in a separate queue, instead of using the main queue for all jobs. This queue is running the jobs one after the other. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-616) Provide better filter options to search for job
[ https://issues.apache.org/jira/browse/SLING-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-616. -- Resolution: Fixed For now, the properties template seems to be enough. In addition, one can distinguish between running jobs, queued jobs and all jobs. Provide better filter options to search for job --- Key: SLING-616 URL: https://issues.apache.org/jira/browse/SLING-616 Project: Sling Issue Type: New Feature Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 Currently it's only possible to search for all jobs, activate jobs and filter by an exact matching topics. This can be enhanced to allow pattern matching for the job topic - like the OSGi eventing does and to provide a map of properties that must match as well. This map acts like a search template. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-339) Implement job acknowledge
[ https://issues.apache.org/jira/browse/SLING-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626957#action_12626957 ] Carsten Ziegeler commented on SLING-339: When implementing an own job processor, it is advisable to use the EventUtil#processJob method. The first implementation will add the acknowledges to this method, so when this method is used, everything is fine. The background clean up thread will be enhanced to check for non acknowledge jobs and mark them as failed. (calling finish with failed value) Implement job acknowledge - Key: SLING-339 URL: https://issues.apache.org/jira/browse/SLING-339 Project: Sling Issue Type: Improvement Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Priority: Blocker Fix For: Extensions Event 2.0.4 Original Estimate: 0h Remaining Estimate: 0h Currently there is no acknowledge that someone is interested in processing a job. This results in the problem that jobs might end up locked in the repository for ever if there is noone interested in processing this kind of job. This couldbe solved by requiring that a job processor acknowledges the receival of a job and thereby indicates that it will process this job. This could also be used to deny other processors for this job. If a job is not acknowledged during a specified timeout, the job will be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-635) Stop thread for own job queues when it is unused
Stop thread for own job queues when it is unused Key: SLING-635 URL: https://issues.apache.org/jira/browse/SLING-635 Project: Sling Issue Type: Improvement Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 The background thread should check if a job queue thread has been unused for a longer time and then stop it. This avoids too many idle threads. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-637) Add regexp based mapping rules
Add regexp based mapping rules -- Key: SLING-637 URL: https://issues.apache.org/jira/browse/SLING-637 Project: Sling Issue Type: New Feature Components: JCR Resource Affects Versions: JCR Resource 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.4 Currently the url mapping in the jcr resolver is path based. it would be nice to provide some regexp rewriting rules, for instance to beautify urls. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-637) Add regexp based mapping rules
[ https://issues.apache.org/jira/browse/SLING-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627482#action_12627482 ] Carsten Ziegeler commented on SLING-637: Hmm, no I don't think that this could be used for SLING-249, sorry. The reg exp are executed on the resulting path and are not taking any additional information into account, like host etc. Add regexp based mapping rules -- Key: SLING-637 URL: https://issues.apache.org/jira/browse/SLING-637 Project: Sling Issue Type: New Feature Components: JCR Resource Affects Versions: JCR Resource 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.4 Currently the url mapping in the jcr resolver is path based. it would be nice to provide some regexp rewriting rules, for instance to beautify urls. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-637) Add regexp based mapping rules
[ https://issues.apache.org/jira/browse/SLING-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-637. -- Resolution: Fixed Add regexp for resource resolution. All configured regexp are applied before the mapping is tested. Add regexp based mapping rules -- Key: SLING-637 URL: https://issues.apache.org/jira/browse/SLING-637 Project: Sling Issue Type: New Feature Components: JCR Resource Affects Versions: JCR Resource 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.4 Currently the url mapping in the jcr resolver is path based. it would be nice to provide some regexp rewriting rules, for instance to beautify urls. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-640) Add provider for status information about timed events
Add provider for status information about timed events -- Key: SLING-640 URL: https://issues.apache.org/jira/browse/SLING-640 Project: Sling Issue Type: Improvement Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 Currently it is only possible to start and stop timed events (by sending events) A new interface TimedEventStatusProvider should be added which allows to query if something is scheduled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-640) Add provider for status information about timed events
[ https://issues.apache.org/jira/browse/SLING-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-640. -- Resolution: Fixed Added a simple provider which can be queried for scheduled events and which can be used to cancel events. Add provider for status information about timed events -- Key: SLING-640 URL: https://issues.apache.org/jira/browse/SLING-640 Project: Sling Issue Type: Improvement Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 Currently it is only possible to start and stop timed events (by sending events) A new interface TimedEventStatusProvider should be added which allows to query if something is scheduled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-602) ValueMap#get(java.lang.String name, T defaultValue) should support Integer
[ https://issues.apache.org/jira/browse/SLING-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-602: --- Component/s: JCR Resource Affects Version/s: JCR Resource 2.0.4 ValueMap#get(java.lang.String name, T defaultValue) should support Integer -- Key: SLING-602 URL: https://issues.apache.org/jira/browse/SLING-602 Project: Sling Issue Type: Wish Components: JCR Resource Affects Versions: JCR Resource 2.0.4 Environment: Windows XP, Sling Version 2.0.3-incubator-SNAPSHOT (running of Communiqué5) Reporter: Andreas Vogl Priority: Minor Hi, Working with the sling API, I've been using the ValueMap class rather frequently: org.apache.sling.api.resource.ValueMap I noticed that the type java.util.Lang is supported for the getter methods, but the type java.util.Integer is apparently not supported. The getter methods i am referring to: T T get(java.lang.String name, java.lang.ClassT type) T T get(java.lang.String name, T defaultValue) Personally I would find it very convenient to be able to pass integers as default values and also get an integer as return type. Apart from the convenience aspect, the lack of Integer support is really a source for bugs: It's intuitive to pass Integers - it will compile fine but not work in the end. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-245) After reinstalling sling core, server shutdown hangs
[ https://issues.apache.org/jira/browse/SLING-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-245. -- Resolution: Fixed Fix Version/s: 2.0.1 The corresponding bug in Apache Felix has been fixed a long time ago, we haven't heard anything new about this, so I'll close the bug. After reinstalling sling core, server shutdown hangs Key: SLING-245 URL: https://issues.apache.org/jira/browse/SLING-245 Project: Sling Issue Type: Bug Components: Engine Reporter: Tobias Bocanegra Fix For: 2.0.1 Attachments: threaddump.txt i'll attach the stacktrace -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-45) Sling leaks PermSpace memory on restart of the webapp
[ https://issues.apache.org/jira/browse/SLING-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-45. - Resolution: Fixed Fix Version/s: 2.0.0 This bug has been filed against early Sling, so I'll close it. If the problem still exists, please open a new bug with the correct version etc. Sling leaks PermSpace memory on restart of the webapp - Key: SLING-45 URL: https://issues.apache.org/jira/browse/SLING-45 Project: Sling Issue Type: Improvement Components: Engine Reporter: David Nuescheler Priority: Minor Fix For: 2.0.0 After restarting the Sling webapp a number of times in a Servlet Container I ran out of PermSpace. It seems like some classes or other objects are not entirely removed upon restart of the webapp. Unfortunately I don't have any detailed memory profiler dump, but I think it should be reasonably evident once someone attaches a memory profiler and restarts the webapp. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-650) Support for vanity urls
Support for vanity urls --- Key: SLING-650 URL: https://issues.apache.org/jira/browse/SLING-650 Project: Sling Issue Type: New Feature Components: JCR Resource Affects Versions: JCR Resource 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.4 It would be nice to have support for vanity urls: these are urls that do not directly point to a resource. Instead it is possible to give a resource a pretty (vanity) url which can be used to address this resource. Example: /a/b/x/y/myPage You can either address this by /a/b/x/y/myPage or by /products This can be done by adding a new mixin: sling:VanityUrl which has two properties: vanityUrl (which has in the example above the value /products) and redirect which is a boolean indication if a redirect should be done or if the content should be directly displayed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-650) Support for vanity urls
[ https://issues.apache.org/jira/browse/SLING-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-650: --- Component/s: Servlets Get Affects Version/s: Servlets Get 2.0.2 Fix Version/s: Servlets Get 2.0.4 Support for vanity urls --- Key: SLING-650 URL: https://issues.apache.org/jira/browse/SLING-650 Project: Sling Issue Type: New Feature Components: JCR Resource, Servlets Get Affects Versions: JCR Resource 2.0.2, Servlets Get 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.4, Servlets Get 2.0.4 It would be nice to have support for vanity urls: these are urls that do not directly point to a resource. Instead it is possible to give a resource a pretty (vanity) url which can be used to address this resource. Example: /a/b/x/y/myPage You can either address this by /a/b/x/y/myPage or by /products This can be done by adding a new mixin: sling:VanityUrl which has two properties: vanityUrl (which has in the example above the value /products) and redirect which is a boolean indication if a redirect should be done or if the content should be directly displayed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-650) Support for vanity urls
[ https://issues.apache.org/jira/browse/SLING-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-650. -- Resolution: Fixed Implemented with an additional priority field which is used if several resources use the same vanity url. The one with the highest priority is used then. Support for vanity urls --- Key: SLING-650 URL: https://issues.apache.org/jira/browse/SLING-650 Project: Sling Issue Type: New Feature Components: JCR Resource, Servlets Get Affects Versions: JCR Resource 2.0.2, Servlets Get 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.4, Servlets Get 2.0.4 It would be nice to have support for vanity urls: these are urls that do not directly point to a resource. Instead it is possible to give a resource a pretty (vanity) url which can be used to address this resource. Example: /a/b/x/y/myPage You can either address this by /a/b/x/y/myPage or by /products This can be done by adding a new mixin: sling:VanityUrl which has two properties: vanityUrl (which has in the example above the value /products) and redirect which is a boolean indication if a redirect should be done or if the content should be directly displayed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-528) ServletException on request for synthtic resource
[ https://issues.apache.org/jira/browse/SLING-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-528. -- Resolution: Won't Fix Fix Version/s: Servlets Get 2.0.4 I'll close this as the behaviour in the get servlets has changed. If there is still an issue please open a new bug. ServletException on request for synthtic resource - Key: SLING-528 URL: https://issues.apache.org/jira/browse/SLING-528 Project: Sling Issue Type: Bug Components: Servlets Get Reporter: christian Assignee: Felix Meschberger Fix For: Servlets Get 2.0.4 Have a Resource at path /synthetic Requesting this resource SlingDefaultGetServlet throws an ServletException with the message path=/synthetic does not adapt to a Node or a Property. This is thrown by the PlainTextRendererSerlvet, which expects a JCR Resource. I would suggest to fail gracefully. Like rendering the ResourceMetadata -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-393) default renderer for .xml
[ https://issues.apache.org/jira/browse/SLING-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-393: -- Assignee: Carsten Ziegeler default renderer for .xml - Key: SLING-393 URL: https://issues.apache.org/jira/browse/SLING-393 Project: Sling Issue Type: Improvement Components: Servlets Get Reporter: Michael Marth Assignee: Carsten Ziegeler Priority: Minor I would like to suggest a default renderer for .xml requests, similar to the .json renderer that exists already. This would allow zero-config remote access for clients that do not understand json, e.g. desktop apps. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-393) default renderer for .xml
[ https://issues.apache.org/jira/browse/SLING-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12629814#action_12629814 ] Carsten Ziegeler commented on SLING-393: I've implemented a first version which does not support depth (if we need it, we can add it later on anyway) As I don't think that round-tripping is that important and as the docview is easier for later processing, I go with docview as default. default renderer for .xml - Key: SLING-393 URL: https://issues.apache.org/jira/browse/SLING-393 Project: Sling Issue Type: Improvement Components: Servlets Get Reporter: Michael Marth Assignee: Carsten Ziegeler Priority: Minor I would like to suggest a default renderer for .xml requests, similar to the .json renderer that exists already. This would allow zero-config remote access for clients that do not understand json, e.g. desktop apps. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-393) default renderer for .xml
[ https://issues.apache.org/jira/browse/SLING-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-393: --- Affects Version/s: Servlets Get 2.0.2 Fix Version/s: Servlets Get 2.0.4 default renderer for .xml - Key: SLING-393 URL: https://issues.apache.org/jira/browse/SLING-393 Project: Sling Issue Type: Improvement Components: Servlets Get Affects Versions: Servlets Get 2.0.2 Reporter: Michael Marth Assignee: Carsten Ziegeler Priority: Minor Fix For: Servlets Get 2.0.4 I would like to suggest a default renderer for .xml requests, similar to the .json renderer that exists already. This would allow zero-config remote access for clients that do not understand json, e.g. desktop apps. -- 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=12639137#action_12639137 ] Carsten Ziegeler commented on SLING-694: You're assuming correctly that the content loader is working on folders as the basic input, therefore something like CQ-INF/content/etc/designs/;overwrite:=true;path:=/etc/designs with just xyz.json in CQ-INF/content/etc/designs/ should do the trick I think. 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] Closed: (SLING-695) Optimize bundle installation and update
[ https://issues.apache.org/jira/browse/SLING-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-695. -- Resolution: Fixed JUnit tests work and manual tests works Optimize bundle installation and update --- Key: SLING-695 URL: https://issues.apache.org/jira/browse/SLING-695 Project: Sling Issue Type: Improvement Components: JCR Install Affects Versions: JCR Install 2.0.4 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Install 2.0.4 Removed unnecessary resolveBundles and optimized package refreshs Bundles are now directly resolved inside processResourceQueue after installation and refresh packages is called at the end of processResourceQueue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-699) Bundles should be installed, updated started one after the other
Bundles should be installed, updated started one after the other Key: SLING-699 URL: https://issues.apache.org/jira/browse/SLING-699 Project: Sling Issue Type: Improvement Components: JCR Install Affects Versions: JCR Install 2.0.4 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Install 2.0.4 Currently the bundles are installed/updated in one thread one after the other, while another thread asynchronously starts and resolves the bundles. To avoid possible start up problems in the framework this should be done synchronously -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-699) Bundles should be installed, updated started one after the other
[ https://issues.apache.org/jira/browse/SLING-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12640120#action_12640120 ] Carsten Ziegeler commented on SLING-699: I synchronized the two methods in question and additionally bundles are now only updated if the new version number is really higher than the installed version number. I'll leave the bug open to further watch this problem. Bundles should be installed, updated started one after the other Key: SLING-699 URL: https://issues.apache.org/jira/browse/SLING-699 Project: Sling Issue Type: Improvement Components: JCR Install Affects Versions: JCR Install 2.0.4 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Install 2.0.4 Currently the bundles are installed/updated in one thread one after the other, while another thread asynchronously starts and resolves the bundles. To avoid possible start up problems in the framework this should be done synchronously -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-697) enhance ResourceResolver#findResources() signature to support typing
[ https://issues.apache.org/jira/browse/SLING-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12640443#action_12640443 ] Carsten Ziegeler commented on SLING-697: (the method name should actually be adaptResourcesTo or just adaptTo) enhance ResourceResolver#findResources() signature to support typing Key: SLING-697 URL: https://issues.apache.org/jira/browse/SLING-697 Project: Sling Issue Type: Improvement Components: API Reporter: Dominique Jäggi Priority: Minor it would be nice to be able to receive a typed iterator when using ResourceResolver#findResources(): final IteratorMyPojo iterator = resourceResolver.findResources(statement, Query.XPATH, MyPojo.class); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-701) HtmlResponse should replace all place holders
HtmlResponse should replace all place holders - Key: SLING-701 URL: https://issues.apache.org/jira/browse/SLING-701 Project: Sling Issue Type: Bug Components: API Affects Versions: API 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: API 2.0.4 Currently the HtlmResponse leaves the placeholders in the response if there is no value for a placeholder. Instead it should remove the placeholder as otherwise the client has to take extra care to detect if a value is really missing -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-700) Send notification event when a job is cancelled
[ https://issues.apache.org/jira/browse/SLING-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-700: --- Fix Version/s: (was: Extensions Event 2.0.4) Send notification event when a job is cancelled --- Key: SLING-700 URL: https://issues.apache.org/jira/browse/SLING-700 Project: Sling Issue Type: New Feature Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler If a job is cancelled currently no notification is sent. A new job cancelled event should be sent if the job is cancelled through the ui or removed from the repository directly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-701) HtmlResponse should replace all place holders
[ https://issues.apache.org/jira/browse/SLING-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-701. -- Resolution: Fixed The placeholder is now always removed. If the corresponding property value is not available it is replaced with an empty string Fixed in Revision 706296 HtmlResponse should replace all place holders - Key: SLING-701 URL: https://issues.apache.org/jira/browse/SLING-701 Project: Sling Issue Type: Bug Components: API Affects Versions: API 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: API 2.0.4 Currently the HtlmResponse leaves the placeholders in the response if there is no value for a placeholder. Instead it should remove the placeholder as otherwise the client has to take extra care to detect if a value is really missing -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-710) Scheduler should user service id for registering services
Scheduler should user service id for registering services - Key: SLING-710 URL: https://issues.apache.org/jira/browse/SLING-710 Project: Sling Issue Type: Bug Components: Commons Scheduler Affects Versions: Commons Scheduler 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Commons Scheduler 2.0.4 Currently the scheduler uses the pid to register a service. In the case of an bundle update, the new service has the same pid as the old service. But as the bind method with the new service is invoked before the unbind with the old service, the scheduler stops the previously scheduled new service. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-710) Scheduler should user service id for registering services
[ https://issues.apache.org/jira/browse/SLING-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-710. -- Resolution: Fixed Fixed in r708122 by appending the service pid to the pid or the provided name. Scheduler should user service id for registering services - Key: SLING-710 URL: https://issues.apache.org/jira/browse/SLING-710 Project: Sling Issue Type: Bug Components: Commons Scheduler Affects Versions: Commons Scheduler 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Commons Scheduler 2.0.4 Currently the scheduler uses the pid to register a service. In the case of an bundle update, the new service has the same pid as the old service. But as the bind method with the new service is invoked before the unbind with the old service, the scheduler stops the previously scheduled new service. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-339) Implement job acknowledge
[ https://issues.apache.org/jira/browse/SLING-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-339. -- Resolution: Fixed All started jobs are queried after a configured time, if someone started to process them. If not, they're requeued. If more than one job processor wants to process a job, only the first one is used to notify the job event handler of success/failure. Implement job acknowledge - Key: SLING-339 URL: https://issues.apache.org/jira/browse/SLING-339 Project: Sling Issue Type: Improvement Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Priority: Blocker Fix For: Extensions Event 2.0.4 Original Estimate: 0h Remaining Estimate: 0h Currently there is no acknowledge that someone is interested in processing a job. This results in the problem that jobs might end up locked in the repository for ever if there is noone interested in processing this kind of job. This couldbe solved by requiring that a job processor acknowledges the receival of a job and thereby indicates that it will process this job. This could also be used to deny other processors for this job. If a job is not acknowledged during a specified timeout, the job will be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-714) Make jcr property adaptable to array types
Make jcr property adaptable to array types -- Key: SLING-714 URL: https://issues.apache.org/jira/browse/SLING-714 Project: Sling Issue Type: Improvement Components: JCR Resource Affects Versions: JCR Resource 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.4 The jcr property is currently only adaptable to single values. If the property is a multi value property it would be nice to adapt this to arrays like String[] etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-714) Make jcr property adaptable to array types
[ https://issues.apache.org/jira/browse/SLING-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-714. -- Resolution: Fixed adaptTo on a jcr property now supports String[], Boolean[], Long[], Double[], Calendar[], and Value[] Make jcr property adaptable to array types -- Key: SLING-714 URL: https://issues.apache.org/jira/browse/SLING-714 Project: Sling Issue Type: Improvement Components: JCR Resource Affects Versions: JCR Resource 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.4 The jcr property is currently only adaptable to single values. If the property is a multi value property it would be nice to adapt this to arrays like String[] etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-753) Create new launchpad package project
[ https://issues.apache.org/jira/browse/SLING-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12652722#action_12652722 ] Carsten Ziegeler commented on SLING-753: What about using deployment packages? Create new launchpad package project Key: SLING-753 URL: https://issues.apache.org/jira/browse/SLING-753 Project: Sling Issue Type: Improvement Components: Launchpad Launcher Reporter: Felix Meschberger Currently the launchpad/app project prepares a runnable jar package from the launchpad/base project (providing the launcher) and all the bundles required for inclusion. The launchpad/webapp project takes the launchpad/app package and modifies it by adding servlet container integration and removing the embedded servlet container. This construct creates a complicated dependency in the webapp project on app internals. It would probably be better to have a launchpad/package project, which just packages everything which web app and app have in common and have the app and webapp projects extend the package by adding additional stuff required for the specific environment (standalone vs. servlet container). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-756) Bundle startup becomes very slow with many bundles present
[ https://issues.apache.org/jira/browse/SLING-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12653242#action_12653242 ] Carsten Ziegeler commented on SLING-756: Not sure if this is the problem, but I think resolving has improved in the latest Felix releases, so upgrading to 1.4.x might already make a difference Bundle startup becomes very slow with many bundles present -- Key: SLING-756 URL: https://issues.apache.org/jira/browse/SLING-756 Project: Sling Issue Type: Bug Components: JCR Install Reporter: Bertrand Delacretaz When running the jcrinstall integration tests with a few hundreds of very simple bundles, the bundle.start call in the BundleResourceProcessor class becomes very slow. With a few bundles it takes only a few milliseconds, and goes up to the 500 msec range with about 500 installed bundles. Seems like most of that time is spent in the Felix R4SearchPolicyCore.resolve() method, but I haven't investigated that in detail yet. To reproduce, run mvn clean install in extensions/jcrinstall/testing, with these parameters: -D sling.test.scale.factor = 20 -D sling.test.bundles.wait.seconds = 200 With these values, the StopAndChangeBundlesTest installs 140 bundles by copying them into the repository, disables jcrinstall, replaces the bundles with 260 new ones and reactivates jcrinstall. When reactivated, jcrinstall uninistalls the 140 bundles and then installs and starts the 260 new ones - this is when the bundle.start becomes very slow. All bundles are clones of the extensions/jcrinstall/testbundles/observer bundle, same code but unique bundle symbolic name and name. This causes warnings from the Felix framework as all bundle clones contain a component with the same name. I don't think that's related to the long start time though. As it seems like the problem has to do with resolving the bundle, here are the package exports/imports of the test bundle: exports: none imports: javax.jcr,version=1.0.0 from org.apache.sling.jcr.api (16) javax.jcr.observation,version=1.0.0 from org.apache.sling.jcr.api (16) org.apache.sling.jcr.api,version=2.0.3.incubator-SNAPSHOT from org.apache.sling.jcr.api (16) org.osgi.framework,version=1.4.0 from System Bundle (0) org.osgi.service.component,version=1.0.0 from System Bundle (0) org.slf4j,version=1.5.2 from org.apache.sling.commons.log (19) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-758) Thread Pool Policy is always abort
Thread Pool Policy is always abort -- Key: SLING-758 URL: https://issues.apache.org/jira/browse/SLING-758 Project: Sling Issue Type: Bug Components: Commons Threads Affects Versions: Commons Threads 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Commons Threads 2.0.4 Regardless of the thread pool block policy, always the abort handler is used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-758) Thread Pool Policy is always abort
[ https://issues.apache.org/jira/browse/SLING-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-758. -- Resolution: Fixed Fixed in revision 723309 Thread Pool Policy is always abort -- Key: SLING-758 URL: https://issues.apache.org/jira/browse/SLING-758 Project: Sling Issue Type: Bug Components: Commons Threads Affects Versions: Commons Threads 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Commons Threads 2.0.4 Regardless of the thread pool block policy, always the abort handler is used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-757) changing default access rights not possible
[ https://issues.apache.org/jira/browse/SLING-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12653311#action_12653311 ] Carsten Ziegeler commented on SLING-757: I guess this is an old bug of the webconsole which is fixed in newer versions. Which webconsole version are you using? changing default access rights not possible --- Key: SLING-757 URL: https://issues.apache.org/jira/browse/SLING-757 Project: Sling Issue Type: Bug Environment: vista Reporter: Michael Marth Trying to change the default access rights is not possible in the Sling console. Go to http://localhost:/system/console/configMgr/org.apache.sling.engine.impl.auth.SlingAuthenticator Untick auth.annonymous.name, hit save - result: option still ticked (btw: auth.annonymous.name is a bit cryptic :) ) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-757) changing default access rights not possible
[ https://issues.apache.org/jira/browse/SLING-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12653323#action_12653323 ] Carsten Ziegeler commented on SLING-757: There is no official release yet of the sling web console, so that's why we still refer to the old version in sling. We don't want to depend on snapshots...but maybe that's the better solution for know. However, can you try with the latest webconsole from trunk if that solves your problem? changing default access rights not possible --- Key: SLING-757 URL: https://issues.apache.org/jira/browse/SLING-757 Project: Sling Issue Type: Bug Environment: vista Reporter: Michael Marth Trying to change the default access rights is not possible in the Sling console. Go to http://localhost:/system/console/configMgr/org.apache.sling.engine.impl.auth.SlingAuthenticator Untick auth.annonymous.name, hit save - result: option still ticked (btw: auth.annonymous.name is a bit cryptic :) ) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-759) Don't synchronize on jcr sessions
Don't synchronize on jcr sessions - Key: SLING-759 URL: https://issues.apache.org/jira/browse/SLING-759 Project: Sling Issue Type: Bug Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Engine 2.0.4 As some jcr implementations synchronize themselves on the jcr session it's better to not base own sync code on a session. (However as the session is wrapped in Sling this shouldn't be a problem, but as soon as it is not wrapped anymore, it becomes one, so it's better to avoid this potential problem upfront) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-759) Don't synchronize on jcr sessions
[ https://issues.apache.org/jira/browse/SLING-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-759. -- Resolution: Fixed Fixed in revision723362 Don't synchronize on jcr sessions - Key: SLING-759 URL: https://issues.apache.org/jira/browse/SLING-759 Project: Sling Issue Type: Bug Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Engine 2.0.4 As some jcr implementations synchronize themselves on the jcr session it's better to not base own sync code on a session. (However as the session is wrapped in Sling this shouldn't be a problem, but as soon as it is not wrapped anymore, it becomes one, so it's better to avoid this potential problem upfront) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-764) Deadlock when more than three job queues are used.
Deadlock when more than three job queues are used. -- Key: SLING-764 URL: https://issues.apache.org/jira/browse/SLING-764 Project: Sling Issue Type: Bug Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 The current thread pool config has a limit of 10 threads with an unbounded queue, in this case if 10 threads are running and another one is about to start, this one gets queue. If more job queues are added, this means more permanent running threads. As soon as there are 10 permanent running threads, no new thread is freed which means the queue can never get empty. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-764) Deadlock when more than three job queues are used.
[ https://issues.apache.org/jira/browse/SLING-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-764. -- Resolution: Fixed Fixed in revision 724794 Add an own thread pool service and change configuration with a fixed queue. By using a fixed queue, the max pool size is used and the pool growth. In addition the minimum size of the pool is increased to all ootb more parallel job queues. Deadlock when more than three job queues are used. -- Key: SLING-764 URL: https://issues.apache.org/jira/browse/SLING-764 Project: Sling Issue Type: Bug Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 The current thread pool config has a limit of 10 threads with an unbounded queue, in this case if 10 threads are running and another one is about to start, this one gets queue. If more job queues are added, this means more permanent running threads. As soon as there are 10 permanent running threads, no new thread is freed which means the queue can never get empty. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-766) Initial Content should not be removed on bundle stop
[ https://issues.apache.org/jira/browse/SLING-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-766: --- Fix Version/s: (was: JCR Jackrabbit Server 2.0.4) JCR Contentloader 2.0.4 Initial Content should not be removed on bundle stop Key: SLING-766 URL: https://issues.apache.org/jira/browse/SLING-766 Project: Sling Issue Type: Bug Components: JCR Contentloader Affects Versions: JCR Contentloader 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Contentloader 2.0.4 Currently the initial content is removed on a bundle stop - while this is logically ok (content is installed on bundle start, and content shouldn't be available when bundle is not running anymore), this creates problems when the server is shutdown as the bundle is stopped and therefore removes all content on shutdown. (of course the content is added again on server startup) Therefore it's better to remove the content only when the bundle is uninstalled. As a consequence of not uninstalling the initial content anymore when the bundle is stopped, content update when the bundle is updated must be adapted and take care on properly replacing old content with new 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-771) Upgrade to latest Felix framework release
Upgrade to latest Felix framework release - Key: SLING-771 URL: https://issues.apache.org/jira/browse/SLING-771 Project: Sling Issue Type: Improvement Components: Launchpad Launcher Affects Versions: Launchpad Base 2.0.2 Reporter: Carsten Ziegeler Fix For: Launchpad Base 2.0.4 As discussed in the mailing list updating to the latest Felix framework should bring some improvements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-771) Upgrade to latest Felix framework release
[ https://issues.apache.org/jira/browse/SLING-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-771. -- Resolution: Duplicate This is a duplicate of SLING-712 Upgrade to latest Felix framework release - Key: SLING-771 URL: https://issues.apache.org/jira/browse/SLING-771 Project: Sling Issue Type: Improvement Components: Launchpad Launcher Affects Versions: Launchpad Base 2.0.2 Reporter: Carsten Ziegeler Fix For: Launchpad Base 2.0.4 As discussed in the mailing list updating to the latest Felix framework should bring some improvements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-766) Initial Content should not be removed on bundle stop
[ https://issues.apache.org/jira/browse/SLING-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12656985#action_12656985 ] Carsten Ziegeler commented on SLING-766: Changed this in revision 727047: Don't uninstall content when bundle is stopped. The content is now only uninstalled when the bundle is uninstalled. During installation a string array containing all paths that will be removed later on is collected which makes the uninstall easier. Also refactored the classes and packages a little bit. I'll leave the bug open for further testing Initial Content should not be removed on bundle stop Key: SLING-766 URL: https://issues.apache.org/jira/browse/SLING-766 Project: Sling Issue Type: Bug Components: JCR Contentloader Affects Versions: JCR Contentloader 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Contentloader 2.0.4 Currently the initial content is removed on a bundle stop - while this is logically ok (content is installed on bundle start, and content shouldn't be available when bundle is not running anymore), this creates problems when the server is shutdown as the bundle is stopped and therefore removes all content on shutdown. (of course the content is added again on server startup) Therefore it's better to remove the content only when the bundle is uninstalled. As a consequence of not uninstalling the initial content anymore when the bundle is stopped, content update when the bundle is updated must be adapted and take care on properly replacing old content with new 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-782) Commons OSGi depends on Sling API
Commons OSGi depends on Sling API - Key: SLING-782 URL: https://issues.apache.org/jira/browse/SLING-782 Project: Sling Issue Type: Bug Components: Commons OSGi Affects Versions: Commons OSGi 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Commons OSGi 2.0.4 Commons OSGi has an unused dep to the Sling API - commons should be independent from everything else in Sling -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-782) Commons OSGi depends on Sling API
[ https://issues.apache.org/jira/browse/SLING-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-782. -- Resolution: Fixed Removed in revision 727341 Commons OSGi depends on Sling API - Key: SLING-782 URL: https://issues.apache.org/jira/browse/SLING-782 Project: Sling Issue Type: Bug Components: Commons OSGi Affects Versions: Commons OSGi 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Commons OSGi 2.0.4 Commons OSGi has an unused dep to the Sling API - commons should be independent from everything else in Sling -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-784) SlingPostServlet does not allow setting mixin types on existing nodes
[ https://issues.apache.org/jira/browse/SLING-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12657731#action_12657731 ] Carsten Ziegeler commented on SLING-784: While this sounds reasonable, I'm a little bit worried about the practical aspect. If I just want to add one mixin, I need to know all applied mixins and post them again just to be able to do this simple stuff. I'm all for handling this in the same way as we do with props, so what doing like outlined above and adding support for ./jcr:mixinty...@add=mixins which just adds the mixins? SlingPostServlet does not allow setting mixin types on existing nodes - Key: SLING-784 URL: https://issues.apache.org/jira/browse/SLING-784 Project: Sling Issue Type: Improvement Components: Servlets Post Reporter: Alexander Saar Attachments: post-servlet-change-mixins.diff the current implementation of the sling POST servlet allows to specify mixin node types when a new node is created, but it is not possible to add/change mixin node types of existing nodes. I suggest to add this funtionality because it is a common use case that you want to set properties which are defined in mixin node types (eg adding some meta data to a file). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-793) Improve property file includes
Improve property file includes -- Key: SLING-793 URL: https://issues.apache.org/jira/browse/SLING-793 Project: Sling Issue Type: Improvement Affects Versions: Launchpad Base 2.0.2 Reporter: Carsten Ziegeler Fix For: Launchpad Base 2.0.4 To include own property files with startup information, an include statement needs to be added to the sling.properties file. An exception is the jcr-client.properties file which is a hard-coded include in launchpad. It would be nice to be able to add own property files by convention instead of configuration. This would allow to use the sling.properties from launchpad base untouched by just adding additional files. I think the convention could use some filename conventions, so all files names *-sling.properties are included. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-393) default renderer for .xml
[ https://issues.apache.org/jira/browse/SLING-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-393. -- Resolution: Fixed As we now have xml rendering, I'll close this bug. default renderer for .xml - Key: SLING-393 URL: https://issues.apache.org/jira/browse/SLING-393 Project: Sling Issue Type: Improvement Components: Servlets Get Affects Versions: Servlets Get 2.0.2 Reporter: Michael Marth Assignee: Carsten Ziegeler Priority: Minor Fix For: Servlets Get 2.0.4 I would like to suggest a default renderer for .xml requests, similar to the .json renderer that exists already. This would allow zero-config remote access for clients that do not understand json, e.g. desktop apps. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-796) Corrupt json output with resources from a bundle or other places
Corrupt json output with resources from a bundle or other places Key: SLING-796 URL: https://issues.apache.org/jira/browse/SLING-796 Project: Sling Issue Type: Bug Components: Servlets Get Affects Versions: Servlets Get 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Servlets Get 2.0.4 When outputting json through the JsonResourceWriter, the resource is tried to adapted to a ValueMap, Map and as a last resort String. If the resource is can't be adapted to any of the three, only the key is outputted with no value, creating a corrupt json. As in this case there is nothing one can really output, I think it makes sense to just output an empty object. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-796) Corrupt json output with resources from a bundle or other places
[ https://issues.apache.org/jira/browse/SLING-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12659066#action_12659066 ] Carsten Ziegeler commented on SLING-796: I've applied a patch in revision 729281 Corrupt json output with resources from a bundle or other places Key: SLING-796 URL: https://issues.apache.org/jira/browse/SLING-796 Project: Sling Issue Type: Bug Components: Servlets Get Affects Versions: Servlets Get 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Servlets Get 2.0.4 When outputting json through the JsonResourceWriter, the resource is tried to adapted to a ValueMap, Map and as a last resort String. If the resource is can't be adapted to any of the three, only the key is outputted with no value, creating a corrupt json. As in this case there is nothing one can really output, I think it makes sense to just output an empty object. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-797) EventUtil.getNodePropertyValue wrong check for basic types
[ https://issues.apache.org/jira/browse/SLING-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-797: --- Component/s: JCR Resource Affects Version/s: JCR Resource 2.0.2 Fix Version/s: Extensions Event 2.0.4 JCR Resource 2.0.4 Assignee: Carsten Ziegeler Adding jcr resource as the JcrResourceUtil has the same code in the createValue() method. EventUtil.getNodePropertyValue wrong check for basic types -- Key: SLING-797 URL: https://issues.apache.org/jira/browse/SLING-797 Project: Sling Issue Type: Bug Components: Event, JCR Resource Affects Versions: JCR Resource 2.0.2, Extensions Event 2.0.2 Reporter: Tobias Bocanegra Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.4, Extensions Event 2.0.4 Attachments: EventUtil-r712058.patch The type checks in getNodePropertyValue() are the wrong way around and never find the respective JCR property type. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-797) EventUtil.getNodePropertyValue wrong check for basic types
[ https://issues.apache.org/jira/browse/SLING-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12660039#action_12660039 ] Carsten Ziegeler commented on SLING-797: Hi Tobi, while the checks where actually really wrong this only had an influence on calendar objects. Thanks for your patch - I applied it in revision 730337 - please cross check and close this bug. Thanks EventUtil.getNodePropertyValue wrong check for basic types -- Key: SLING-797 URL: https://issues.apache.org/jira/browse/SLING-797 Project: Sling Issue Type: Bug Components: Event, JCR Resource Affects Versions: JCR Resource 2.0.2, Extensions Event 2.0.2 Reporter: Tobias Bocanegra Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.4, Extensions Event 2.0.4 Attachments: EventUtil-r712058.patch The type checks in getNodePropertyValue() are the wrong way around and never find the respective JCR property type. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-797) EventUtil.getNodePropertyValue wrong check for basic types
[ https://issues.apache.org/jira/browse/SLING-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-797. Resolution: Fixed EventUtil.getNodePropertyValue wrong check for basic types -- Key: SLING-797 URL: https://issues.apache.org/jira/browse/SLING-797 Project: Sling Issue Type: Bug Components: Event, JCR Resource Affects Versions: JCR Resource 2.0.2, Extensions Event 2.0.2 Reporter: Tobias Bocanegra Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.4, Extensions Event 2.0.4 Attachments: EventUtil-r712058.patch The type checks in getNodePropertyValue() are the wrong way around and never find the respective JCR property type. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-798) Create filesystem provider configurations for initial content on sling install
Create filesystem provider configurations for initial content on sling install -- Key: SLING-798 URL: https://issues.apache.org/jira/browse/SLING-798 Project: Sling Issue Type: New Feature Components: Maven Plugins Affects Versions: Maven Sling Plugin 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Maven Sling Plugin 2.0.4 The maven sling plugin could be improved to generate file system provider factory configurations for initial content. During a sling:install, the plugin will read the generated manifest, extract the initial content directives and uses them to POST new configurations to the Felix webconsole -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-798) Create filesystem provider configurations for initial content on sling install
[ https://issues.apache.org/jira/browse/SLING-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12660299#action_12660299 ] Carsten Ziegeler commented on SLING-798: Revision 730701 contains a first version which posts new configs on each sling:install. Initial content entries can be ignored by setting the directive maven:mount:=false for the entry. The whole procedure can be disabled by setting -D.sling.mountByFS=false The current approach allows to generate a config and mount scripts contained in the project through the fs provider. The scripts can then be edited in the IDE and changes are applied immediately. This initial version has some drawbacks, one of them is that each invocation creates new configs, old configs are never removed etc. Create filesystem provider configurations for initial content on sling install -- Key: SLING-798 URL: https://issues.apache.org/jira/browse/SLING-798 Project: Sling Issue Type: New Feature Components: Maven Plugins Affects Versions: Maven Sling Plugin 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Maven Sling Plugin 2.0.4 The maven sling plugin could be improved to generate file system provider factory configurations for initial content. During a sling:install, the plugin will read the generated manifest, extract the initial content directives and uses them to POST new configurations to the Felix webconsole -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-799) Job Folder is not ordered and results in unordered queue
[
https://issues.apache.org/jira/browse/SLING-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12660352#action_12660352
]
Carsten Ziegeler commented on SLING-799:
Not 100% sure (I've to check the code), but I think the job handler does not
rely on the order of the nodes in the repository.
The job handler holds the queues in memory in the correct order. In case of a
restart the query fetches the nodes in the correct order by using a sorting on
a property.
However, an ordered folder shouldn't hurt.
Job Folder is not ordered and results in unordered queue
Key: SLING-799
URL: https://issues.apache.org/jira/browse/SLING-799
Project: Sling
Issue Type: Bug
Components: Event
Affects Versions: Extensions Event 2.0.2
Reporter: Tobias Bocanegra
check code of
AbstractRepositoryEventHandler.ensureRepositoryPath()
/**
* Check if the repository path already exists. If not, create it.
*/
protected Node ensureRepositoryPath()
throws RepositoryException {
final Node node = JcrResourceUtil.createPath(this.repositoryPath,
EventHelper.NODETYPE_FOLDER,
EventHelper.NODETYPE_FOLDER,
this.writerSession, true);
return node;
}
this should use a sling:OrderedFolder
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-799) Job Folder is not ordered and results in unordered queue
[
https://issues.apache.org/jira/browse/SLING-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12660450#action_12660450
]
Carsten Ziegeler commented on SLING-799:
Ah, right - now I would prefer to use a sorted query and don't rely on any
(maybe unknown) sorting of the nodes in the repository. An ordered collection
in jcr only means that it is somehow ordered.
So I think we should a) sort the result of the JobStatusProvider methods during
the query and b) use an ordered folder as this usually shows the order of the
queue in the repository.
Job Folder is not ordered and results in unordered queue
Key: SLING-799
URL: https://issues.apache.org/jira/browse/SLING-799
Project: Sling
Issue Type: Bug
Components: Event
Affects Versions: Extensions Event 2.0.2
Reporter: Tobias Bocanegra
check code of
AbstractRepositoryEventHandler.ensureRepositoryPath()
/**
* Check if the repository path already exists. If not, create it.
*/
protected Node ensureRepositoryPath()
throws RepositoryException {
final Node node = JcrResourceUtil.createPath(this.repositoryPath,
EventHelper.NODETYPE_FOLDER,
EventHelper.NODETYPE_FOLDER,
this.writerSession, true);
return node;
}
this should use a sling:OrderedFolder
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-808) Increase version of parent pom to avoid problems with snapshot builds
[ https://issues.apache.org/jira/browse/SLING-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-808. -- Resolution: Fixed Updated in revision 731526 Increase version of parent pom to avoid problems with snapshot builds - Key: SLING-808 URL: https://issues.apache.org/jira/browse/SLING-808 Project: Sling Issue Type: Bug Components: General Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler We are using the 4-snapshot version of the parent pom for a long time now, if we change it (like we did with removing the jcr dependencies) this breaks all older snapshot builds as they refer to the old parent pom. Therefore, we'll update our parent pom to 5-snapshot. This allows us to modify the pom without breaking old builds. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-799) Job Folder is not ordered and results in unordered queue
[
https://issues.apache.org/jira/browse/SLING-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-799.
--
Resolution: Fixed
Fix Version/s: Extensions Event 2.0.4
Fixed in revision 731509 by creating an ordered folder and sorting the query
result.
Job Folder is not ordered and results in unordered queue
Key: SLING-799
URL: https://issues.apache.org/jira/browse/SLING-799
Project: Sling
Issue Type: Bug
Components: Event
Affects Versions: Extensions Event 2.0.2
Reporter: Tobias Bocanegra
Assignee: Carsten Ziegeler
Fix For: Extensions Event 2.0.4
check code of
AbstractRepositoryEventHandler.ensureRepositoryPath()
/**
* Check if the repository path already exists. If not, create it.
*/
protected Node ensureRepositoryPath()
throws RepositoryException {
final Node node = JcrResourceUtil.createPath(this.repositoryPath,
EventHelper.NODETYPE_FOLDER,
EventHelper.NODETYPE_FOLDER,
this.writerSession, true);
return node;
}
this should use a sling:OrderedFolder
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-821) Remove dependency to JCR
Remove dependency to JCR Key: SLING-821 URL: https://issues.apache.org/jira/browse/SLING-821 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.0.2 Reporter: Carsten Ziegeler The current engine relies in some places on jcr which makes Sling unusable without a repository. If you just want to use the nice resolution and scripting features, this prevents you from doing so. I currently have the use case for Sling inside a portlet application where it's not possible (and not needed) to run a repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-832) ValueMapDecorator does not support arrays.
[ https://issues.apache.org/jira/browse/SLING-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-832: -- Assignee: Carsten Ziegeler ValueMapDecorator does not support arrays. -- Key: SLING-832 URL: https://issues.apache.org/jira/browse/SLING-832 Project: Sling Issue Type: Improvement Components: API Affects Versions: API 2.0.2 Reporter: Tobias Bocanegra Assignee: Carsten Ziegeler Fix For: API 2.0.4 Attachments: ValueMapDecorator.r735030.patch albeit the JcrPropertyMap supports arrays, the wrapper does not and yields to unexpected problems when using it. eg: i use the following code, to get a detached copy of a jcr property map: Node content = node.getNode(jcr:content); ValueMap props = new JcrPropertyMap(content); // create detached copy ValueMap properties = new ValueMapDecorator(new HashMapString, Object(props)); and the following does not work: String[] values = properties.get(myProp, new String[0]); although it works on the JcrPropertyMap ps: will provide a patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-832) ValueMapDecorator does not support arrays.
[ https://issues.apache.org/jira/browse/SLING-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-832: --- Affects Version/s: (was: Scripting API 2.0.2) API 2.0.2 Fix Version/s: API 2.0.4 Correct version ValueMapDecorator does not support arrays. -- Key: SLING-832 URL: https://issues.apache.org/jira/browse/SLING-832 Project: Sling Issue Type: Improvement Components: API Affects Versions: API 2.0.2 Reporter: Tobias Bocanegra Assignee: Carsten Ziegeler Fix For: API 2.0.4 Attachments: ValueMapDecorator.r735030.patch albeit the JcrPropertyMap supports arrays, the wrapper does not and yields to unexpected problems when using it. eg: i use the following code, to get a detached copy of a jcr property map: Node content = node.getNode(jcr:content); ValueMap props = new JcrPropertyMap(content); // create detached copy ValueMap properties = new ValueMapDecorator(new HashMapString, Object(props)); and the following does not work: String[] values = properties.get(myProp, new String[0]); although it works on the JcrPropertyMap ps: will provide a patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-832) ValueMapDecorator does not support arrays.
[ https://issues.apache.org/jira/browse/SLING-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-832. Resolution: Fixed Thanks for your patch. I've applied it in revision: 735083. Please cross check and close this bug. Thansk ValueMapDecorator does not support arrays. -- Key: SLING-832 URL: https://issues.apache.org/jira/browse/SLING-832 Project: Sling Issue Type: Improvement Components: API Affects Versions: API 2.0.2 Reporter: Tobias Bocanegra Assignee: Carsten Ziegeler Fix For: API 2.0.4 Attachments: ValueMapDecorator.r735030.patch albeit the JcrPropertyMap supports arrays, the wrapper does not and yields to unexpected problems when using it. eg: i use the following code, to get a detached copy of a jcr property map: Node content = node.getNode(jcr:content); ValueMap props = new JcrPropertyMap(content); // create detached copy ValueMap properties = new ValueMapDecorator(new HashMapString, Object(props)); and the following does not work: String[] values = properties.get(myProp, new String[0]); although it works on the JcrPropertyMap ps: will provide a patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-825) impossible to debug servlet code due to incorrect sourceFile atribute of generated class file
[ https://issues.apache.org/jira/browse/SLING-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-825: --- Fix Version/s: Scripting Java 2.0.0 Assignee: Carsten Ziegeler impossible to debug servlet code due to incorrect sourceFile atribute of generated class file - Key: SLING-825 URL: https://issues.apache.org/jira/browse/SLING-825 Project: Sling Issue Type: Bug Components: Scripting Java Reporter: Stefan Guggisberg Assignee: Carsten Ziegeler Fix For: Scripting Java 2.0.0 assume the following servlet source file in content: /apps/foo/bar.png.java this resource declares the java class bar_png.java in the package foo. the resulting class file's sourceFile attribute returns .foo.bar_png.java, i.e. it is prefixed by a dot and the package. furthermore all but the last dot in the resource name are replaced by underscores. in order for java debuggers being able to debug such classes the sourceFile attribute should just return the name of the compilation unit, i.e. bar.png.java. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-825) impossible to debug servlet code due to incorrect sourceFile atribute of generated class file
[ https://issues.apache.org/jira/browse/SLING-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12665051#action_12665051 ] Carsten Ziegeler commented on SLING-825: Hi Stefan, I've committed a patch in revision: 735621, could you please test this? impossible to debug servlet code due to incorrect sourceFile atribute of generated class file - Key: SLING-825 URL: https://issues.apache.org/jira/browse/SLING-825 Project: Sling Issue Type: Bug Components: Scripting Java Reporter: Stefan Guggisberg Assignee: Carsten Ziegeler Fix For: Scripting Java 2.0.0 assume the following servlet source file in content: /apps/foo/bar.png.java this resource declares the java class bar_png.java in the package foo. the resulting class file's sourceFile attribute returns .foo.bar_png.java, i.e. it is prefixed by a dot and the package. furthermore all but the last dot in the resource name are replaced by underscores. in order for java debuggers being able to debug such classes the sourceFile attribute should just return the name of the compilation unit, i.e. bar.png.java. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
