[jira] Created: (SLING-1935) Remove dependency to web console
Remove dependency to web console Key: SLING-1935 URL: https://issues.apache.org/jira/browse/SLING-1935 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Bundleresource 2.0.4 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Bundleresource 2.0.6 Since some versions the web console provides a way to register plugins without directly depending on the web console api - we should use this as well -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1935) Remove dependency to web console
[ https://issues.apache.org/jira/browse/SLING-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1935. - Resolution: Fixed Removed the dependency and register directly a servlet with revision 1060490 Remove dependency to web console Key: SLING-1935 URL: https://issues.apache.org/jira/browse/SLING-1935 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Bundleresource 2.0.4 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Bundleresource 2.0.6 Since some versions the web console provides a way to register plugins without directly depending on the web console api - we should use this as well -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1391) Make JcrModifiablePropertyMap write changes directly
[
https://issues.apache.org/jira/browse/SLING-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12983562#action_12983562
]
Carsten Ziegeler commented on SLING-1391:
-
Rethinking this, I now agree that this makes more sense, especially if we're
moving to full CRUD operations though the resource resolver.
Make JcrModifiablePropertyMap write changes directly
Key: SLING-1391
URL: https://issues.apache.org/jira/browse/SLING-1391
Project: Sling
Issue Type: Improvement
Components: JCR
Affects Versions: JCR Resource 2.0.6
Reporter: Vidar S. Ramdal
As discussed on http://markmail.org/thread/io2dnkykjnayydwz, the current
JcrModifiablePropertyMap implementation of the PersistableValueMap interface
uses a cached map to store changed values. The cached values are not written
to the underlying node until a PVM.save() is called - at which point JMPM
calles Node.save() to persist the changes. Thus, reverting changes made in a
session is impossible.
This makes atomic operations such as this difficult to implement:
try {
// Modify a property through PersistableValueMap
PersistableValueMap props = resource.adaptTo(PersistableValueMap.class);
props.put(prop, value);
props.save();
// Do some other, unrelated changes
Node sibling = resource.adaptTo(Node.class).getParent().addNode(child);
sibling.doSomeChange(); // This may throw an exception
session.save();
} catch(Exception e) {
session.refresh(false); // Cancel the pending changes of this session
}
Felix suggests (http://markmail.org/message/5fae3cwsshbnemrf):
* Enable the PersistableValueMap to write through to the JCR
transient space on put().
* Write-through is configurable on a global level (in the
JcrResourceResolver providing the PersistableValueMap
instances upon adapt()). By default it is switched off
(backwards compatiblity).
* Write-through can also be switched on/off on a per-instance
level of the PersistableValueMap object (setWriteThrough(boolean))
* PersistableValueMap.save() first writes back local changes
not already stored using write-through and then calls node.save()
* PersistableValueMap.reset() drops local changes not already stored
using write-through and then calls node.refresh(false)
* When we finally do full CRUD in the ResourceResolver, we should
add save/reset methods, which would call Session.save() or
refresh(false), resp. For now the Session methods must be called
directly.
This task is about implementing Felix' suggestions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1940) selector form submits to the wrong path when used in a non-root servlet context
[
https://issues.apache.org/jira/browse/SLING-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12984209#action_12984209
]
Carsten Ziegeler commented on SLING-1940:
-
I think the resource path should already contain the context path and then used
as is. This would allow to redirect to any path - not even within the same
webapp.
selector form submits to the wrong path when used in a non-root servlet
context
---
Key: SLING-1940
URL: https://issues.apache.org/jira/browse/SLING-1940
Project: Sling
Issue Type: Bug
Components: Authentication
Reporter: Justin Edelson
Assignee: Justin Edelson
If you run Sling on a non-root servlet context go to the login page (e.g.
http://localhost:8080/org.apache.sling.launchpad.testing-war-6-SNAPSHOT/system/sling/login.html),
the login servlet redirects to a login form with a query parameter called
resource set to the servlet context path (e.g.
http://localhost:8080/org.apache.sling.launchpad.testing-war-6-SNAPSHOT/system/sling/selector/login?resource=%2Forg.apache.sling.launchpad.testing-war-6-SNAPSHOT)
When the form is created, the HTML form submission path (i.e. the form
action) contains the servlet context path *twice*, e.g.
action=/org.apache.sling.launchpad.testing-war-6-SNAPSHOT/org.apache.sling.launchpad.testing-war-6-SNAPSHOT/j_security_check
The reason for this is that
org.apache.sling.auth.core.spi.AbstractAuthenticationFormServlet.getContextPath()
concatenates the servlet context path and the resource query param:
StringBuilder b = new StringBuilder();
b.append(request.getContextPath());
String resource = getResource(request);
int query = resource.indexOf('?');
if (query 0) {
b.append(resource.substring(0, query));
} else {
b.append(resource);
}
Obviously, we should only add the servlet context path once, either in the
resource query param OR AbstractAuthenticationFormServlet.getContextPath().
My inclination is to do the former, i.e. the default value of the resource
query param is /, not the servlet context path.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1942) Include ServiceTracker in Bundle
Include ServiceTracker in Bundle Key: SLING-1942 URL: https://issues.apache.org/jira/browse/SLING-1942 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.2 As the installer is a core service we should include the service tracker in the bundle to avoid a dependency to someone else providing these packages - they might be provided by the framework or the compendium bundle or someone else, depending on the installation -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1943) Sort services (transformer and factories) by service ranking before invoking
Sort services (transformer and factories) by service ranking before invoking Key: SLING-1943 URL: https://issues.apache.org/jira/browse/SLING-1943 Project: Sling Issue Type: Bug Components: Installer Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.2 The services (transformers and factories) should be invoked in order of their service ranking (highest first) - currently they are invoked in random order -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1942) Include ServiceTracker in Bundle
[ https://issues.apache.org/jira/browse/SLING-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1942. - Resolution: Fixed Changed pom in revision 1061697 Include ServiceTracker in Bundle Key: SLING-1942 URL: https://issues.apache.org/jira/browse/SLING-1942 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.2 As the installer is a core service we should include the service tracker in the bundle to avoid a dependency to someone else providing these packages - they might be provided by the framework or the compendium bundle or someone else, depending on the installation -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1944) Check result from resource transformer
Check result from resource transformer -- Key: SLING-1944 URL: https://issues.apache.org/jira/browse/SLING-1944 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.2 If a resource transformer returns a new resource type, it must also return a unique id - this should be checked by the installer -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1944) Check result from resource transformer
[ https://issues.apache.org/jira/browse/SLING-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1944. - Resolution: Fixed Added extra checks in revision 1061701 Check result from resource transformer -- Key: SLING-1944 URL: https://issues.apache.org/jira/browse/SLING-1944 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.2 If a resource transformer returns a new resource type, it must also return a unique id - this should be checked by the installer -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1946) Transformer should only be invoked once on an untransformed resource
Transformer should only be invoked once on an untransformed resource Key: SLING-1946 URL: https://issues.apache.org/jira/browse/SLING-1946 Project: Sling Issue Type: Improvement Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.2 If a transformer has seen a resource, it should not be invoked again on this resource regardless if the transformation has been successdful or not -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1945) Remove resource from untransformed resources if resource is removed by provider
Remove resource from untransformed resources if resource is removed by provider --- Key: SLING-1945 URL: https://issues.apache.org/jira/browse/SLING-1945 Project: Sling Issue Type: Bug Components: Installer Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Priority: Minor Fix For: Installer Core 3.1.2 If a resource is removed by the provider but is still in the untransformed resources, it should be removed from that list as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1945) Remove resource from untransformed resources if resource is removed by provider
[ https://issues.apache.org/jira/browse/SLING-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1945. - Resolution: Fixed Fixed with revision 1061707 Remove resource from untransformed resources if resource is removed by provider --- Key: SLING-1945 URL: https://issues.apache.org/jira/browse/SLING-1945 Project: Sling Issue Type: Bug Components: Installer Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Priority: Minor Fix For: Installer Core 3.1.2 If a resource is removed by the provider but is still in the untransformed resources, it should be removed from that list as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1519) URL Mappings for URL paths containing - does not work
[ https://issues.apache.org/jira/browse/SLING-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1519: Fix Version/s: (was: JCR Resource 2.0.8) JCR Resource 2.0.10 Moving to next version to not block the release URL Mappings for URL paths containing - does not work --- Key: SLING-1519 URL: https://issues.apache.org/jira/browse/SLING-1519 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Resource 2.0.6 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Resource 2.0.10 Consider the following mapping for JCR Resource Resolver URL Mapping: /content/somesite/en-us/-/ This breaks, because the dash in en-us is considered a separator instead of being part of the incoming URL path thus giving a mapping /content/somesite/en -- us/-/ To fix this situation in a broader context the - should be replaced as the character indicating bidirectional mapping by a : and the code adapted to not break on dashes any more. For backwards compatibility, the dash should still be supported as a bidirectional indicator. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1943) Sort services (transformer and factories) by service ranking before invoking
[ https://issues.apache.org/jira/browse/SLING-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1943. - Resolution: Fixed Added sorting in revision 1061795 Sort services (transformer and factories) by service ranking before invoking Key: SLING-1943 URL: https://issues.apache.org/jira/browse/SLING-1943 Project: Sling Issue Type: Bug Components: Installer Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.2 The services (transformers and factories) should be invoked in order of their service ranking (highest first) - currently they are invoked in random order -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1947) Remove dependency to JCR and make resource provider implementation easier
Remove dependency to JCR and make resource provider implementation easier - Key: SLING-1947 URL: https://issues.apache.org/jira/browse/SLING-1947 Project: Sling Issue Type: Improvement Components: Extensions, JCR Affects Versions: Extensions Bundleresource 2.0.4, File System Resource Provider 1.0.0, JCR Resource 2.0.6 Reporter: Carsten Ziegeler Currently the resource provider implementations usually check if the resource points to a directory if the repository has a node at this location to allow to let the repository return this node as the directory resource. This requires the implementations to adapt the resolver to a session, check if the node is available etc. This looks like a workaround, creates an unnecessary dependency to JCR and might create problems in the future if the repository is not used as a provider or is not the root provider. One solution would be to let the implementations return nt:folder and the resource resolver checks in this case the root provider if it has a resource at the same position and returns that one instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1949) Improve removal of bundles if the bundle is installed more than once
Improve removal of bundles if the bundle is installed more than once Key: SLING-1949 URL: https://issues.apache.org/jira/browse/SLING-1949 Project: Sling Issue Type: Bug Components: Installer Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Priority: Minor Fix For: Installer Core 3.1.2 If a bundle is removed through a provider but is installed more than once, currently the first one with the same symbolic name is compared with the bundle to be uninstalled. If the version does not match, nothing happens. If a bundle with a symbolic name is installed once, this is no problem - but as soon as a bundle with the same symbolic name is installed more than once, the wrong bundle can be used for the comparison. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1949) Improve removal of bundles if the bundle is installed more than once
[ https://issues.apache.org/jira/browse/SLING-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1949. - Resolution: Fixed Now searching an exact match (symbolic name and version) when uninstalling; for installing now the bundle with the same symbolic name and highest version is used. Revision 1062180 Improve removal of bundles if the bundle is installed more than once Key: SLING-1949 URL: https://issues.apache.org/jira/browse/SLING-1949 Project: Sling Issue Type: Bug Components: Installer Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Priority: Minor Fix For: Installer Core 3.1.2 If a bundle is removed through a provider but is installed more than once, currently the first one with the same symbolic name is compared with the bundle to be uninstalled. If the version does not match, nothing happens. If a bundle with a symbolic name is installed once, this is no problem - but as soon as a bundle with the same symbolic name is installed more than once, the wrong bundle can be used for the comparison. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1950) Parameters are not removed from symbolic name
Parameters are not removed from symbolic name - Key: SLING-1950 URL: https://issues.apache.org/jira/browse/SLING-1950 Project: Sling Issue Type: Bug Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.2 If the symbolic name header contains parameters, these are not removed for further processing. Therefore searching the bundle with the symbolic name always results in a bundle not found. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1950) Parameters are not removed from symbolic name
[ https://issues.apache.org/jira/browse/SLING-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1950. - Resolution: Fixed Fixed in revision 1062193 Parameters are not removed from symbolic name - Key: SLING-1950 URL: https://issues.apache.org/jira/browse/SLING-1950 Project: Sling Issue Type: Bug Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.2 If the symbolic name header contains parameters, these are not removed for further processing. Therefore searching the bundle with the symbolic name always results in a bundle not found. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1946) Transformer should only be invoked once on an untransformed resource
[ https://issues.apache.org/jira/browse/SLING-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1946: Component/s: Installer Transformer should only be invoked once on an untransformed resource Key: SLING-1946 URL: https://issues.apache.org/jira/browse/SLING-1946 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.2 If a transformer has seen a resource, it should not be invoked again on this resource regardless if the transformation has been successdful or not -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1950) Parameters are not removed from symbolic name
[ https://issues.apache.org/jira/browse/SLING-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1950: Component/s: Installer Parameters are not removed from symbolic name - Key: SLING-1950 URL: https://issues.apache.org/jira/browse/SLING-1950 Project: Sling Issue Type: Bug Components: Installer Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.2 If the symbolic name header contains parameters, these are not removed for further processing. Therefore searching the bundle with the symbolic name always results in a bundle not found. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1946) Transformer should only be invoked once on an untransformed resource
[ https://issues.apache.org/jira/browse/SLING-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1946. - Resolution: Fixed The transformer service is identified by the service id - a transformer with a service id is only invoked once on an untransformed resource Fixed in revision 1062196 Transformer should only be invoked once on an untransformed resource Key: SLING-1946 URL: https://issues.apache.org/jira/browse/SLING-1946 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: Installer Core 3.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.2 If a transformer has seen a resource, it should not be invoked again on this resource regardless if the transformation has been successdful or not -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1931) Compiler message contain only class name but not resource path
[ https://issues.apache.org/jira/browse/SLING-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1931. --- Compiler message contain only class name but not resource path -- Key: SLING-1931 URL: https://issues.apache.org/jira/browse/SLING-1931 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Compiler 2.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Compiler 2.0.2 The compiler messages from the jcr compiler contain just the java class name, but not the resource path -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1930) Compilation message contains only class name without package information
[ https://issues.apache.org/jira/browse/SLING-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1930. --- Compilation message contains only class name without package information Key: SLING-1930 URL: https://issues.apache.org/jira/browse/SLING-1930 Project: Sling Issue Type: Bug Components: Commons Affects Versions: Commons Compiler 2.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Commons Compiler 2.0.2 The compilation messages return just the class name (followed by .java) without the package -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1912) Commons/log bundle should import exported SLF4J and OSGi LogService API
[ https://issues.apache.org/jira/browse/SLING-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1912. --- Commons/log bundle should import exported SLF4J and OSGi LogService API --- Key: SLING-1912 URL: https://issues.apache.org/jira/browse/SLING-1912 Project: Sling Issue Type: Bug Components: Commons Affects Versions: Commons Log 2.1.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Commons Log 2.1.2 The commons/log bundle currently exports the SLF4J and OSGi LogService APIs for which implementations are provided (where the LogService implementation actually uses SLF4J loggers). The Commons Logging and Log4J APIs exported from the commons/log bundle do not need to be re-imported because we just provide SLF4J based implementations of this API and if there are other providers, we don't really care. Besides the core org.slf4j package, the org.slf4j.spi and org.slf4j.helpers package needs also be exported and re-imported because these packages depend on each others and should be imported (if at all) together. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1927) Upgrade Logging Support to SLF4J 1.6.1
[ https://issues.apache.org/jira/browse/SLING-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1927. --- Upgrade Logging Support to SLF4J 1.6.1 -- Key: SLING-1927 URL: https://issues.apache.org/jira/browse/SLING-1927 Project: Sling Issue Type: Improvement Components: Commons Affects Versions: Commons Log 2.1.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Commons Log 2.1.2 SLF4j 1.6.1 is available for quite some time already; so we should upgrade to support applications requiring these new API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1823) Use ConfigAdmin configurations for queues
[ https://issues.apache.org/jira/browse/SLING-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1823. --- Use ConfigAdmin configurations for queues - Key: SLING-1823 URL: https://issues.apache.org/jira/browse/SLING-1823 Project: Sling Issue Type: New Feature Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 Currently the jobs send to the job handler might contain queue configuration information, like a queue name, parallel settings etc. These props are used to create queues. This approach has a least two potential problems: - What happens if two jobs specify the same queue name with different settings? - The developer creating the code to send the job might not be the person deciding what is processed in which queue and how Therefore it would make more sense to have a queue as a configuration in the ConfigAdmin . this would make maintenance easier and allows to have a single place for queue configurations. Of course the old props should still be supported for compatibility. The configurations can then be easily added, viewed and monitored through the web console. The main queue is a configuration which is always available -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1825) Use in memory searches for jobs
[ https://issues.apache.org/jira/browse/SLING-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1825. --- Use in memory searches for jobs --- Key: SLING-1825 URL: https://issues.apache.org/jira/browse/SLING-1825 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 Jobs are currently searched through a JCR query - the query can be very slow and as most of the information is already available in memory anyway, we could directly search in memory and don't need any jcr access -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1808) Don't use thread pool for system threads
[ https://issues.apache.org/jira/browse/SLING-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1808. --- Don't use thread pool for system threads Key: SLING-1808 URL: https://issues.apache.org/jira/browse/SLING-1808 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 The system threads (background threads that run as long as the bundle runs) are currently taken from the thread pool; this is not necessary and in addition reduces the number of available threads from the pool; it makes calculating the required threads more difficult. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1826) Provide a round robin queue based on the topic
[ https://issues.apache.org/jira/browse/SLING-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1826. --- Provide a round robin queue based on the topic -- Key: SLING-1826 URL: https://issues.apache.org/jira/browse/SLING-1826 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 Currently we have two queues: parallel or ordered. We could also do a topic round robin queue, which picks a different a job with a topic. This allows to limit the number of jobs processed in parallel for these topics while each topic is processed as fast as possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1827) Mechanism to process specific jobs on specific machines
[ https://issues.apache.org/jira/browse/SLING-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1827. --- Mechanism to process specific jobs on specific machines --- Key: SLING-1827 URL: https://issues.apache.org/jira/browse/SLING-1827 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 When the job mechanism is used for expensive operations like movie encodings etc. it would be nice to have dedicated machines processing these jobs. We could simply restrict queues to process jobs on specific nodes in a cluster through the Sling application id -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1475) Create a web console plugin
[ https://issues.apache.org/jira/browse/SLING-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1475. --- Create a web console plugin --- Key: SLING-1475 URL: https://issues.apache.org/jira/browse/SLING-1475 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Event 2.3.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 It would be nice to have a web console plugin for the configuration status which displays all available information, like available job queues, number of jobs in processing 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-1824) Clean up implementation
[ https://issues.apache.org/jira/browse/SLING-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1824. --- Clean up implementation --- Key: SLING-1824 URL: https://issues.apache.org/jira/browse/SLING-1824 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 The job handling implementation has grown over time and got overly complicated now. It is time to clean it up and refactor it -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1828) Provide queue operations like suspend/resume
[ https://issues.apache.org/jira/browse/SLING-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1828. --- Provide queue operations like suspend/resume Key: SLING-1828 URL: https://issues.apache.org/jira/browse/SLING-1828 Project: Sling Issue Type: New Feature Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 Queue operations for supsending (to stop processing for a while), resuming, clearing the queue (without removing the jobs) and removing all jobs from the queue -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1829) Provide statistics about job processing
[ https://issues.apache.org/jira/browse/SLING-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1829. --- Provide statistics about job processing --- Key: SLING-1829 URL: https://issues.apache.org/jira/browse/SLING-1829 Project: Sling Issue Type: New Feature Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 It would be nice to have some statistics about the job handling like home many jobs have been processed, are queued, are in processing etc. We could have one general set and a set per queue for drill down -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1849) DropQueueTest failure
[ https://issues.apache.org/jira/browse/SLING-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1849. --- DropQueueTest failure - Key: SLING-1849 URL: https://issues.apache.org/jira/browse/SLING-1849 Project: Sling Issue Type: Bug Components: Extensions Environment: $ mvn -v Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_13 Java home: /usr/java/jdk1.6.0_13/jre Default locale: de_CH, platform encoding: UTF-8 OS name: linux version: 2.6.32-25-generic arch: amd64 Family: unix Reporter: Felix Meschberger Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 The bundles/extensions/event module has a unit test failure on my Ubuntu box: testDroppingQueue(org.apache.sling.event.impl.jobs.DropQueueTest) --- Test set: org.apache.sling.event.impl.jobs.DropQueueTest --- Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.976 sec FAILURE! testDroppingQueue(org.apache.sling.event.impl.jobs.DropQueueTest) Time elapsed: 2.809 sec FAILURE! java.lang.AssertionError: expected:0 but was:4 at org.junit.Assert.fail(Assert.java:91) at org.junit.Assert.failNotEquals(Assert.java:645) at org.junit.Assert.assertEquals(Assert.java:126) at org.junit.Assert.assertEquals(Assert.java:470) at org.junit.Assert.assertEquals(Assert.java:454) at org.apache.sling.event.impl.jobs.DropQueueTest.testDroppingQueue(DropQueueTest.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:66) at org.jmock.integration.junit4.JMock$1.invoke(JMock.java:37) at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:105) at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:86) at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:94) at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:84) at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:49) at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:98) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:61) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:54) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:34) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:44) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:52) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1889) Make job creation date available
[ https://issues.apache.org/jira/browse/SLING-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1889. --- Make job creation date available Key: SLING-1889 URL: https://issues.apache.org/jira/browse/SLING-1889 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Event 2.4.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 Each job event contains the sling:created property indicating when the job has been created. However, there is no public constant or method available -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1830) Improve write acesses for job execution
[ https://issues.apache.org/jira/browse/SLING-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1830. --- Improve write acesses for job execution --- Key: SLING-1830 URL: https://issues.apache.org/jira/browse/SLING-1830 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Event 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 Currently, the flow for a job is: - write the job to the repository - lock the node - add the PROCESSOR info - remove the node or unlock it and set some props We can at least skip the PROCESSOR info and set it at the end. In addition we should base the job handling completly on observation -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1896) Provide a configuration option to disable/enable all event processing
[ https://issues.apache.org/jira/browse/SLING-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1896. --- Provide a configuration option to disable/enable all event processing - Key: SLING-1896 URL: https://issues.apache.org/jira/browse/SLING-1896 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Extensions Event 2.4.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 Sometimes, it would be helpfull to complete disable just the processing of job events We should add a configuration property to the job manager -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1918) Use time based folder structure for jobs without an id
[ https://issues.apache.org/jira/browse/SLING-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1918. --- Use time based folder structure for jobs without an id -- Key: SLING-1918 URL: https://issues.apache.org/jira/browse/SLING-1918 Project: Sling Issue Type: New Feature Components: Extensions Affects Versions: Extensions Event 2.4.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.0 Currently jobs without an job id are stored in an artifical folder structure (to avoid a too large flat hierarchy) - this folder structure is created randomly by generating uuid. To avoid concurrency problems in a clustered environment, these folders are never deleted - resulting in a large empty folder structure We could use a time based folder structure instead and create a new folder every minute - once this folder gets empty and another minute has started we can safely remove the folder. In addition if we include the sling id in the folder name, we avoid folder creation problems in a clustered environment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1928) JSP API classes from the environment can't be used.
[ https://issues.apache.org/jira/browse/SLING-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1928. --- JSP API classes from the environment can't be used. --- Key: SLING-1928 URL: https://issues.apache.org/jira/browse/SLING-1928 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scripting JSP 2.0.12 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Scripting JSP 2.0.14 The jsp scripting bundles includes the jsp api and taglib classes; however if the api classes from outside (like another bundle or the servlet engine) should be used instead, this leads to class cast exceptions as the jsp scripting bundle sets the JspFactory.setDefaultFactory() to its own factory. After this call, all web applications of the servlet engine will use the Sling JspFactory which leads to such exceptions -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1911) If the same resource is at different locations they should be treated as the same resource
[ https://issues.apache.org/jira/browse/SLING-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1911. --- If the same resource is at different locations they should be treated as the same resource -- Key: SLING-1911 URL: https://issues.apache.org/jira/browse/SLING-1911 Project: Sling Issue Type: Bug Components: Installer Affects Versions: Installer Core 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.0 If e.g. a bundle is in two different location (in the repository), these bundles represent the same resource. Currently they end up as two different resources which might create unwanted results, e.g. if the bundle is removed from location A while added at location B In this case the bundle might be uninstalled after this operation, but of course it should still be installed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1913) Implement own serialization/deserilization
[ https://issues.apache.org/jira/browse/SLING-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1913. --- Implement own serialization/deserilization -- Key: SLING-1913 URL: https://issues.apache.org/jira/browse/SLING-1913 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: Installer Core 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.0 As the used data objects/classes might change in future versions, we should implement the serialization/deserialization of these objects and not rely on the default behaviour -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1914) Only one config per factory configuration possible
[ https://issues.apache.org/jira/browse/SLING-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1914. --- Only one config per factory configuration possible -- Key: SLING-1914 URL: https://issues.apache.org/jira/browse/SLING-1914 Project: Sling Issue Type: Bug Components: Installer Affects Versions: Installer Core 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.0 It's not possible to have several configs for a factory configuration - always the first one added is overwritten with further configurations -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1922) Allow resource transformer for processing installable resources
[ https://issues.apache.org/jira/browse/SLING-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1922. --- Allow resource transformer for processing installable resources --- Key: SLING-1922 URL: https://issues.apache.org/jira/browse/SLING-1922 Project: Sling Issue Type: New Feature Components: Installer Affects Versions: Installer Core 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.0 In some cases the installable resource is not directly the installable end product, for example if a jar is dropped into the installer which is not a bundle a service could bundlize this jar. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-755) Web Console Plugin for the OSGi Installer
[ https://issues.apache.org/jira/browse/SLING-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-755. -- Web Console Plugin for the OSGi Installer - Key: SLING-755 URL: https://issues.apache.org/jira/browse/SLING-755 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: Installer Core 3.0.0 Reporter: Bertrand Delacretaz Assignee: Carsten Ziegeler Priority: Minor Fix For: Installer Core 3.1.0 (changed title as discussion moved to creating a console plugin) Making a servlet out of the jcrinstall RepositoryObserver class introduces dependencies on the sling api and servlet bundles, which are not desired for jcrinstall - its dependencies should be kept to a minimum. I'll move the servlet to its own bundle - it is currently only needed for integration testing, but might be useful for other monitoring purposes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1915) Status information should be stored outside the bundle data directory
[ https://issues.apache.org/jira/browse/SLING-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1915. --- Status information should be stored outside the bundle data directory - Key: SLING-1915 URL: https://issues.apache.org/jira/browse/SLING-1915 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: Installer Core 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.0 Currently the status information is stored inside the private bundle data area of the installer core bundle - this is fine as long as the core bundle itself is not updated. As soon as it is updated, all this data is lost. Most of the data can be recalculated but the information if a bundle or config has been installed through the installer or through any other way is lost. Therefore we should store the data outside of the bundle private data (like config admin does) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1920) Make installers pluggable
[ https://issues.apache.org/jira/browse/SLING-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1920. --- Make installers pluggable - Key: SLING-1920 URL: https://issues.apache.org/jira/browse/SLING-1920 Project: Sling Issue Type: New Feature Components: Installer Affects Versions: Installer Core 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.0 Currently the osgi installer only supports bundles and configurations - we should add service interfaces to allow installation of other resources like deployment packages 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-1909) Don't uninstall bundles not installed by the installer
[ https://issues.apache.org/jira/browse/SLING-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1909. --- Don't uninstall bundles not installed by the installer -- Key: SLING-1909 URL: https://issues.apache.org/jira/browse/SLING-1909 Project: Sling Issue Type: Bug Components: Installer Affects Versions: Installer Core 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.0 If a bundle has been installed by someone else than the installer, but is also in the list of installed resources and then gets removed from this list of resources, it should not be uninstalled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1934) Provider should provide all resources to the installer
[ https://issues.apache.org/jira/browse/SLING-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1934. --- Provider should provide all resources to the installer -- Key: SLING-1934 URL: https://issues.apache.org/jira/browse/SLING-1934 Project: Sling Issue Type: Bug Components: Installer Affects Versions: JCR Installer 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Installer 3.0.2 Currently, the jcr provider only forwards files with the extension jar|config|properties With the new pluggable support of the installer core, this prevents other types to be installed - the check needs to be completly removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1923) Improve the (internal) resource handling
[ https://issues.apache.org/jira/browse/SLING-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1923. --- Improve the (internal) resource handling Key: SLING-1923 URL: https://issues.apache.org/jira/browse/SLING-1923 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: Installer Core 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.1.0 The current resource handling has some drawbacks - one is that a resource is always copied into the local data store even if it did not change; another one is that integrating new concepts like the resource transformer etc is difficult and error prone. The first thing we should change is the resource types, currently we have CONFIG and BUNDLE - this assumes that the client knows what resources it is providing - however it is not the task of the client to decide this; in many cases the client has even not the knowledge about it. Therefore we should introduce two new resource types PROPERTIES and FILE. However, if the client really knows what it is dealing with, it can use one of the two new types OSGI_BUNDLE or OSGI_CONFIG - we introduce these new types, to be more compatible - the old constants CONFIG and BUNDLE will be deprecated and aliases for PROPERTIES and FILE! When a new resource provider is registering itself or an update of resources takes place, merging of resources should be done immediately - the sync first does some general sanity checks on the incoming data and then uses URL and digest of the data to check for updates/removes. If a resource with the same URL and digest is already available, it is assumed to be the same and no further processing is required! This avoids unnecessary copies. We further decide between incoming resource type (usually PROPERTIES or FILE) and processing resource type. The new resource transformer services are responsible for this transformation (maybe in combination with data transformation). A resource transformer can omit one or more resources with resource type and data. If a resource has a processing resource type, this resource is used to be processed by the osgi installer task factories. As long as the resource has no processing resource type, it is not processed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1952) Remove support for deployment packages
Remove support for deployment packages -- Key: SLING-1952 URL: https://issues.apache.org/jira/browse/SLING-1952 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Base 2.2.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Launchpad Base 2.2.2 The current support for deployment packages does not work as it has class loading issues - therefore we should remove it and use the new installation way (already used for configurations) instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1952) Remove support for deployment packages
[ https://issues.apache.org/jira/browse/SLING-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1952. - Resolution: Fixed Removed in revision 1062752 Remove support for deployment packages -- Key: SLING-1952 URL: https://issues.apache.org/jira/browse/SLING-1952 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Base 2.2.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Launchpad Base 2.2.2 The current support for deployment packages does not work as it has class loading issues - therefore we should remove it and use the new installation way (already used for configurations) instead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1953) Support provisioning of all file types
Support provisioning of all file types -- Key: SLING-1953 URL: https://issues.apache.org/jira/browse/SLING-1953 Project: Sling Issue Type: Improvement Components: Launchpad Affects Versions: Launchpad Base 2.2.0 Reporter: Carsten Ziegeler Fix For: Launchpad Base 2.2.2 The new launchpad installer only supports configuration file from resources/config It should add all found files as installable resources, this would enable support for all types supported by the installer or plugins like deployment packages, webapps 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-1953) Support provisioning of all file types
[ https://issues.apache.org/jira/browse/SLING-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12985656#action_12985656 ] Carsten Ziegeler commented on SLING-1953: - One way would be to provide all files from another directory like resources/provisioning (?) to the installer core as files. Support provisioning of all file types -- Key: SLING-1953 URL: https://issues.apache.org/jira/browse/SLING-1953 Project: Sling Issue Type: Improvement Components: Launchpad Affects Versions: Launchpad Base 2.2.0 Reporter: Carsten Ziegeler Fix For: Launchpad Base 2.2.2 The new launchpad installer only supports configuration file from resources/config It should add all found files as installable resources, this would enable support for all types supported by the installer or plugins like deployment packages, webapps 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-1298) Update Authentication Documentation with Impersonation support info
[ https://issues.apache.org/jira/browse/SLING-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1298: Fix Version/s: (was: Auth Core 1.0.6) Auth Core 1.0.8 Moving to 1.0.8 to not block 1.0.6 release Update Authentication Documentation with Impersonation support info --- Key: SLING-1298 URL: https://issues.apache.org/jira/browse/SLING-1298 Project: Sling Issue Type: Task Components: Authentication Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Auth Core 1.0.8 Currently the Sling authentication documentation page at http://sling.apache.org/site/authentication.html does not provide any information on support for user impersonation by the Sling Authenticator. This should be added. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-1954) Launchpad installer should not depend on SCR
[ https://issues.apache.org/jira/browse/SLING-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-1954: --- Assignee: Carsten Ziegeler Launchpad installer should not depend on SCR Key: SLING-1954 URL: https://issues.apache.org/jira/browse/SLING-1954 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: Launchpad Base 2.2.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Launchpad Base 2.2.2 The current launchpad installer implementation requires SCR - we should rather implement an activator with a service listener. As soon as the osgi installer service and the resource provider is available, this service should start it's action -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1954) Launchpad installer should not depend on SCR
[ https://issues.apache.org/jira/browse/SLING-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986314#action_12986314 ] Carsten Ziegeler commented on SLING-1954: - I've changed the implementation in revision 1063204 - it's not tested yet, therefore I'll leave the issue open Launchpad installer should not depend on SCR Key: SLING-1954 URL: https://issues.apache.org/jira/browse/SLING-1954 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: Launchpad Base 2.2.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Launchpad Base 2.2.2 The current launchpad installer implementation requires SCR - we should rather implement an activator with a service listener. As soon as the osgi installer service and the resource provider is available, this service should start it's action -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-1956) ConfigNodeConverter throws NPE on config with empty multi-valued property
[ https://issues.apache.org/jira/browse/SLING-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-1956: --- Assignee: Carsten Ziegeler ConfigNodeConverter throws NPE on config with empty multi-valued property - Key: SLING-1956 URL: https://issues.apache.org/jira/browse/SLING-1956 Project: Sling Issue Type: Bug Components: Installer Affects Versions: JCR Installer 3.0.2 Reporter: Marcel Reutegger Assignee: Carsten Ziegeler Fix For: JCR Installer 3.0.4 Attachments: SLING-1956.patch 25.01.2011 22:24:33.270 *ERROR* [JcrInstaller.1] org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception in Thread Thread[JcrInstaller.1,5,main] java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:394) at org.apache.sling.installer.provider.jcr.impl.ConfigNodeConverter.loadProperties(ConfigNodeConverter.java:103) at org.apache.sling.installer.provider.jcr.impl.ConfigNodeConverter.load(ConfigNodeConverter.java:76) at org.apache.sling.installer.provider.jcr.impl.ConfigNodeConverter.convertNode(ConfigNodeConverter.java:59) at org.apache.sling.installer.provider.jcr.impl.WatchedFolder.scan(WatchedFolder.java:149) at org.apache.sling.installer.provider.jcr.impl.JcrInstaller$StoppableThread.run(JcrInstaller.java:187) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1956) ConfigNodeConverter throws NPE on config with empty multi-valued property
[ https://issues.apache.org/jira/browse/SLING-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1956. - Resolution: Fixed Fix Version/s: JCR Installer 3.0.4 I think we should put an empty value in the configuration - this allows to override a configuration which has a value with an empty one Changed in revision 1063645 ConfigNodeConverter throws NPE on config with empty multi-valued property - Key: SLING-1956 URL: https://issues.apache.org/jira/browse/SLING-1956 Project: Sling Issue Type: Bug Components: Installer Affects Versions: JCR Installer 3.0.2 Reporter: Marcel Reutegger Assignee: Carsten Ziegeler Fix For: JCR Installer 3.0.4 Attachments: SLING-1956.patch 25.01.2011 22:24:33.270 *ERROR* [JcrInstaller.1] org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception in Thread Thread[JcrInstaller.1,5,main] java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:394) at org.apache.sling.installer.provider.jcr.impl.ConfigNodeConverter.loadProperties(ConfigNodeConverter.java:103) at org.apache.sling.installer.provider.jcr.impl.ConfigNodeConverter.load(ConfigNodeConverter.java:76) at org.apache.sling.installer.provider.jcr.impl.ConfigNodeConverter.convertNode(ConfigNodeConverter.java:59) at org.apache.sling.installer.provider.jcr.impl.WatchedFolder.scan(WatchedFolder.java:149) at org.apache.sling.installer.provider.jcr.impl.JcrInstaller$StoppableThread.run(JcrInstaller.java:187) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1957) Potential deadlock when queue is suspended and resumed
Potential deadlock when queue is suspended and resumed -- Key: SLING-1957 URL: https://issues.apache.org/jira/browse/SLING-1957 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Extensions Event 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.2 If a queue is suspended there is a potential that the queue stays in the suspended state when it gets resumed. This is because the notify waking up the thread is done before the state is set to resumed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1957) Potential deadlock when queue is suspended and resumed
[ https://issues.apache.org/jira/browse/SLING-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1957. - Resolution: Fixed Added explicit syncs for the suspend state and changed the invocation order in the queue run method to avoid any processing when the queue is suspended. Potential deadlock when queue is suspended and resumed -- Key: SLING-1957 URL: https://issues.apache.org/jira/browse/SLING-1957 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Extensions Event 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.0.2 If a queue is suspended there is a potential that the queue stays in the suspended state when it gets resumed. This is because the notify waking up the thread is done before the state is set to resumed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1955) Event Support Unit Tests stall in full trunk build
[ https://issues.apache.org/jira/browse/SLING-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1955: Affects Version/s: Extensions Event 3.0.0 Event Support Unit Tests stall in full trunk build -- Key: SLING-1955 URL: https://issues.apache.org/jira/browse/SLING-1955 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Extensions Event 3.0.0 Environment: $ mvn -v Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_13 Java home: /usr/java/jdk1.6.0_13/jre Default locale: de_CH, platform encoding: UTF-8 OS name: linux version: 2.6.35-24-generic arch: amd64 Family: unix Reporter: Felix Meschberger Fix For: Extensions Event 3.0.2 Attachments: SLING-1955-dump.txt Running a full build with tests -- mvn clean install from trunk root -- causes the Event Support Unit Tests to stall after printing the message: 57150 [Apache Sling Job Queue roundrobintest] INFO org.apache.sling.event.impl.jobs.queues.TopicRoundRobinJobQueue.roundrobintest - Starting job queue roundrobintest -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1955) Event Support Unit Tests stall in full trunk build
[ https://issues.apache.org/jira/browse/SLING-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1955. - Resolution: Fixed This is actually caused by a potential deadlock, see SLING-1957 In addition some of the tests had a bad timing - which I now fixed as well Event Support Unit Tests stall in full trunk build -- Key: SLING-1955 URL: https://issues.apache.org/jira/browse/SLING-1955 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Extensions Event 3.0.0 Environment: $ mvn -v Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_13 Java home: /usr/java/jdk1.6.0_13/jre Default locale: de_CH, platform encoding: UTF-8 OS name: linux version: 2.6.35-24-generic arch: amd64 Family: unix Reporter: Felix Meschberger Fix For: Extensions Event 3.0.2 Attachments: SLING-1955-dump.txt Running a full build with tests -- mvn clean install from trunk root -- causes the Event Support Unit Tests to stall after printing the message: 57150 [Apache Sling Job Queue roundrobintest] INFO org.apache.sling.event.impl.jobs.queues.TopicRoundRobinJobQueue.roundrobintest - Starting job queue roundrobintest -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1933) selector form has incorrect paths to image, css, and signup form
[
https://issues.apache.org/jira/browse/SLING-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-1933.
---
selector form has incorrect paths to image, css, and signup form
Key: SLING-1933
URL: https://issues.apache.org/jira/browse/SLING-1933
Project: Sling
Issue Type: Bug
Components: Authentication
Affects Versions: Auth Selector 1.0.2, Auth Core 1.0.4
Reporter: Justin Edelson
Assignee: Justin Edelson
Fix For: Auth Selector 1.0.4, Auth Core 1.0.6
The selector form uses the substitution variable ${requestContextPath} to
generate HTML references to the CSS, image, and the signup HTML page. This is
wrong as of SLING-1855 because the requestContextPath now includes the
resource path.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1940) selector form submits to the wrong path when used in a non-root servlet context
[
https://issues.apache.org/jira/browse/SLING-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-1940.
---
selector form submits to the wrong path when used in a non-root servlet
context
---
Key: SLING-1940
URL: https://issues.apache.org/jira/browse/SLING-1940
Project: Sling
Issue Type: Bug
Components: Authentication
Reporter: Justin Edelson
Assignee: Justin Edelson
Fix For: Auth Core 1.0.6
If you run Sling on a non-root servlet context go to the login page (e.g.
http://localhost:8080/org.apache.sling.launchpad.testing-war-6-SNAPSHOT/system/sling/login.html),
the login servlet redirects to a login form with a query parameter called
resource set to the servlet context path (e.g.
http://localhost:8080/org.apache.sling.launchpad.testing-war-6-SNAPSHOT/system/sling/selector/login?resource=%2Forg.apache.sling.launchpad.testing-war-6-SNAPSHOT)
When the form is created, the HTML form submission path (i.e. the form
action) contains the servlet context path *twice*, e.g.
action=/org.apache.sling.launchpad.testing-war-6-SNAPSHOT/org.apache.sling.launchpad.testing-war-6-SNAPSHOT/j_security_check
The reason for this is that
org.apache.sling.auth.core.spi.AbstractAuthenticationFormServlet.getContextPath()
concatenates the servlet context path and the resource query param:
StringBuilder b = new StringBuilder();
b.append(request.getContextPath());
String resource = getResource(request);
int query = resource.indexOf('?');
if (query 0) {
b.append(resource.substring(0, query));
} else {
b.append(resource);
}
Obviously, we should only add the servlet context path once, either in the
resource query param OR AbstractAuthenticationFormServlet.getContextPath().
My inclination is to do the former, i.e. the default value of the resource
query param is /, not the servlet context path.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1932) when resource = /, auth.selector form submits to a bad URL
[ https://issues.apache.org/jira/browse/SLING-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1932. --- when resource = /, auth.selector form submits to a bad URL -- Key: SLING-1932 URL: https://issues.apache.org/jira/browse/SLING-1932 Project: Sling Issue Type: Bug Components: Authentication Affects Versions: Auth Core 1.0.4 Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Auth Core 1.0.6 To see this, start up Sling Launchpad, go to http://localhost:8080/ and click on the Login link. This brings up the selector login form. Try submitting the form. It submits to //j_security_check which fails. This is because AbstractAuthenticationFormServlet sets requestContextPath to / when it should 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-1625) Filesystem Resource Provider activation may throw NullPointerException
[ https://issues.apache.org/jira/browse/SLING-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1625. --- Filesystem Resource Provider activation may throw NullPointerException -- Key: SLING-1625 URL: https://issues.apache.org/jira/browse/SLING-1625 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: File System Resource Provider 1.0.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: File System Resource Provider 1.0.2 When setting up the Filesystem Resource provider, the configured location is scanned to setup montioring on external locations. If a directory to be monitored cannot be accessed, the File.listFiles() method returns null, which is not caught thus causing NullPointerException to be thrown. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1386) Resource events for nt:file are not calculated properly
[ https://issues.apache.org/jira/browse/SLING-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1386. --- Resource events for nt:file are not calculated properly --- Key: SLING-1386 URL: https://issues.apache.org/jira/browse/SLING-1386 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Resource 2.0.6 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.8 nt:file nodes have a jcr:content sub node which has the data as properties. If now the data property is changed, this results in jcr observation events for the jcr:content node and the current jcr observation to resource event bridge sends the jcr:content node as the resource. In these cases it is more correct to send the nt:file node as the resource. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1420) Remove FakeNode and FakeNodeType
[ https://issues.apache.org/jira/browse/SLING-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1420. --- Remove FakeNode and FakeNodeType Key: SLING-1420 URL: https://issues.apache.org/jira/browse/SLING-1420 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Resource 2.0.6 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.8 In order to make the jcr resource bundle jcr 2.0 compliant we should just add method stubs for the missing methods -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1423) Simplify Standalone script execution
[ https://issues.apache.org/jira/browse/SLING-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1423. --- Simplify Standalone script execution Key: SLING-1423 URL: https://issues.apache.org/jira/browse/SLING-1423 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor Fix For: JCR Resource 2.0.8 Executing a Sling script in standalone mode (i.e. without request/response) should be as simple as: Resource = ... SlingScript script = resource.adaptTo(SlingScript.class); SlingBindings bindings = new SlingBindings(); ...add values to bindings script.eval(bindings); Currently this does not work, and we should add tests for that once it works. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1430) Remove JcrResourceTypeProvider
[ https://issues.apache.org/jira/browse/SLING-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1430. --- Remove JcrResourceTypeProvider -- Key: SLING-1430 URL: https://issues.apache.org/jira/browse/SLING-1430 Project: Sling Issue Type: Improvement Affects Versions: JCR Resource 2.0.6 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.8 As discussed on the mailing list and voted (http://mail-archives.apache.org/mod_mbox/sling-dev/201003.mbox/%3c4b9505c3.4020...@apache.org%3E) we remove the JcrResourceTypeProvider interface (and add a new ResourceDecorator interface) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1486) JcrNodeResource.toString should not search super resource type but return it's own resource super type
[ https://issues.apache.org/jira/browse/SLING-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1486. --- JcrNodeResource.toString should not search super resource type but return it's own resource super type -- Key: SLING-1486 URL: https://issues.apache.org/jira/browse/SLING-1486 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Resource 2.0.6 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.8 Current the toString() method calls a search to get the resource super type - this is wrong as this might not return the resource super type defined for this resource. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1414) JSP Expression Language (eg: ${resource.path}) to call the getPath() method of a Resource object returned by ResourceResolver.findResources() result in error.
[
https://issues.apache.org/jira/browse/SLING-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-1414.
---
JSP Expression Language (eg: ${resource.path}) to call the getPath() method
of a Resource object returned by ResourceResolver.findResources() result in
error.
Key: SLING-1414
URL: https://issues.apache.org/jira/browse/SLING-1414
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: JCR Resource 2.0.6
Environment: CQ5.2.1/CQ5.3
Reporter: zhangchunlong
Assignee: Felix Meschberger
Priority: Minor
Fix For: JCR Resource 2.0.8
Often in the JSPs, we call the ResourceResolver.findResources(query, xpath)
method to return an IteratorResource object, which we iterate through using
JSTL and EL syntax. When we attempt to access the getPath() method of each
Resource, the following exception is thrown:
java.lang.IllegalAccessException: Class javax.el.BeanELResolver can not
access a member of class
org.apache.sling.jcr.resource.internal.helper.jcr.JcrItemResource with
modifiers public.
This works with CQ5.2.1 with no problem before. The issue happens on CQ5.3 GA
release.
Example codes to re-produce the error in CQ5.3.
IteratorResource found = resourceResolver.findResources(//element(*,
nt:unstructured),xpath);
while(found.hasNext()){
try{
Resource foundResource = found.next();
pageContext.setAttribute(foundResource, foundResource);
%${foundResource.path}%
}
catch(Exception e){
%%=e.getMessage()%%
}
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1429) Add support for ResourceDecorator i
[
https://issues.apache.org/jira/browse/SLING-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-1429.
---
Add support for ResourceDecorator i
---
Key: SLING-1429
URL: https://issues.apache.org/jira/browse/SLING-1429
Project: Sling
Issue Type: New Feature
Components: API, JCR
Affects Versions: JCR Resource 2.0.6, API 2.0.8
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: JCR Resource 2.0.8, API 2.1.0
As discussed in the mailing list, we add a new interface
interface ResourceDecorator {
Resource decorate(Resource)
Resource decorate(Resource, HttpServletRequest)
}
The registered decorators will be called from the resource resolver for each
resource returned.
The services will be called in the order of their service ranking
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1546) Disabling multi-workspaces doesn't do what it says in the metatype
[ https://issues.apache.org/jira/browse/SLING-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1546. --- Disabling multi-workspaces doesn't do what it says in the metatype -- Key: SLING-1546 URL: https://issues.apache.org/jira/browse/SLING-1546 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR Resource 2.0.8 Metatype says: If this is enabled, multiple workspaces are supported This includes registering observation listeners for all workspaces and allows to resolve resources from other workspaces than the default one. (resource.resolver.multiworkspace) --- Which is correct, but the reverse is not. Logic would say that the reverse would be... If this is disabled, multiple workspaces are not supported This includes registering observation listeners for only the default workspace and does not allows to resolve resources from other workspaces than the default one. (resource.resolver.multiworkspace) --- This was my original intent, just got lost along the way. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1553) result of findResources() not correctly wrapped with workspace name
[ https://issues.apache.org/jira/browse/SLING-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1553. --- result of findResources() not correctly wrapped with workspace name --- Key: SLING-1553 URL: https://issues.apache.org/jira/browse/SLING-1553 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR Resource 2.0.8 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1470) Sometimes redirect.cnd does not load first time.
[ https://issues.apache.org/jira/browse/SLING-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1470. --- Sometimes redirect.cnd does not load first time. Key: SLING-1470 URL: https://issues.apache.org/jira/browse/SLING-1470 Project: Sling Issue Type: Bug Components: JCR, Servlets Affects Versions: Servlets Get 2.0.8, JCR Resource 2.0.6 Reporter: Ian Boston Fix For: Servlets Get 2.1.0, JCR Resource 2.0.8 At times redriect.cnd does not load since it depends on resource.cnd as per [1] moving to jcr/resource bundle 1. http://markmail.org/thread/zat4qjtngysahbn3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1447) support for resource paths containing workspace name
[ https://issues.apache.org/jira/browse/SLING-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1447. --- support for resource paths containing workspace name Key: SLING-1447 URL: https://issues.apache.org/jira/browse/SLING-1447 Project: Sling Issue Type: Improvement Components: API, JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR Resource 2.0.8, API 2.1.0 Attachments: SLING-1447_adapttosession.patch, SLING-1447_post.patch via configuration, it'd be nice to be able to specify multiple workspaces. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1566) Add ResourceResolver.isLive() method
[ https://issues.apache.org/jira/browse/SLING-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1566. --- Add ResourceResolver.isLive() method Key: SLING-1566 URL: https://issues.apache.org/jira/browse/SLING-1566 Project: Sling Issue Type: Improvement Components: API, JCR Affects Versions: JCR Prefs 1.0.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Resource 2.0.8, API 2.1.0 SLING-1262 added a close() method to the ResourceResolver declaring that an exception will be thrown if the ResourceResolver is used after it has been closed. To be able to check a ResourceResolver in application code, an isLive method should be added. In addition, the actual exception -- IllegalStateException -- being thrown if the ResourceResolver has been closed should also be documented. Finally, in the JcrResourceReslver, the live-check is mainly implemented in the checkClosed() method. Probably this method should not only check the close state of itself but also, whether the underlying primary session is still alive. If the ResourceResolver has not been closed yet, but the session has already been logged out, the JcrResourceResolver may choose to close itself too (as a side effect). This is to be discussed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1572) jcr.resource bundle has wrong name
[ https://issues.apache.org/jira/browse/SLING-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1572. --- jcr.resource bundle has wrong name -- Key: SLING-1572 URL: https://issues.apache.org/jira/browse/SLING-1572 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Assignee: Justin Edelson Priority: Trivial Fix For: JCR Resource 2.0.8 This is minor, but occasionally annoying to me. It is Apache Sling Resource Resolver and should be Apache Sling JCR Resource Resolver -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1547) ResourceProviders aren't consulted for non-default workspace resources when listing children
[ https://issues.apache.org/jira/browse/SLING-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1547. --- ResourceProviders aren't consulted for non-default workspace resources when listing children Key: SLING-1547 URL: https://issues.apache.org/jira/browse/SLING-1547 Project: Sling Issue Type: Bug Components: JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR Resource 2.0.8 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1516) FSResource Provider throws exception on first activate.
[ https://issues.apache.org/jira/browse/SLING-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1516. --- FSResource Provider throws exception on first activate. --- Key: SLING-1516 URL: https://issues.apache.org/jira/browse/SLING-1516 Project: Sling Issue Type: Bug Affects Versions: File System Resource Provider 0.9.2 Reporter: Ian Boston Assignee: Ian Boston Fix For: File System Resource Provider 1.0.2 04.05.2010 11:07:03.367 *ERROR* [SCR Component Actor] org.apache.sling.fsresource [org.apache.sling.fsprovider.internal.FsResourceProvider] The activate method has thrown an exception (java.lang.IllegalArgumentException: provider.roots property must be set) java.lang.IllegalArgumentException: provider.roots property must be set at org.apache.sling.fsprovider.internal.FsResourceProvider.activate(FsResourceProvider.java:206) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.felix.scr.impl.helper.BaseMethod.invokeMethod(BaseMethod.java:213) at org.apache.felix.scr.impl.helper.BaseMethod.access$500(BaseMethod.java:38) Seeing these when FSResource is present and not configured. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1527) resourceResolver.listChildren() doesn't handle non-default workspace nodes
[ https://issues.apache.org/jira/browse/SLING-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1527. --- resourceResolver.listChildren() doesn't handle non-default workspace nodes -- Key: SLING-1527 URL: https://issues.apache.org/jira/browse/SLING-1527 Project: Sling Issue Type: Bug Components: JCR Reporter: Justin Edelson Fix For: JCR Resource 2.0.8 if passed a resource from a non-default workspace, resourceResolver.listChildren() returns an empty list. This is because non-default workspace nodes are wrapped and thus not castable to JcrItemResource, which causes JcrResourceProvider to try to retreive the node path INCLUDING the workspace prefix from the JCR repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1525) JcrResourceListenerTest#testInWs2 fails with the actual trunk on fastmachines from time to time.
[ https://issues.apache.org/jira/browse/SLING-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1525. --- JcrResourceListenerTest#testInWs2 fails with the actual trunk on fastmachines from time to time. -- Key: SLING-1525 URL: https://issues.apache.org/jira/browse/SLING-1525 Project: Sling Issue Type: Bug Components: Testing Affects Versions: JCR Resource 2.0.6 Environment: Win XP SP3, Maven 2.2.1 Reporter: Mike Müller Assignee: Carsten Ziegeler Priority: Trivial Fix For: JCR Resource 2.0.8 Attachments: SLING-1525.patch Failure: testInWs2(org.apache.sling.jcr.resource.internal.JcrResourceListenerTest) AssertionFailedError: expected:ws2:/test1274309020796 but was:ws2:/test1274309020796[2] It seems, that createTestPath produces more than one time the same path (because called in the same millisecond). If we extend the path with a random number everything seems to be okay. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1551) Workspace names need to be stripped inside JcrResourceResolver.map()
[ https://issues.apache.org/jira/browse/SLING-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1551. --- Workspace names need to be stripped inside JcrResourceResolver.map() Key: SLING-1551 URL: https://issues.apache.org/jira/browse/SLING-1551 Project: Sling Issue Type: Bug Components: JCR Reporter: Justin Edelson Assignee: Justin Edelson Priority: Minor Fix For: JCR Resource 2.0.8 map(ws:/path) should return /path -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1595) Add a jcr:path property to JcrPropertyMap
[ https://issues.apache.org/jira/browse/SLING-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1595. --- Add a jcr:path property to JcrPropertyMap - Key: SLING-1595 URL: https://issues.apache.org/jira/browse/SLING-1595 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Fix For: JCR Resource 2.0.8 Although it can be computed, it would be nice to always have access to a jcr:path property via the ValueMap. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1618) JCR Session attribute impersonator not set any more
[ https://issues.apache.org/jira/browse/SLING-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1618. --- JCR Session attribute impersonator not set any more - Key: SLING-1618 URL: https://issues.apache.org/jira/browse/SLING-1618 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Resource 2.0.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Resource 2.0.8 While switching the Commons Auth implementation to use the new ResourceResolverFactory service instead of directly creating JCR sessions (SLING-1534, Rev. 950104), the functionality to set the impersonator session attribute on an impersonated session has been lost. This should be added again to the JcrResourceResolverFactoryImpl.handleSudo method again. In addition, copying over all of the Authentication Info parameters (except any parameters whose name contains the word password, particularly user.password) might also be added. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1672) resource.resourceResolver.listChildren only enlists jcr nodes but not all child resources
[ https://issues.apache.org/jira/browse/SLING-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1672. --- resource.resourceResolver.listChildren only enlists jcr nodes but not all child resources - Key: SLING-1672 URL: https://issues.apache.org/jira/browse/SLING-1672 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Resource 2.0.6 Environment: sling from trunk (as of August 20th 2010) Reporter: Clemens Wyss Assignee: Felix Meschberger Fix For: JCR Resource 2.0.8 in my esp-script I have the follwoing line: var childResources = request.resourceResolver.listChildren(resource ); In my pom.xml I have the follwoing declaration: Sling-Bundle-Resources /res/sling/explorer;overwrite:=true;uninstall=true;path:=/libs/sling/explorer /Sling-Bundle-Resources i.e. I map /res/sling/explorer to /libs/sling/explorer. And I can directly access the files beneath /res/sling/explorer, e.g. http://localhost:8080/res/sling/explorer/css/explorer.css. I.e. resolving seems to work But when I enlist (which end up in BundleResourceProvider#listChildren()) on the root (/) I don't see 'res' -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1705) Proactively set length of jcr:data property for nt:file node resources
[ https://issues.apache.org/jira/browse/SLING-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1705. --- Proactively set length of jcr:data property for nt:file node resources -- Key: SLING-1705 URL: https://issues.apache.org/jira/browse/SLING-1705 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Resource 2.0.6 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Resource 2.0.8 A resource wrapping a node of type nt:file provides access to the jcr:content/jcr:data by an adapter to the InputStream. In this case, the Property.getLength() value of the jcr:content/jcr:data property can be considered the content length of the resource and should be set in the ResourceMetadata accordingly. Currently (as of SLING-288) the content length metadata property is only set when the resource is adapted to an InputStream. Same holds for Property-based resources. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1590) OSGi events should contain a userID when possible.
[ https://issues.apache.org/jira/browse/SLING-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1590. --- OSGi events should contain a userID when possible. -- Key: SLING-1590 URL: https://issues.apache.org/jira/browse/SLING-1590 Project: Sling Issue Type: Improvement Components: API, JCR Affects Versions: JCR Resource 2.0.8, API 2.0.8 Reporter: Simon Gaeremynck Assignee: Justin Edelson Fix For: JCR Resource 2.0.8, API 2.1.0 Attachments: userids-in-events.diff We're building a system that tracks the user's movements in the system. One of the things we're tracking is the OSGi events that are emitted by Sling. These don't contain a userid however. Since this all hapens in the JcrResourceListener which is a JCR Observation Listener, getting the userID is fairly straightforward. I'll attach a patch that includes this functionality. AFAICT this is the only location that emits user generated events, if I missed a spot I'd be happy to try and patch that one as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1640) Add ResourceResolver.clone(Map) method
[ https://issues.apache.org/jira/browse/SLING-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1640. --- Add ResourceResolver.clone(Map) method --- Key: SLING-1640 URL: https://issues.apache.org/jira/browse/SLING-1640 Project: Sling Issue Type: New Feature Components: API, JCR Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Resource 2.0.8, API 2.1.0 As discussed on the list the ResourceResolver interface should be extended with a new method: ResourceResolver clone(Map credentials); This method creates a new ResourceResolver as follows: // start with original credentials Map newCredentials = new HashMap(current resolver credentials); // overlay with provided credentials newCredentials.addAll(credentials); // return a new ResourceResolver return resourceResolverFactory.login(newCredentials); This new method allows for the removal of the AuthenticationInfo object from the request attributes (as discussed in SLING-1445) and allows for a better implementation of the background servlet 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-1633) After unregistering a ResourceDecorator service any request causes a NullPointerException to be thrown
[ https://issues.apache.org/jira/browse/SLING-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1633. --- After unregistering a ResourceDecorator service any request causes a NullPointerException to be thrown -- Key: SLING-1633 URL: https://issues.apache.org/jira/browse/SLING-1633 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Resource 2.0.6 Reporter: Davide Maestroni Assignee: Felix Meschberger Priority: Critical Fix For: JCR Resource 2.0.8 After registering and then unregistering a service implementing the ResourceDecorator interface, any request causes a NullPointerException thus making the whole repository unusable even if the HTTP response code is always 200 (see trace below). 09.08.2010 12:23:15.109 *INFO* [127.0.0.1 [1281349395109] GET /sling/content.json HTTP/1.1] logs/request.log 09/Aug/2010:12:23:15 +0200 [2] - 200 - 0ms 09.08.2010 12:23:15.109 *INFO* [127.0.0.1 [1281349395109] GET /sling/content.json HTTP/1.1] logs/access.log 127.0.0.1 - admin 09/Aug/2010:12:23:15 +0200 GET /sling/content.json HTTP/1.1 200 - - curl/7.19.5 (i586-pc-mingw32msvc) libcurl/7.19.5 zlib/1.2.3 09.08.2010 12:23:15.109 *ERROR* [127.0.0.1 [1281349395109] GET /sling/content.json HTTP/1.1] org.apache.sling.engine.impl.SlingMainServlet service: Uncaught Problem handling the request java.lang.NullPointerException at org.apache.sling.engine.impl.SlingHttpServletRequestImpl.getResource(SlingHttpServletRequestImpl.java:107) at org.apache.sling.servlets.resolver.internal.SlingServletResolver.getErrorResource(SlingServletResolver.java:537) at org.apache.sling.servlets.resolver.internal.SlingServletResolver.handleError(SlingServletResolver.java:490) at org.apache.sling.engine.impl.SlingMainServlet.service(SlingMainServlet.java:363) at org.apache.sling.engine.impl.SlingMainServlet.service(SlingMainServlet.java:207) at org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:91) at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:77) at org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42) at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49) at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33) at org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48) at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39) at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.felix.http.proxy.ProxyServlet.service(ProxyServlet.java:60) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.sling.launchpad.base.webapp.SlingServletDelegate.service(SlingServletDelegate.java:275) at org.apache.sling.launchpad.webapp.SlingServlet.service(SlingServlet.java:148) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:527) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:423) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:456) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:924) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:358) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:860) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:245) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113) at org.eclipse.jetty.server.Server.handle(Server.java:335) at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:588) at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:1029) at
[jira] Closed: (SLING-1646) Expose subset of authentication info properties as ResourceResolver attributes
[ https://issues.apache.org/jira/browse/SLING-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1646. --- Expose subset of authentication info properties as ResourceResolver attributes -- Key: SLING-1646 URL: https://issues.apache.org/jira/browse/SLING-1646 Project: Sling Issue Type: Improvement Components: API, JCR Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Resource 2.0.8, API 2.1.0 The properties of the authentication info (or credentials map) provided to the ResoureResolverFactory to create a new ResourceResolver should be exposed by the ResourceResolver. Exceptions apply to any passwords or JCR Credentials or other identifiable sensitive information, which should of course not be exposed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1767) Update JCR Resource Import-Package to require o.a.s.c.osgi version 2.0.6
[ https://issues.apache.org/jira/browse/SLING-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1767. --- Update JCR Resource Import-Package to require o.a.s.c.osgi version 2.0.6 Key: SLING-1767 URL: https://issues.apache.org/jira/browse/SLING-1767 Project: Sling Issue Type: Bug Components: JCR Reporter: Julian Sedding Assignee: Carsten Ziegeler Fix For: JCR Resource 2.0.8 For JCR Resource 2.0.8 the Import-Package statement in pom.xml needs to be updated to require o.a.s.c.osgi version 2.0.6. RootResourceProviderEntry makes use of OsgiUtil#getComparableForServiceRanking(), which only exists since 2.0.6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1781) bad String equality check in jcr.resource
[ https://issues.apache.org/jira/browse/SLING-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1781. --- bad String equality check in jcr.resource - Key: SLING-1781 URL: https://issues.apache.org/jira/browse/SLING-1781 Project: Sling Issue Type: Bug Components: JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR Resource 2.0.8 in a few locations in jcr.resource == is used to test for String equality. This is bad. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1647) Cleanup Authentication Info constants and implementation
[ https://issues.apache.org/jira/browse/SLING-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1647. --- Cleanup Authentication Info constants and implementation Key: SLING-1647 URL: https://issues.apache.org/jira/browse/SLING-1647 Project: Sling Issue Type: Improvement Components: API, Authentication, JCR Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Resource 2.0.8, Auth Core 1.0.0, API 2.1.0 The constants defined on the AuthenticationInfo class in the Commons Auth bundle should be moved as follows: USER = user.name to the ResourceResolverFactory interface PASSWORD = user.password; to the ResourceResolverFactory interface CREDENTIALS = user.jcr.credentials; to the JcrResourceResolverFactory interface In addition support for checking the type of a credentials property is to be removed from the AuthenticationInfo class. Likewise the following constants currently internal to the JcrResourceResolverFactoryImpl class should be moved: AUTH_INFO_WORKSPACE = internal.user.jcr.workspace; to the JcrResourceResolverFactory interface and change value to user.jcr.workspace (removing the internal prefix) SESSION_ATTR_IMPERSONATOR = impersonator; to the ResourceResolverFactory interface Finally the following constant from the ResourceResolverFactory interface should be changed: SUDO_USER_ID = sudo.user.id; change the value to user.impersonation At the end use constants should be ensured, mostly in the JcrResourceResolverFactoryImpl and JcrResourceResolver classes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1726) Namespace mangling is broken for path segments with a leading underscore
[ https://issues.apache.org/jira/browse/SLING-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1726. --- Namespace mangling is broken for path segments with a leading underscore Key: SLING-1726 URL: https://issues.apache.org/jira/browse/SLING-1726 Project: Sling Issue Type: Bug Components: JCR Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Resource 2.0.8 Consider a node at /content/_test/jcr:content With namespace mangling, this node should be accessible with the URL path /content/_test/_jcr_content where the _jcr_ prefix is converted to the correct namespace prefix jcr: but the prefixed underscore _ of the _test node must be left unmodified. The regular expression to find and replace the namespace prefixes -- /_([^_]+)_ -- is setup to match anything enclosed with /_ and _. Thus the test path would match /_test/_ and fail to convert this (of course test/ is not a valid, registered namespace prefix). But subsequently the real prefix -- _jcr_ -- is actually missed. The regular expression must be modified to not match any slash characters, thus /_([^_/]+)_ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1906) Allow scheme/host/port mapping in the vanityUrls
[ https://issues.apache.org/jira/browse/SLING-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1906. --- Allow scheme/host/port mapping in the vanityUrls Key: SLING-1906 URL: https://issues.apache.org/jira/browse/SLING-1906 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Resource 2.0.6 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Priority: Minor Fix For: JCR Resource 2.0.8 The vanity url path property on a node is currently assumed to be an absolute path. This prevents vanity urls to be domain specific - the easiest solution is to allow complete urls as a vanity path - in this case the vanity path only matches if scheme, host and port match as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1861) Support jcr:mixinTypes for jcr powered persistable value map
[
https://issues.apache.org/jira/browse/SLING-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-1861.
---
Support jcr:mixinTypes for jcr powered persistable value map
Key: SLING-1861
URL: https://issues.apache.org/jira/browse/SLING-1861
Project: Sling
Issue Type: New Feature
Components: JCR
Affects Versions: JCR Resource 2.0.6
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: JCR Resource 2.0.8
It would be nice if the jcr powered persistable value map supports setting
mixin node types through the jcr:mixinTypes property:
PersistableValueMap pvm;
String[] types = pvm.get(jcr:mixinTypes,
String[].class);
if ( types == null ) {
pvm.put(jcr:mixinTypes, slingshot:Photo);
} else {
String[] newTypes = new String[types.length + 1];
System.arraycopy(types, 0, newTypes, 0,
types.length);
newTypes[types.length] = slingshot:Photo;
pvm.put(jcr:mixinTypes, newTypes);
}
If a mixin type is several times in the array, it is only applied once.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
