[jira] Commented: (SLING-1445) store the AuthenticationInfo object in a request attribute
[ https://issues.apache.org/jira/browse/SLING-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12896210#action_12896210 ] Justin Edelson commented on SLING-1445: --- IIRC, my use case was to log into a different workspace using the same credentials. copy() obviously won't help for this. Apologies for not documenting the rationale. I can probably get by with a combination of loginAdministrative and impersonate if you want to roll this back. (Bertrand - as an aside, I briefly looked at the class linked to above and didn't see the ResourceResolver being closed. Maybe I just missed it, but I figured it was worth mentioning.) store the AuthenticationInfo object in a request attribute -- Key: SLING-1445 URL: https://issues.apache.org/jira/browse/SLING-1445 Project: Sling Issue Type: Improvement Components: Commons Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Commons Auth 1.0.0 called org.apache.sling.commons.auth.spi.AuthenticationInfo -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1445) store the AuthenticationInfo object in a request attribute
[ https://issues.apache.org/jira/browse/SLING-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12896499#action_12896499 ] Justin Edelson commented on SLING-1445: --- This looks ok to me. store the AuthenticationInfo object in a request attribute -- Key: SLING-1445 URL: https://issues.apache.org/jira/browse/SLING-1445 Project: Sling Issue Type: Improvement Components: Commons Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Commons Auth 1.0.0 called org.apache.sling.commons.auth.spi.AuthenticationInfo -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (SLING-1654) Remove JCR Session as request attribte
[ https://issues.apache.org/jira/browse/SLING-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson reopened SLING-1654: --- Assignee: Justin Edelson (was: Felix Meschberger) this change brakes all the integration tests due to an issue with the webdav bundle. Remove JCR Session as request attribte -- Key: SLING-1654 URL: https://issues.apache.org/jira/browse/SLING-1654 Project: Sling Issue Type: Task Components: Commons Reporter: Felix Meschberger Assignee: Justin Edelson Fix For: Auth Core 1.0.0 Currently the SlingAuthenticator sets the following three request attributes in the Authenticator.handleSecurity method besides the attributes required by the OSGi Http Service spec: javax.jcr.Session -- the primary session underlying the resource resolver $$org.apache.sling.commons.auth.impl.SlingAuthenticatorResourceResolver$$ -- internal wrapper to help logout the resource resolver org.apache.sling.commons.auth.ResourceResolver -- the request's resource resolver The Session is here for backwards compatibility for a long time now. The official way to get at a session in requests has long been to adapt the request's resource resolver to a Session. Keeping the Session as a request attribute just makes cleaning up at the end more complicated. The $$org.apache.sling.commons.auth.impl.SlingAuthenticatorResourceResolver$$ request attribute has been introduce with the commons auth module but before the ResourceResolver.close() method to cleanup the resource resolver and session after request processing. This request attribute is not needed any longer thanks to the ResourceResolver.close() method which allows for propery cleanup. This the $$org.apache.sling.commons.auth.impl.SlingAuthenticatorResourceResolver$$ and javax.jcr.Session request attributes should not be set any longer. As kind of a replacement, JavaDoc of the Authenticator interface and particularly the Authenticator.handleSecurity method should be enhanced to list the request attributes be set and to request from the caller to call the close() method on the resource resovler at then end of request processing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1654) Remove JCR Session as request attribte
[ https://issues.apache.org/jira/browse/SLING-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1654. --- Resolution: Fixed webdav bundle updated in r985944 Remove JCR Session as request attribte -- Key: SLING-1654 URL: https://issues.apache.org/jira/browse/SLING-1654 Project: Sling Issue Type: Task Components: Commons, JCR Reporter: Felix Meschberger Assignee: Justin Edelson Fix For: JCR Webdav 2.0.10, Auth Core 1.0.0 Currently the SlingAuthenticator sets the following three request attributes in the Authenticator.handleSecurity method besides the attributes required by the OSGi Http Service spec: javax.jcr.Session -- the primary session underlying the resource resolver $$org.apache.sling.commons.auth.impl.SlingAuthenticatorResourceResolver$$ -- internal wrapper to help logout the resource resolver org.apache.sling.commons.auth.ResourceResolver -- the request's resource resolver The Session is here for backwards compatibility for a long time now. The official way to get at a session in requests has long been to adapt the request's resource resolver to a Session. Keeping the Session as a request attribute just makes cleaning up at the end more complicated. The $$org.apache.sling.commons.auth.impl.SlingAuthenticatorResourceResolver$$ request attribute has been introduce with the commons auth module but before the ResourceResolver.close() method to cleanup the resource resolver and session after request processing. This request attribute is not needed any longer thanks to the ResourceResolver.close() method which allows for propery cleanup. This the $$org.apache.sling.commons.auth.impl.SlingAuthenticatorResourceResolver$$ and javax.jcr.Session request attributes should not be set any longer. As kind of a replacement, JavaDoc of the Authenticator interface and particularly the Authenticator.handleSecurity method should be enhanced to list the request attributes be set and to request from the caller to call the close() method on the resource resovler at then end of request processing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1658) Switch logging implementation used during testing to logback
Switch logging implementation used during testing to logback Key: SLING-1658 URL: https://issues.apache.org/jira/browse/SLING-1658 Project: Sling Issue Type: Improvement Components: Launchpad, Testing Reporter: Justin Edelson Assignee: Justin Edelson Priority: Minor Fix For: Launchpad Testing 6 See JCR-2584 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1659) log each integration test case in a separate file
log each integration test case in a separate file - Key: SLING-1659 URL: https://issues.apache.org/jira/browse/SLING-1659 Project: Sling Issue Type: Improvement Components: Testing, Launchpad, Commons Reporter: Justin Edelson Assignee: Justin Edelson Priority: Minor Fix For: Launchpad Testing 6, Commons Testing 2.0.6 see JCR-2693 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1658) Switch logging implementation used during testing to logback
[ https://issues.apache.org/jira/browse/SLING-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12898957#action_12898957 ] Justin Edelson commented on SLING-1658: --- done in r985979 Switch logging implementation used during testing to logback Key: SLING-1658 URL: https://issues.apache.org/jira/browse/SLING-1658 Project: Sling Issue Type: Improvement Components: Launchpad, Testing Reporter: Justin Edelson Assignee: Justin Edelson Priority: Minor Fix For: Launchpad Testing 6 See JCR-2584 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1659) log each integration test case in a separate file
[ https://issues.apache.org/jira/browse/SLING-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1659. --- Resolution: Fixed log each integration test case in a separate file - Key: SLING-1659 URL: https://issues.apache.org/jira/browse/SLING-1659 Project: Sling Issue Type: Improvement Components: Commons, Launchpad, Testing Reporter: Justin Edelson Assignee: Justin Edelson Priority: Minor Fix For: Launchpad Testing 6, Commons Testing 2.0.6 see JCR-2693 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1659) log each integration test case in a separate file
[ https://issues.apache.org/jira/browse/SLING-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12898959#action_12898959 ] Justin Edelson commented on SLING-1659: --- done in r985980 log each integration test case in a separate file - Key: SLING-1659 URL: https://issues.apache.org/jira/browse/SLING-1659 Project: Sling Issue Type: Improvement Components: Commons, Launchpad, Testing Reporter: Justin Edelson Assignee: Justin Edelson Priority: Minor Fix For: Launchpad Testing 6, Commons Testing 2.0.6 see JCR-2693 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1660) upgrade to Jackrabbit 2.1.1
upgrade to Jackrabbit 2.1.1 --- Key: SLING-1660 URL: https://issues.apache.org/jira/browse/SLING-1660 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1661) compute the digest when a dictionary is read from the input stream
compute the digest when a dictionary is read from the input stream -- Key: SLING-1661 URL: https://issues.apache.org/jira/browse/SLING-1661 Project: Sling Issue Type: Improvement Components: Installer Reporter: Justin Edelson Attachments: SLING-1661.patch currently, if this call is made: new InstallableResource(id, is, null, null, InstallableResource.TYPE_CONFIG, null) an error will be thrown because the digest is null. But this isn't necessary because we can generate the digest from the parsed dictionary -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1661) compute the digest when a dictionary is read from the input stream
[ https://issues.apache.org/jira/browse/SLING-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1661: -- Attachment: SLING-1661.patch compute the digest when a dictionary is read from the input stream -- Key: SLING-1661 URL: https://issues.apache.org/jira/browse/SLING-1661 Project: Sling Issue Type: Improvement Components: Installer Reporter: Justin Edelson Attachments: SLING-1661.patch currently, if this call is made: new InstallableResource(id, is, null, null, InstallableResource.TYPE_CONFIG, null) an error will be thrown because the digest is null. But this isn't necessary because we can generate the digest from the parsed dictionary -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1661) compute the digest when a dictionary is read from the input stream
[ https://issues.apache.org/jira/browse/SLING-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899218#action_12899218 ] Justin Edelson commented on SLING-1661: --- here's a patch. compute the digest when a dictionary is read from the input stream -- Key: SLING-1661 URL: https://issues.apache.org/jira/browse/SLING-1661 Project: Sling Issue Type: Improvement Components: Installer Reporter: Justin Edelson Attachments: SLING-1661.patch currently, if this call is made: new InstallableResource(id, is, null, null, InstallableResource.TYPE_CONFIG, null) an error will be thrown because the digest is null. But this isn't necessary because we can generate the digest from the parsed dictionary -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1257) Add a JSON Groovy Builder to commons.json
[ https://issues.apache.org/jira/browse/SLING-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899224#action_12899224 ] Justin Edelson commented on SLING-1257: --- note - this was subsequently moved to the extensions.groovy module. See SLING-1339. Add a JSON Groovy Builder to commons.json - Key: SLING-1257 URL: https://issues.apache.org/jira/browse/SLING-1257 Project: Sling Issue Type: Improvement Components: Commons Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Commons JSON 2.0.6 json-lib has a Groovy Builder which faciliates the easy creation of JSON documents. Since Sling uses a its own JSON library (and json-lib isn't OSGi-friendly), this can't be used directly. Instead, something inspired by json-lib's builder can be added to commons.json -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1662) Add a GString / GSP Script engine(s)
Add a GString / GSP Script engine(s) Key: SLING-1662 URL: https://issues.apache.org/jira/browse/SLING-1662 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Justin Edelson -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1662) Add a GString / GSP Script engine(s)
[ https://issues.apache.org/jira/browse/SLING-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1662: -- Fix Version/s: Groovy Extensions 1.0.0 Add a GString / GSP Script engine(s) Key: SLING-1662 URL: https://issues.apache.org/jira/browse/SLING-1662 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Justin Edelson Fix For: Groovy Extensions 1.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1662) Add a GString / GSP Script engine(s)
[ https://issues.apache.org/jira/browse/SLING-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1662: -- Assignee: Justin Edelson Add a GString / GSP Script engine(s) Key: SLING-1662 URL: https://issues.apache.org/jira/browse/SLING-1662 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Groovy Extensions 1.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1664) support reading the jackrabbit configuration file from the launchpad archive
support reading the jackrabbit configuration file from the launchpad archive Key: SLING-1664 URL: https://issues.apache.org/jira/browse/SLING-1664 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson downstream users of Sling should be able to put a repository.xml in either the launchpad JAR or WAR and get it to work without any additional configuration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1662) Add a GString / GSP Script engine(s)
[ https://issues.apache.org/jira/browse/SLING-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1662. --- Resolution: Fixed done in r986420 uses the GStringTemplateEngine described here: http://groovy.codehaus.org/Groovy+Templates Add a GString / GSP Script engine(s) Key: SLING-1662 URL: https://issues.apache.org/jira/browse/SLING-1662 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Groovy Extensions 1.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1665) Revision 985214 failed to export the org.apache.sling.api.services package
[ https://issues.apache.org/jira/browse/SLING-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899558#action_12899558 ] Justin Edelson commented on SLING-1665: --- there's no package named org.apache.sling.api.services in the sling.api bundle. Revision 985214 failed to export the org.apache.sling.api.services package -- Key: SLING-1665 URL: https://issues.apache.org/jira/browse/SLING-1665 Project: Sling Issue Type: Bug Components: API Reporter: Drake Callahan The following change includes an update to the maven bundle plugin to explicitly list exports. The org.apache.sling.api.services package is not included in this list; but is depended on. Revision 985214 Jump to revision: Author: fmeschbe Date: Fri Aug 13 14:42:23 2010 UTC (4 days, 4 hours ago) Changed paths:3 Log Message: * JavaDoc Fixes * Explicitly list all exported packages with their export version * Set JIRA version reference property -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (SLING-1665) Revision 985214 failed to export the org.apache.sling.api.services package
[ https://issues.apache.org/jira/browse/SLING-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899558#action_12899558 ] Justin Edelson edited comment on SLING-1665 at 8/17/10 4:17 PM: there's no package named org.apache.sling.api.services in the sling.api bundle. The contents of this package are now in the settings bundle (extensions/settings) in the org.apache.sling.settings package. See SLING-1460 was (Author: justinedelson): there's no package named org.apache.sling.api.services in the sling.api bundle. Revision 985214 failed to export the org.apache.sling.api.services package -- Key: SLING-1665 URL: https://issues.apache.org/jira/browse/SLING-1665 Project: Sling Issue Type: Bug Components: API Reporter: Drake Callahan The following change includes an update to the maven bundle plugin to explicitly list exports. The org.apache.sling.api.services package is not included in this list; but is depended on. Revision 985214 Jump to revision: Author: fmeschbe Date: Fri Aug 13 14:42:23 2010 UTC (4 days, 4 hours ago) Changed paths:3 Log Message: * JavaDoc Fixes * Explicitly list all exported packages with their export version * Set JIRA version reference property -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1665) Revision 985214 failed to export the org.apache.sling.api.services package
[ https://issues.apache.org/jira/browse/SLING-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1665. --- Resolution: Invalid Revision 985214 failed to export the org.apache.sling.api.services package -- Key: SLING-1665 URL: https://issues.apache.org/jira/browse/SLING-1665 Project: Sling Issue Type: Bug Components: API Reporter: Drake Callahan The following change includes an update to the maven bundle plugin to explicitly list exports. The org.apache.sling.api.services package is not included in this list; but is depended on. Revision 985214 Jump to revision: Author: fmeschbe Date: Fri Aug 13 14:42:23 2010 UTC (4 days, 4 hours ago) Changed paths:3 Log Message: * JavaDoc Fixes * Explicitly list all exported packages with their export version * Set JIRA version reference property -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1667) GSP script engine should use dynamic class loader
GSP script engine should use dynamic class loader - Key: SLING-1667 URL: https://issues.apache.org/jira/browse/SLING-1667 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Groovy Extensions 1.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1667) GSP script engine should use dynamic class loader
[ https://issues.apache.org/jira/browse/SLING-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1667. --- Resolution: Fixed done in r986780 GSP script engine should use dynamic class loader - Key: SLING-1667 URL: https://issues.apache.org/jira/browse/SLING-1667 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Groovy Extensions 1.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1560) Improve and clean up code
[ https://issues.apache.org/jira/browse/SLING-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899924#action_12899924 ] Justin Edelson commented on SLING-1560: --- fixed failing IT in r986813 Improve and clean up code - Key: SLING-1560 URL: https://issues.apache.org/jira/browse/SLING-1560 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: OSGi Installer 3.0.0, JCR Installer 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: OSGi Installer 3.0.0, JCR Installer 3.0.0 In order to fix some outstanding bugs and to add new features, a code review and clean up seems to be a good idea :) This bug will keep track of all changes to the code that don't add new features -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (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 ] Justin Edelson reassigned SLING-1672: - Assignee: Justin Edelson 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: Justin Edelson 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] Created: (SLING-1674) BundleResourceProvider.listChildren() doesn't handle mapped paths
BundleResourceProvider.listChildren() doesn't handle mapped paths - Key: SLING-1674 URL: https://issues.apache.org/jira/browse/SLING-1674 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Justin Edelson Assignee: Justin Edelson If a path is mapped using the Sling-Bundle-Resources manifest header, then the contents of that path aren't listed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1674) BundleResourceProvider.listChildren() doesn't handle mapped paths
[ https://issues.apache.org/jira/browse/SLING-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1674: -- Fix Version/s: Extensions Bundleresource 2.0.6 BundleResourceProvider.listChildren() doesn't handle mapped paths - Key: SLING-1674 URL: https://issues.apache.org/jira/browse/SLING-1674 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Extensions Bundleresource 2.0.6 If a path is mapped using the Sling-Bundle-Resources manifest header, then the contents of that path aren't listed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1674) BundleResourceProvider.listChildren() doesn't handle mapped paths
[ https://issues.apache.org/jira/browse/SLING-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1674. --- Resolution: Fixed this is fixed in r987545, but it turns out to be a slightly different problem than SLING-1672 BundleResourceProvider.listChildren() doesn't handle mapped paths - Key: SLING-1674 URL: https://issues.apache.org/jira/browse/SLING-1674 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Extensions Bundleresource 2.0.6 If a path is mapped using the Sling-Bundle-Resources manifest header, then the contents of that path aren't listed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1660) upgrade to Jackrabbit 2.1.1
[ https://issues.apache.org/jira/browse/SLING-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1660: -- Assignee: Justin Edelson upgrade to Jackrabbit 2.1.1 --- Key: SLING-1660 URL: https://issues.apache.org/jira/browse/SLING-1660 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Assignee: Justin Edelson -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (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:comment-tabpanelfocusedCommentId=12900745#action_12900745 ] Justin Edelson commented on SLING-1672: --- This is trickier than I thought... The BundleResourceProvider provides resources starting with the path in the manifest. I'm not sure that the BundleResourceProvider should be *providing* the /res resource in this case. There was an issue with listing the contents of a mapped path (SLING-1674) which I found while looking into this, but that's not the issue here. This issue is that the resource provider doesn't provide resources which don't start with /res/sling/explorer and that seems to be to be the correct behavior. 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: Justin Edelson 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] Resolved: (SLING-1660) upgrade to Jackrabbit 2.1.1
[ https://issues.apache.org/jira/browse/SLING-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1660. --- Fix Version/s: JCR Webdav 2.0.10 JCR Jackrabbit Server 2.0.8 JCR DavEx 1.0.0 Commons Testing 2.0.6 Resolution: Fixed done in r987559 upgrade to Jackrabbit 2.1.1 --- Key: SLING-1660 URL: https://issues.apache.org/jira/browse/SLING-1660 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR Webdav 2.0.10, JCR Jackrabbit Server 2.0.8, JCR DavEx 1.0.0, Commons Testing 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] Updated: (SLING-1660) upgrade to Jackrabbit 2.1.1
[ https://issues.apache.org/jira/browse/SLING-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1660: -- Component/s: Commons upgrade to Jackrabbit 2.1.1 --- Key: SLING-1660 URL: https://issues.apache.org/jira/browse/SLING-1660 Project: Sling Issue Type: Improvement Components: Commons, JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR Webdav 2.0.10, JCR Jackrabbit Server 2.0.8, JCR DavEx 1.0.0, Commons Testing 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] Commented: (SLING-783) SlingPostServlet's jcr:mixinTypes parameter is not tested
[ https://issues.apache.org/jira/browse/SLING-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12900753#action_12900753 ] Justin Edelson commented on SLING-783: -- This is being exercised as part of the versionable post tests. SlingPostServlet's jcr:mixinTypes parameter is not tested - Key: SLING-783 URL: https://issues.apache.org/jira/browse/SLING-783 Project: Sling Issue Type: Test Components: Testing Reporter: Bertrand Delacretaz I don't think we have tests for the jcr:mixinTypes parameter of the SlingPostServlet. The description of that feature at http://incubator.apache.org/sling/site/manipulating-content-the-slingpostservlet.html is also incomplete, there's no example. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1675) BundleResourceProvider doesn't provide resources when asked to list the children of a mapped path
BundleResourceProvider doesn't provide resources when asked to list the children of a mapped path - Key: SLING-1675 URL: https://issues.apache.org/jira/browse/SLING-1675 Project: Sling Issue Type: Bug Components: Extensions Reporter: Justin Edelson If you have Sling-Bundle-Resources/foo/bar/Sling-Bundle-Resources and the resource at /foo exists (say, provided by the JCR Resource Provider), then a call to BundleResourceProvider.listChildren(resource) where the resource is an existing resource at /foo, then BRP should return an iterator over the root bundle resource (i.e. /foo/bar in this case). This is similar to SLING-1672 with the difference being that /foo/bar is a legitimate bundle resource, whereas SLING-1672 is about having BRP provide a resource in listChildren() which it will not in getResource(). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1675) BundleResourceProvider doesn't provide resources when asked to list the children of a mapped path
[ https://issues.apache.org/jira/browse/SLING-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12900760#action_12900760 ] Justin Edelson commented on SLING-1675: --- patch for this at http://codereview.appspot.com/242 but I have doubts if this is a good idea. BundleResourceProvider doesn't provide resources when asked to list the children of a mapped path - Key: SLING-1675 URL: https://issues.apache.org/jira/browse/SLING-1675 Project: Sling Issue Type: Bug Components: Extensions Reporter: Justin Edelson If you have Sling-Bundle-Resources/foo/bar/Sling-Bundle-Resources and the resource at /foo exists (say, provided by the JCR Resource Provider), then a call to BundleResourceProvider.listChildren(resource) where the resource is an existing resource at /foo, then BRP should return an iterator over the root bundle resource (i.e. /foo/bar in this case). This is similar to SLING-1672 with the difference being that /foo/bar is a legitimate bundle resource, whereas SLING-1672 is about having BRP provide a resource in listChildren() which it will not in getResource(). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1682) add osgi and jcr install into launchpad
add osgi and jcr install into launchpad --- Key: SLING-1682 URL: https://issues.apache.org/jira/browse/SLING-1682 Project: Sling Issue Type: Improvement Components: Launchpad Reporter: Justin Edelson Fix For: Launchpad Builder 6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1681) Merge Installer into Reactor
Merge Installer into Reactor Key: SLING-1681 URL: https://issues.apache.org/jira/browse/SLING-1681 Project: Sling Issue Type: Improvement Components: General Reporter: Justin Edelson installer builds and test successfully, so we should merge it into the main reactor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1686) AuthenticationInfoPostProcessors aren't invoked for basic auth
AuthenticationInfoPostProcessors aren't invoked for basic auth -- Key: SLING-1686 URL: https://issues.apache.org/jira/browse/SLING-1686 Project: Sling Issue Type: Bug Components: Authentication Reporter: Justin Edelson If the built-in http basic authentication handler is used, the AuthenticationInfoPostProcessor list won't be invoked for the extracted credentials. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1686) AuthenticationInfoPostProcessors aren't invoked for basic auth
[ https://issues.apache.org/jira/browse/SLING-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12901591#action_12901591 ] Justin Edelson commented on SLING-1686: --- fixed in r988314. be great to see this in the Auth Core 1.0.0 release (see my vote), but I'm leaving the Fix Version blank for now. AuthenticationInfoPostProcessors aren't invoked for basic auth -- Key: SLING-1686 URL: https://issues.apache.org/jira/browse/SLING-1686 Project: Sling Issue Type: Bug Components: Authentication Reporter: Justin Edelson If the built-in http basic authentication handler is used, the AuthenticationInfoPostProcessor list won't be invoked for the extracted credentials. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1686) AuthenticationInfoPostProcessors aren't invoked for basic auth
[ https://issues.apache.org/jira/browse/SLING-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1686. --- Resolution: Fixed AuthenticationInfoPostProcessors aren't invoked for basic auth -- Key: SLING-1686 URL: https://issues.apache.org/jira/browse/SLING-1686 Project: Sling Issue Type: Bug Components: Authentication Reporter: Justin Edelson If the built-in http basic authentication handler is used, the AuthenticationInfoPostProcessor list won't be invoked for the extracted credentials. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1692) When started from Maven Launchpad Plugin, framework cannot be restarted
When started from Maven Launchpad Plugin, framework cannot be restarted --- Key: SLING-1692 URL: https://issues.apache.org/jira/browse/SLING-1692 Project: Sling Issue Type: Bug Components: Maven Plugins Reporter: Justin Edelson Fix For: Maven Launchpad Plugin 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] Updated: (SLING-1692) When started from Maven Launchpad Plugin, framework cannot be restarted
[ https://issues.apache.org/jira/browse/SLING-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1692: -- Assignee: Justin Edelson When started from Maven Launchpad Plugin, framework cannot be restarted --- Key: SLING-1692 URL: https://issues.apache.org/jira/browse/SLING-1692 Project: Sling Issue Type: Bug Components: Maven Plugins Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Maven Launchpad Plugin 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] Resolved: (SLING-1692) When started from Maven Launchpad Plugin, framework cannot be restarted
[ https://issues.apache.org/jira/browse/SLING-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1692. --- Resolution: Fixed When started from Maven Launchpad Plugin, framework cannot be restarted --- Key: SLING-1692 URL: https://issues.apache.org/jira/browse/SLING-1692 Project: Sling Issue Type: Bug Components: Maven Plugins Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Maven Launchpad Plugin 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] Commented: (SLING-1692) When started from Maven Launchpad Plugin, framework cannot be restarted
[ https://issues.apache.org/jira/browse/SLING-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12901952#action_12901952 ] Justin Edelson commented on SLING-1692: --- done in r988610 When started from Maven Launchpad Plugin, framework cannot be restarted --- Key: SLING-1692 URL: https://issues.apache.org/jira/browse/SLING-1692 Project: Sling Issue Type: Bug Components: Maven Plugins Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Maven Launchpad Plugin 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] Created: (SLING-1693) Maven Launchpad Plugin's ResourceProvider should return .xml files from the classpath
Maven Launchpad Plugin's ResourceProvider should return .xml files from the classpath - Key: SLING-1693 URL: https://issues.apache.org/jira/browse/SLING-1693 Project: Sling Issue Type: Bug Components: Maven Plugins Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Maven Launchpad Plugin 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] Resolved: (SLING-1693) Maven Launchpad Plugin's ResourceProvider should return .xml files from the classpath
[ https://issues.apache.org/jira/browse/SLING-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1693. --- Resolution: Fixed done in r988612 Maven Launchpad Plugin's ResourceProvider should return .xml files from the classpath - Key: SLING-1693 URL: https://issues.apache.org/jira/browse/SLING-1693 Project: Sling Issue Type: Improvement Components: Maven Plugins Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Maven Launchpad Plugin 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] Updated: (SLING-1693) Maven Launchpad Plugin's ResourceProvider should return .xml files from the classpath
[ https://issues.apache.org/jira/browse/SLING-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1693: -- Issue Type: Improvement (was: Bug) Maven Launchpad Plugin's ResourceProvider should return .xml files from the classpath - Key: SLING-1693 URL: https://issues.apache.org/jira/browse/SLING-1693 Project: Sling Issue Type: Improvement Components: Maven Plugins Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Maven Launchpad Plugin 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] Reopened: (SLING-1693) Maven Launchpad Plugin's ResourceProvider should return .xml files from the classpath
[ https://issues.apache.org/jira/browse/SLING-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson reopened SLING-1693: --- need to rethink this strategy entirely... Maven Launchpad Plugin's ResourceProvider should return .xml files from the classpath - Key: SLING-1693 URL: https://issues.apache.org/jira/browse/SLING-1693 Project: Sling Issue Type: Improvement Components: Maven Plugins Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Maven Launchpad Plugin 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] Updated: (SLING-1693) Maven Launchpad Plugin's ResourceProvider should use a search path
[ https://issues.apache.org/jira/browse/SLING-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1693: -- Summary: Maven Launchpad Plugin's ResourceProvider should use a search path (was: Maven Launchpad Plugin's ResourceProvider should return .xml files from the classpath) for resources, regardless of file type, should be... 1) a local directory 2) the classpath 3) treat the path as a URL Maven Launchpad Plugin's ResourceProvider should use a search path -- Key: SLING-1693 URL: https://issues.apache.org/jira/browse/SLING-1693 Project: Sling Issue Type: Improvement Components: Maven Plugins Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Maven Launchpad Plugin 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] Updated: (SLING-1664) support reading the jackrabbit configuration file from the launchpad archive
[ https://issues.apache.org/jira/browse/SLING-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1664: -- Assignee: Justin Edelson support reading the jackrabbit configuration file from the launchpad archive Key: SLING-1664 URL: https://issues.apache.org/jira/browse/SLING-1664 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Assignee: Justin Edelson downstream users of Sling should be able to put a repository.xml in either the launchpad JAR or WAR and get it to work without any additional configuration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1693) Maven Launchpad Plugin's ResourceProvider should use a search path
[ https://issues.apache.org/jira/browse/SLING-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1693. --- Resolution: Fixed reimplemented in r988642 Maven Launchpad Plugin's ResourceProvider should use a search path -- Key: SLING-1693 URL: https://issues.apache.org/jira/browse/SLING-1693 Project: Sling Issue Type: Improvement Components: Maven Plugins Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Maven Launchpad Plugin 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] Updated: (SLING-1664) support reading the jackrabbit configuration file from the launchpad archive
[ https://issues.apache.org/jira/browse/SLING-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1664: -- Fix Version/s: JCR Jackrabbit Server 2.0.8 support reading the jackrabbit configuration file from the launchpad archive Key: SLING-1664 URL: https://issues.apache.org/jira/browse/SLING-1664 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR Jackrabbit Server 2.0.8 downstream users of Sling should be able to put a repository.xml in either the launchpad JAR or WAR and get it to work without any additional configuration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1664) support reading the jackrabbit configuration file from the launchpad archive
[ https://issues.apache.org/jira/browse/SLING-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12901998#action_12901998 ] Justin Edelson commented on SLING-1664: --- done in r988640 if there's no configuration for the embedded repository and there is a repository.xml file at the root of the ResourceProvider, then that configuration file is copied into sling.home and used as the repository configuration. for JAR archives, this is the root of the archive for WAR archives, this is the root of the archive, WEB-IF, or the webapp classpath when using the Maven Launchpad Plugin, it is src/test/resources support reading the jackrabbit configuration file from the launchpad archive Key: SLING-1664 URL: https://issues.apache.org/jira/browse/SLING-1664 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR Jackrabbit Server 2.0.8 downstream users of Sling should be able to put a repository.xml in either the launchpad JAR or WAR and get it to work without any additional configuration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1681) Merge Installer into Reactor
[ https://issues.apache.org/jira/browse/SLING-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1681. --- Assignee: Justin Edelson Resolution: Fixed Merge Installer into Reactor Key: SLING-1681 URL: https://issues.apache.org/jira/browse/SLING-1681 Project: Sling Issue Type: Improvement Components: General Reporter: Justin Edelson Assignee: Justin Edelson installer builds and test successfully, so we should merge it into the main reactor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1681) Merge Installer into Reactor
[ https://issues.apache.org/jira/browse/SLING-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902000#action_12902000 ] Justin Edelson commented on SLING-1681: --- done in r988646 Merge Installer into Reactor Key: SLING-1681 URL: https://issues.apache.org/jira/browse/SLING-1681 Project: Sling Issue Type: Improvement Components: General Reporter: Justin Edelson Assignee: Justin Edelson installer builds and test successfully, so we should merge it into the main reactor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1695) form auth should be able to set the auth cookie on a specific domain
form auth should be able to set the auth cookie on a specific domain Key: SLING-1695 URL: https://issues.apache.org/jira/browse/SLING-1695 Project: Sling Issue Type: Improvement Components: Authentication Reporter: Justin Edelson -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1697) Log the start of each test class run
Log the start of each test class run Key: SLING-1697 URL: https://issues.apache.org/jira/browse/SLING-1697 Project: Sling Issue Type: Improvement Components: Testing Reporter: Justin Edelson Fix For: Launchpad Testing 6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1698) Set an explicit version for exported packages
Set an explicit version for exported packages - Key: SLING-1698 URL: https://issues.apache.org/jira/browse/SLING-1698 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Fix For: JCR Jackrabbit Access Manager 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] Updated: (SLING-1698) Set an explicit version for exported packages
[ https://issues.apache.org/jira/browse/SLING-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1698: -- Fix Version/s: JCR Jackrabbit User Manager 2.0.6 Set an explicit version for exported packages - Key: SLING-1698 URL: https://issues.apache.org/jira/browse/SLING-1698 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Fix For: JCR Jackrabbit User Manager 2.0.6, JCR Jackrabbit Access Manager 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] Resolved: (SLING-1664) support reading the jackrabbit configuration file from the launchpad archive
[ https://issues.apache.org/jira/browse/SLING-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1664. --- Resolution: Fixed support reading the jackrabbit configuration file from the launchpad archive Key: SLING-1664 URL: https://issues.apache.org/jira/browse/SLING-1664 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR Jackrabbit Server 2.0.8 downstream users of Sling should be able to put a repository.xml in either the launchpad JAR or WAR and get it to work without any additional configuration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1698) Set an explicit version for exported packages
[ https://issues.apache.org/jira/browse/SLING-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1698: -- Fix Version/s: Scripting JSP-Taglib 2.1.0 Set an explicit version for exported packages - Key: SLING-1698 URL: https://issues.apache.org/jira/browse/SLING-1698 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Fix For: Scripting JSP-Taglib 2.1.0, JCR Jackrabbit User Manager 2.0.6, JCR Jackrabbit Access Manager 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] Updated: (SLING-1421) Resorce Resolver Mapping - Better Support for Multiple Domain/Protocol Mapping
[ https://issues.apache.org/jira/browse/SLING-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1421: -- Fix Version/s: (was: JCR Resource 2.0.8) Resorce Resolver Mapping - Better Support for Multiple Domain/Protocol Mapping -- Key: SLING-1421 URL: https://issues.apache.org/jira/browse/SLING-1421 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Resource 2.0.6 Reporter: Stefan Seifert Attachments: 100303_slingtest-mapping.zip in our sling CMS-based web projects we've the following scenario: * most pages of a website are accessed via HTTP, but some of the via HTTPs (e.g. including forms submitting personal data) * at the same time we use the mapping features at /etc/map to shorten the urls for a given domain name * in fact we have to configure two mappings for two domain names (one for HTTP and one for HTTPS), pointing to the same start path in JCR with this configuration in place the sling ResourceResolver.map method sometimes produces unexpected or incorrect results with the current implementation. if the current host name and port does not match with the configured mapping host name and port sling automatically adds protocol, host name and port from the configuration to the result of the map method. but in the case above with multiple mappings for the same start path this cannot produce correct results, because the decision whether the secure or non-secure domain name should be chosen is custom application logic. i'm not sure what the best solution is for this problem, because the current implementation makes sense in some way and works well for the simple scenarios. but in complex scenarios with multiple domain mappings it would be more practical to use the map method only for shortening the urls and not for adding the hostname. of course it is possible to parse the value of the map method and strip off any hostname returned manually and add an own one, but this seems not right. and if the cms does a check if the internal url is valid this url can be treated as invalid. for easy reproduction of the scenario i've attached a simple test project [^100303_slingtest-mapping.zip]. please deploy it to a sling instance using mvn install and then call in the intro page http://localhost:8080/content/slingtest-mapping.html and follow the instructions on the page (two host names have to be added to the local hosts file). the test project contains two templates/jsp components, a configuration at /etc/map with two domain names pointing to the same path and some sample content nodes. depending whether a default mapping /content/-/ is configured in apache sling resource resolver the generated links on the site 1 test page are correct. but the links generate on the site 2 test pages are wrong. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1421) Resorce Resolver Mapping - Better Support for Multiple Domain/Protocol Mapping
[ https://issues.apache.org/jira/browse/SLING-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902642#action_12902642 ] Justin Edelson commented on SLING-1421: --- moving out of 2.0.8 Resorce Resolver Mapping - Better Support for Multiple Domain/Protocol Mapping -- Key: SLING-1421 URL: https://issues.apache.org/jira/browse/SLING-1421 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Resource 2.0.6 Reporter: Stefan Seifert Attachments: 100303_slingtest-mapping.zip in our sling CMS-based web projects we've the following scenario: * most pages of a website are accessed via HTTP, but some of the via HTTPs (e.g. including forms submitting personal data) * at the same time we use the mapping features at /etc/map to shorten the urls for a given domain name * in fact we have to configure two mappings for two domain names (one for HTTP and one for HTTPS), pointing to the same start path in JCR with this configuration in place the sling ResourceResolver.map method sometimes produces unexpected or incorrect results with the current implementation. if the current host name and port does not match with the configured mapping host name and port sling automatically adds protocol, host name and port from the configuration to the result of the map method. but in the case above with multiple mappings for the same start path this cannot produce correct results, because the decision whether the secure or non-secure domain name should be chosen is custom application logic. i'm not sure what the best solution is for this problem, because the current implementation makes sense in some way and works well for the simple scenarios. but in complex scenarios with multiple domain mappings it would be more practical to use the map method only for shortening the urls and not for adding the hostname. of course it is possible to parse the value of the map method and strip off any hostname returned manually and add an own one, but this seems not right. and if the cms does a check if the internal url is valid this url can be treated as invalid. for easy reproduction of the scenario i've attached a simple test project [^100303_slingtest-mapping.zip]. please deploy it to a sling instance using mvn install and then call in the intro page http://localhost:8080/content/slingtest-mapping.html and follow the instructions on the page (two host names have to be added to the local hosts file). the test project contains two templates/jsp components, a configuration at /etc/map with two domain names pointing to the same path and some sample content nodes. depending whether a default mapping /content/-/ is configured in apache sling resource resolver the generated links on the site 1 test page are correct. but the links generate on the site 2 test pages are wrong. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1697) Log the start of each test class run
[ https://issues.apache.org/jira/browse/SLING-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902846#action_12902846 ] Justin Edelson commented on SLING-1697: --- That wasn't the behavior I wanted, but it's also not the behavior I'm seeing... Do you see multiple Added lines for each of these? You should see the same number of Added lines as Running lines: $ grep CreateUserTest junit.log 11:04:53.978 INFO [main] TestAll.java:78 Added org.apache.sling.launchpad.webapp.integrationtest.userManager.CreateUserTest 11:05:46.415 INFO [main] LoggingSuite.java:29 Running test class org.apache.sling.launchpad.webapp.integrationtest.userManager.CreateUserTest Log the start of each test class run Key: SLING-1697 URL: https://issues.apache.org/jira/browse/SLING-1697 Project: Sling Issue Type: Improvement Components: Testing Reporter: Justin Edelson Fix For: Launchpad Testing 6 Attachments: HttpTestBase.java.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1697) Log the start of each test class run
[ https://issues.apache.org/jira/browse/SLING-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1697: -- Comment: was deleted (was: That wasn't the behavior I wanted, but it's also not the behavior I'm seeing... Do you see multiple Added lines for each of these? You should see the same number of Added lines as Running lines: $ grep CreateUserTest junit.log 11:04:53.978 INFO [main] TestAll.java:78 Added org.apache.sling.launchpad.webapp.integrationtest.userManager.CreateUserTest 11:05:46.415 INFO [main] LoggingSuite.java:29 Running test class org.apache.sling.launchpad.webapp.integrationtest.userManager.CreateUserTest ) Log the start of each test class run Key: SLING-1697 URL: https://issues.apache.org/jira/browse/SLING-1697 Project: Sling Issue Type: Improvement Components: Testing Reporter: Justin Edelson Fix For: Launchpad Testing 6 Attachments: HttpTestBase.java.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1697) Log the start of each test class run
[ https://issues.apache.org/jira/browse/SLING-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902847#action_12902847 ] Justin Edelson commented on SLING-1697: --- (sorry about that spurious comment, I thought I'd already committed a fix for this) I implemented this in r989653 via the TestAll class so that it appears along side the log messages indicating when a test class is discovered. Log the start of each test class run Key: SLING-1697 URL: https://issues.apache.org/jira/browse/SLING-1697 Project: Sling Issue Type: Improvement Components: Testing Reporter: Justin Edelson Fix For: Launchpad Testing 6 Attachments: HttpTestBase.java.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1697) Log the start of each test class run
[ https://issues.apache.org/jira/browse/SLING-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1697. --- Assignee: Justin Edelson Resolution: Fixed Log the start of each test class run Key: SLING-1697 URL: https://issues.apache.org/jira/browse/SLING-1697 Project: Sling Issue Type: Improvement Components: Testing Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Launchpad Testing 6 Attachments: HttpTestBase.java.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1695) form auth should be able to set the auth cookie on a specific domain
[ https://issues.apache.org/jira/browse/SLING-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902848#action_12902848 ] Justin Edelson commented on SLING-1695: --- for completeness I suspect my use case is very specific and is intertwined with a few other things, but basically... I make heavy use of workspaces in my CMS for content branches. Subdomains of a parent domain are used to identify which workspace should be used. Setting the auth cookie on the parent domain allows for users to view content in different branches (workspaces) without re-authenticating. Another use case (just thinking out loud here), would be to use Sling as an SSO provider, again by setting the cookie on a parent domain and then having a ServletFilter on each client application which check the cookie against the Sling instance. It's no SAML, but would work. form auth should be able to set the auth cookie on a specific domain Key: SLING-1695 URL: https://issues.apache.org/jira/browse/SLING-1695 Project: Sling Issue Type: Improvement Components: Authentication Reporter: Justin Edelson -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1695) form auth should be able to set the auth cookie on a specific domain
[ https://issues.apache.org/jira/browse/SLING-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1695. --- Assignee: Justin Edelson Resolution: Fixed done in r989652. default cookie domain can be set via config admin and overridden via AuthenticationInfo map. form auth should be able to set the auth cookie on a specific domain Key: SLING-1695 URL: https://issues.apache.org/jira/browse/SLING-1695 Project: Sling Issue Type: Improvement Components: Authentication Reporter: Justin Edelson Assignee: Justin Edelson -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1700) contrib/scripting/velocity embeds velocity, causing classloading issue at runtime
[
https://issues.apache.org/jira/browse/SLING-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12903191#action_12903191
]
Justin Edelson commented on SLING-1700:
---
Agree with Felix that Velocity and ORO should be embedded here.
It looks like the problem is that velocity packages are being imported. That
shouldn't be the case.
Note - it would be better if Velocity simply provided an OSGi bundle with
support for JSR-223. See VELOCITY-735 and VELOCITY-765. If this was done, we
wouldn't need this module at all.
contrib/scripting/velocity embeds velocity, causing classloading issue at
runtime
-
Key: SLING-1700
URL: https://issues.apache.org/jira/browse/SLING-1700
Project: Sling
Issue Type: Bug
Components: Scripting
Environment: Felix 1.4, Sling 2.0.7, Apache Velocity 1.6.2
Reporter: Olaf Otto
Original Estimate: 2h
Remaining Estimate: 2h
Affects: Rev. 989119 of
https://svn.apache.org/repos/asf/sling/trunk/contrib/scripting/velocity
(2.0.0-SNAPSHOT)
The maven-bundle-configuration in the pom of the velocity support module
(https://svn.apache.org/repos/asf/sling/trunk/contrib/scripting/velocity/pom.xml)
embeds a couple of dependencies:
...
Embed-Dependency
velocity;oro;commons-lang;inline=true
/Embed-Dependency
...
However, these libraries are available as bundles and should not be embedded.
In the case of velocity, this causes an issue when a apache velocity bundle
is also deployed in felix, as the org.apache.velocity.runtime.log.LogChute
interface is loaded from both the velocity scripting support bundle and the
deployed apache velocity bundle:
Suggested resolution: Remove the embedding. It is bad practice anyway. I've
successfully tested this with the following maven-bundle-configuration
configuration:
configuration
instructions
Private-Package
org.apache.sling.scripting.velocity
/Private-Package
Import-Package
org.apache.velocity.runtime.log,
com.werken.xpath; javax.sql;
org.apache.commons.*; org.apache.log.*;
org.apache.log4j; org.apache.tools.ant.*;
org.jdom.*;resolution:=optional, *
/Import-Package
ScriptEngine-Name${pom.name}/ScriptEngine-Name
ScriptEngine-Version${pom.version}/ScriptEngine-Version
/instructions
/configuration
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1703) Mixin types aren't modified for sub nodes
Mixin types aren't modified for sub nodes - Key: SLING-1703 URL: https://issues.apache.org/jira/browse/SLING-1703 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Justin Edelson curl -F./jcr:mixinTypes=mix:created http://localhost:/test/content/child sets the mixin type for /test/content/child if that node exists, but curl -F./child/jcr:mixinTypes=mix:created http://localhost:/test/content doesn't. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1703) Mixin types aren't modified for sub nodes
[ https://issues.apache.org/jira/browse/SLING-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1703: -- Issue Type: Bug (was: Improvement) Fix Version/s: Servlets Post 2.0.6 Mixin types aren't modified for sub nodes - Key: SLING-1703 URL: https://issues.apache.org/jira/browse/SLING-1703 Project: Sling Issue Type: Bug Components: Servlets Reporter: Justin Edelson Fix For: Servlets Post 2.0.6 curl -F./jcr:mixinTypes=mix:created http://localhost:/test/content/child sets the mixin type for /test/content/child if that node exists, but curl -F./child/jcr:mixinTypes=mix:created http://localhost:/test/content doesn't. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1704) Add support for modifying jcr:primaryType
Add support for modifying jcr:primaryType - Key: SLING-1704 URL: https://issues.apache.org/jira/browse/SLING-1704 Project: Sling Issue Type: Improvement Reporter: Justin Edelson Fix For: Servlets Post 2.1.0 JCR 2 added a setPrimaryNodeType method, which we should use -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1707) add a nodetype configuration printer
add a nodetype configuration printer Key: SLING-1707 URL: https://issues.apache.org/jira/browse/SLING-1707 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Fix For: JCR Web Console 1.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (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 ] Justin Edelson reopened SLING-1705: --- This fails for multi-valued properties, demonstrated in the ReferenceTypeHintTest case. 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] Resolved: (SLING-1703) Mixin types aren't modified for sub nodes
[ https://issues.apache.org/jira/browse/SLING-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1703. --- Assignee: Justin Edelson Resolution: Fixed Mixin types aren't modified for sub nodes - Key: SLING-1703 URL: https://issues.apache.org/jira/browse/SLING-1703 Project: Sling Issue Type: Bug Components: Servlets Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Servlets Post 2.0.6 curl -F./jcr:mixinTypes=mix:created http://localhost:/test/content/child sets the mixin type for /test/content/child if that node exists, but curl -F./child/jcr:mixinTypes=mix:created http://localhost:/test/content doesn't. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1707) add a nodetype configuration printer
[ https://issues.apache.org/jira/browse/SLING-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1707. --- Resolution: Fixed add a nodetype configuration printer Key: SLING-1707 URL: https://issues.apache.org/jira/browse/SLING-1707 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Fix For: JCR Web Console 1.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1707) add a nodetype configuration printer
[ https://issues.apache.org/jira/browse/SLING-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12904233#action_12904233 ] Justin Edelson commented on SLING-1707: --- added in r990832 add a nodetype configuration printer Key: SLING-1707 URL: https://issues.apache.org/jira/browse/SLING-1707 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Fix For: JCR Web Console 1.0.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (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 ] Justin Edelson resolved SLING-1705. --- Resolution: Fixed added multi-valued check in r990833. it might be interesting to set the length to the number of items in the multi-valued property, but I didn't do that. 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] Commented: (SLING-1703) Mixin types aren't modified for sub nodes
[ https://issues.apache.org/jira/browse/SLING-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12904232#action_12904232 ] Justin Edelson commented on SLING-1703: --- fixed in 990831 Mixin types aren't modified for sub nodes - Key: SLING-1703 URL: https://issues.apache.org/jira/browse/SLING-1703 Project: Sling Issue Type: Bug Components: Servlets Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Servlets Post 2.0.6 curl -F./jcr:mixinTypes=mix:created http://localhost:/test/content/child sets the mixin type for /test/content/child if that node exists, but curl -F./child/jcr:mixinTypes=mix:created http://localhost:/test/content doesn't. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1718) text/html property rendering of multi-valued properties doesn't work
text/html property rendering of multi-valued properties doesn't work
Key: SLING-1718
URL: https://issues.apache.org/jira/browse/SLING-1718
Project: Sling
Issue Type: Bug
Components: Servlets
Reporter: Justin Edelson
Fix For: Servlets Get 2.0.10
$ curl -u admin:admin -F a=b -F a...@typehint=string[]
http://localhost:/test/node1
$ curl http://localhost:/test/node1.html
?xml version=1.0 encoding=utf-8?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.1//EN
http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd;
html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en
headmeta http-equiv=content-type content=text/html; charset=utf-8
//head
body
h1Resource dumped by HtmlRendererServlet/h1
pResource path: b/test/node1/b/p
pResource metadata: b{sling.resolutionPathInfo=.html,
sling.resolutionPath=/test/node1}/b/p
pResource type: bnt:unstructured/b/p
pResource super type: b-/b/p
h2Resource properties/h2
p
a: b[b]/bbr /
jcr:primaryType: bnt:unstructured/bbr /
/p
/body/html
$ curl http://localhost:/test/node1/a.html
returns a 204 No Content message
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1718) text/html property rendering of multi-valued properties doesn't work
[
https://issues.apache.org/jira/browse/SLING-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson resolved SLING-1718.
---
Resolution: Fixed
text/html property rendering of multi-valued properties doesn't work
Key: SLING-1718
URL: https://issues.apache.org/jira/browse/SLING-1718
Project: Sling
Issue Type: Bug
Components: Servlets
Reporter: Justin Edelson
Fix For: Servlets Get 2.0.10
$ curl -u admin:admin -F a=b -F a...@typehint=string[]
http://localhost:/test/node1
$ curl http://localhost:/test/node1.html
?xml version=1.0 encoding=utf-8?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.1//EN
http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd;
html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en
headmeta http-equiv=content-type content=text/html; charset=utf-8
//head
body
h1Resource dumped by HtmlRendererServlet/h1
pResource path: b/test/node1/b/p
pResource metadata: b{sling.resolutionPathInfo=.html,
sling.resolutionPath=/test/node1}/b/p
pResource type: bnt:unstructured/b/p
pResource super type: b-/b/p
h2Resource properties/h2
p
a: b[b]/bbr /
jcr:primaryType: bnt:unstructured/bbr /
/p
/body/html
$ curl http://localhost:/test/node1/a.html
returns a 204 No Content message
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1408) text/plain property rendering of multi-valued properties doesn't work
[
https://issues.apache.org/jira/browse/SLING-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905046#action_12905046
]
Justin Edelson commented on SLING-1408:
---
done in r991566
text/plain property rendering of multi-valued properties doesn't work
-
Key: SLING-1408
URL: https://issues.apache.org/jira/browse/SLING-1408
Project: Sling
Issue Type: Bug
Components: Servlets
Affects Versions: Servlets Get 2.0.8
Reporter: Justin Edelson
Fix For: Servlets Get 2.0.10
$ curl -u admin:admin -F a=b -F a...@typehint=string[]
http://localhost:/test/node1
$ curl http://localhost:/test/node1.txt
** Resource dumped by PlainTextRendererServlet**
Resource path:/test/node1
Resource metadata: {sling.resolutionPathInfo=.txt,
sling.resolutionPath=/test/node1}
Resource type: nt:unstructured
Resource super type: -
** Resource properties **
a: [b]
jcr:primaryType: nt:unstructured
$ curl http://localhost:/test/node1/a.txt
(nothing output here)
should be [b] IMHO
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1408) text/plain property rendering of multi-valued properties doesn't work
[
https://issues.apache.org/jira/browse/SLING-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson resolved SLING-1408.
---
Resolution: Fixed
text/plain property rendering of multi-valued properties doesn't work
-
Key: SLING-1408
URL: https://issues.apache.org/jira/browse/SLING-1408
Project: Sling
Issue Type: Bug
Components: Servlets
Affects Versions: Servlets Get 2.0.8
Reporter: Justin Edelson
Fix For: Servlets Get 2.0.10
$ curl -u admin:admin -F a=b -F a...@typehint=string[]
http://localhost:/test/node1
$ curl http://localhost:/test/node1.txt
** Resource dumped by PlainTextRendererServlet**
Resource path:/test/node1
Resource metadata: {sling.resolutionPathInfo=.txt,
sling.resolutionPath=/test/node1}
Resource type: nt:unstructured
Resource super type: -
** Resource properties **
a: [b]
jcr:primaryType: nt:unstructured
$ curl http://localhost:/test/node1/a.txt
(nothing output here)
should be [b] IMHO
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1718) text/html property rendering of multi-valued properties doesn't work
[
https://issues.apache.org/jira/browse/SLING-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905048#action_12905048
]
Justin Edelson commented on SLING-1718:
---
done in r991565
text/html property rendering of multi-valued properties doesn't work
Key: SLING-1718
URL: https://issues.apache.org/jira/browse/SLING-1718
Project: Sling
Issue Type: Bug
Components: Servlets
Reporter: Justin Edelson
Fix For: Servlets Get 2.0.10
$ curl -u admin:admin -F a=b -F a...@typehint=string[]
http://localhost:/test/node1
$ curl http://localhost:/test/node1.html
?xml version=1.0 encoding=utf-8?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.1//EN
http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd;
html xmlns=http://www.w3.org/1999/xhtml; xml:lang=en
headmeta http-equiv=content-type content=text/html; charset=utf-8
//head
body
h1Resource dumped by HtmlRendererServlet/h1
pResource path: b/test/node1/b/p
pResource metadata: b{sling.resolutionPathInfo=.html,
sling.resolutionPath=/test/node1}/b/p
pResource type: bnt:unstructured/b/p
pResource super type: b-/b/p
h2Resource properties/h2
p
a: b[b]/bbr /
jcr:primaryType: bnt:unstructured/bbr /
/p
/body/html
$ curl http://localhost:/test/node1/a.html
returns a 204 No Content message
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1446) Scripts should be resolved against the current workspace
[ https://issues.apache.org/jira/browse/SLING-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1446. --- Assignee: Carsten Ziegeler (was: Justin Edelson) Resolution: Fixed this has been resolved for a while now. Scripts should be resolved against the current workspace Key: SLING-1446 URL: https://issues.apache.org/jira/browse/SLING-1446 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Justin Edelson Assignee: Carsten Ziegeler Fix For: Servlets Resolver 2.0.10 currently, if a non-default workspace is specified in AuthenticationInfo, scripts are still resolved against the default workspace. Scripts should be resolved first against the workspace used in the Request (i.e. from AuthenticationInfo) and then a default workspace as a backup. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1393) Add Jackrabbit's DavEX servlet
[ https://issues.apache.org/jira/browse/SLING-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1393. --- Resolution: Fixed Add Jackrabbit's DavEX servlet -- Key: SLING-1393 URL: https://issues.apache.org/jira/browse/SLING-1393 Project: Sling Issue Type: Task Components: JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR DavEx 1.0.0 Jackrabbit now provides an alternate WebDav servlet which includes support for some JCR-specific extensions. This should be available at /davex. This task should also include the creation of one or more integration tests which show JCR2SPI being used on top of Sling. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1698) Set an explicit version for exported packages
[ https://issues.apache.org/jira/browse/SLING-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1698. --- Resolution: Fixed Set an explicit version for exported packages - Key: SLING-1698 URL: https://issues.apache.org/jira/browse/SLING-1698 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Fix For: Scripting JSP-Taglib 2.1.0, JCR Jackrabbit User Manager 2.0.6, JCR Jackrabbit Access Manager 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] Commented: (SLING-1698) Set an explicit version for exported packages
[ https://issues.apache.org/jira/browse/SLING-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905050#action_12905050 ] Justin Edelson commented on SLING-1698: --- fixed in r991571 Set an explicit version for exported packages - Key: SLING-1698 URL: https://issues.apache.org/jira/browse/SLING-1698 Project: Sling Issue Type: Improvement Components: JCR Reporter: Justin Edelson Fix For: Scripting JSP-Taglib 2.1.0, JCR Jackrabbit User Manager 2.0.6, JCR Jackrabbit Access Manager 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] Commented: (SLING-1393) Add Jackrabbit's DavEX servlet
[ https://issues.apache.org/jira/browse/SLING-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905051#action_12905051 ] Justin Edelson commented on SLING-1393: --- resolved for a while. mount path is actually /server to keep inline with Jackrabbit default Add Jackrabbit's DavEX servlet -- Key: SLING-1393 URL: https://issues.apache.org/jira/browse/SLING-1393 Project: Sling Issue Type: Task Components: JCR Reporter: Justin Edelson Assignee: Justin Edelson Fix For: JCR DavEx 1.0.0 Jackrabbit now provides an alternate WebDav servlet which includes support for some JCR-specific extensions. This should be available at /davex. This task should also include the creation of one or more integration tests which show JCR2SPI being used on top of Sling. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1391) Make JcrModifiablePropertyMap write changes directly
[
https://issues.apache.org/jira/browse/SLING-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-1391:
--
Fix Version/s: (was: JCR Resource 2.0.8)
descheduling from current release
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] Updated: (SLING-1463) Rewrite MapEntries to be a OSGi EventHandler instead of a JCR EventListener
[ https://issues.apache.org/jira/browse/SLING-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1463: -- Fix Version/s: (was: JCR Resource 2.0.8) descheduling from current release Rewrite MapEntries to be a OSGi EventHandler instead of a JCR EventListener --- Key: SLING-1463 URL: https://issues.apache.org/jira/browse/SLING-1463 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Resource 2.0.6 Reporter: Vidar S. Ramdal Assignee: Carsten Ziegeler Attachments: SLING1463.patch Original Estimate: 3h Remaining Estimate: 3h o.a.s.jcr.resource.internal.helper.MapEntries is responsible for holding a map of domain mappings. The map is created by scanning resources found under /etc/map. Currently, the scanning is triggered when a JCR node under /etc/map is modified, as MapEntries implements javax.jcr.observation.EventListener. To support resources other than JCR nodes for domain map specifications, MapEntries should instead listen for OSGi resource events sent through EventAdmin - thus implement org.osgi.service.event.Event instead of javax.jcr.observation.EventListener. As MapEntries already uses the Resource API (not the JCR API) to examine the /etc/map tree, this task should not be too hard. Mailinglist discussion: http://markmail.org/message/tuckengyhs3lyhlf -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1455) Impossible to refer to same-name-siblings when doing internal redirect to another protocol
[
https://issues.apache.org/jira/browse/SLING-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-1455:
--
Fix Version/s: (was: JCR Resource 2.0.8)
descheduling from current release
Impossible to refer to same-name-siblings when doing internal redirect to
another protocol
--
Key: SLING-1455
URL: https://issues.apache.org/jira/browse/SLING-1455
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: JCR Resource 2.0.6
Reporter: Vidar S. Ramdal
Attachments: content.xml, etc.xml
Consider the following repository contents:
/etc/map/general-redirect
- sling:internalRedirect = protocol://$1
- sling:match = http/(.*)\.\d+
/etc/map/protocol
- sling:internalRedirect = /content
/content/localhost.80
/content/localhost.80/child
/content/localhost.80/child[2]
The domain mappings (under /etc/map) are then set up so that:
1) A request to http://localhost:8080 should internally redirect to
protocol://localhost.80. This, again, causes the request to resolve to
/content/localhost.80, which is what is intended.
2) Thus, a request to http://localhost:8080/child.html should resolve to
/content/localhost.80/child.
Both 1) and 2) works as intended. However, when including indexes for
same-name siblings, the resolution fails:
http://localhost:8080/child[2].html
.. causes a NPE: *ERROR* [0:0:0:0:0:0:0:1%0 [1269213415402] GET
/child%5B2%5D.html 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:90)
at
org.apache.sling.servlets.resolver.internal.SlingServletResolver.getErrorResource(SlingServletResolver.java:368)
at
org.apache.sling.servlets.resolver.internal.SlingServletResolver.handleError(SlingServletResolver.java:259)
This is because resolution in JcrResourceResolver has failed when trying to
construct a URL for the string protocol://localhost/child[2].html:
try {
URI uri = new URI(mappedPath[0]);
... throws a URISyntaxException because the string argument contains
unescaped brackets (for [2]).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1198) Allow mapping nodes to internet domains with template parameters
[ https://issues.apache.org/jira/browse/SLING-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1198: -- Fix Version/s: (was: JCR Resource 2.0.8) descheduling from current release Allow mapping nodes to internet domains with template parameters Key: SLING-1198 URL: https://issues.apache.org/jira/browse/SLING-1198 Project: Sling Issue Type: New Feature Components: JCR Affects Versions: JCR Resource 2.0.2 Reporter: Róbert Csákány Assignee: Felix Meschberger Attachments: MapEntry.pacth, MapEntry.patch Sling should support hosting multiple domains, with different JCR roots. E.g.: http://www.domain1.com could map to /content/domain1.com http://www.domain2.com could map to /content/domain2.com While developing a website, the fully qualified domain might not be available. Ideally, the mapping could be configured in a flexible way. One option would be to maintain a set of regular expressions to match against URLs. Each regexp would then match to a path in the JCR. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1533) Support JCR2 query languages
[ https://issues.apache.org/jira/browse/SLING-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1533: -- Fix Version/s: Servlets Get 2.1.0 (was: Servlets Get 2.0.10) moving out of current release. Support JCR2 query languages Key: SLING-1533 URL: https://issues.apache.org/jira/browse/SLING-1533 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Justin Edelson Fix For: Servlets Get 2.1.0 currently, the only possible query languages to use with the JsonQueryServlet are sql and xpath. jcr-sql2 should be allowed as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1719) add a method to determine if a resource represents a multi-valued property
add a method to determine if a resource represents a multi-valued property -- Key: SLING-1719 URL: https://issues.apache.org/jira/browse/SLING-1719 Project: Sling Issue Type: Improvement Components: JCR, API Reporter: Justin Edelson Priority: Minor see http://markmail.org/message/k3kz2737ykt52zpy for discussion -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1548) Move bundle event handling to Loader (from AbstractSlingRepository)
[ https://issues.apache.org/jira/browse/SLING-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1548. --- Resolution: Fixed applied a modified version of Felix's patch in r991929 Move bundle event handling to Loader (from AbstractSlingRepository) --- Key: SLING-1548 URL: https://issues.apache.org/jira/browse/SLING-1548 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Base 2.0.6 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Base 2.1.0 Attachments: SLING-1548.patch I am looking at a strange situation starting Sling Trunk build. Not all namespace prefixes seem to be registered in the Loader class of the JCR Base bundle. IMHO the setup in the JCR Base Bundle between the AbstractSlingRepository and the Loader is not optimal: * AbstractSlingRepository implements SynchronousBundleListener to just forward the events to the Loader * There is a time gap between the time the Loader class is instantiated (and handling a set of bundles) and the time AbstractSlingRepository is registered as a bundle listener * There is a bug in the Loader constructor preventing all just INSTALLED bundles from being registered by the BundleListener only handles the INSTALLED (and UNINSTALLED and UPDATED) events. The last part will certainly miss some bundles. I suggest we change this setup such, that the Loader itself is the bundle listener handles the events itself. The AbstractSlingRepository just sets up the loader and uses it. As a result handling events is completely where it should be (in the Loader) and the AbstractSlingRepository does not leak implementation detail (being a bundle listener) to downstream extensions of the class. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1069) Servlets registered with for resourceTypes = sling/servlet/default responds to all extensions
[ https://issues.apache.org/jira/browse/SLING-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1069: -- Fix Version/s: Servlets Resolver 2.1.0 (was: Servlets Resolver 2.0.10) Servlets registered with for resourceTypes = sling/servlet/default responds to all extensions - Key: SLING-1069 URL: https://issues.apache.org/jira/browse/SLING-1069 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Resolver 2.0.4 Reporter: Vidar S. Ramdal Fix For: Servlets Resolver 2.1.0 Attachments: RogueServlet.java, SLING-1069-test.patch, SLING-1069.patch A servlet registered with @scr.property name=sling.servlet.extensions value=html @scr.property name=sling.servlet.resourceTypes value=sling/servlet/default in the Javadoc, responds to all requests, in effect ignoring the sling.servlet.extensions property. To reproduce: 1. Install servlet from attachment (coming up) 2. Let the browser fetch /somenode.json Expected result: The server returns the JSON rendering of /somenode Actual result: The server returns Rogue Servlet -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-892) Allow servlets to be registered with extensions for all request methods
[ https://issues.apache.org/jira/browse/SLING-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-892: - Fix Version/s: Servlets Resolver 2.1.0 (was: Servlets Resolver 2.0.10) Allow servlets to be registered with extensions for all request methods --- Key: SLING-892 URL: https://issues.apache.org/jira/browse/SLING-892 Project: Sling Issue Type: Improvement Components: Servlets Affects Versions: Servlets Resolver 2.0.8 Reporter: Alexander Klimetschek Fix For: Servlets Resolver 2.1.0 As SLING-754 introduced/fixed registering servlets for non-GET methods with selectors (eg. /apps/myapp/selector.POST.servlet), the same should be possible for extensions: /apps/myapp/extension.POST.servlet Use case: symmetric URLs when you import and export stuff at a given resource path: Export = GET @ /some/path/foo.ext Import/Update = POST @ /some/path/foo.ext Currently you are forced to either use a selector for the POST case (/some/path/foo.ext.ext) or to have a sling resource type set on the /some/path/foo, but then you could only have a single POST servlet for that resource type, regardless of the extension (which is unpractical if you for example have a resource type like calendar, but want to import various calendar formats, separated by their file extension). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
