[jira] Assigned: (SLING-1782) Build error: tests take a loooooooooong time
[ https://issues.apache.org/jira/browse/SLING-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-1782: Assignee: Felix Meschberger Build error: tests take a loong time Key: SLING-1782 URL: https://issues.apache.org/jira/browse/SLING-1782 Project: Sling Issue Type: Bug Reporter: Andreas Kuckartz Assignee: Felix Meschberger Building revision 997835 takes a loong time. I stopped that after the integration tests had run longer than half an hour and there werde some problems as one can see in the log. I did not find any more information in sling/launchpad/testing/target/surefire-reports, but there were a small number of warnings [main] HttpMethodBase.java:682 Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. --- Running org.apache.sling.launchpad.testing.TestAll Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING457Test Checking if the required Sling services are started (timeout 62 seconds)... (base URLs=http://localhost:43374 and http://localhost:43374) Sling services seem to be started, continuing with integration tests. JSP script engine configured using serverscripts/jsp-engine-setup.jsp Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.GetStarTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.JspForwardTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PathsServletTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingDefaultValuesTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.MkdirTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PutMethodServletTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtCopyTest Tests run: 8, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.FiltersTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.JavascriptWrappersTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.GetWithSuffixTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.WarSelectorServletTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletUpdateTest Tests run: 7, Failures: 0, Errors: 1, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.RedirectTest Tests run: 4, Failures: 1, Errors: 3, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.GeneratedNodeNameTest Tests run: 6, Failures: 0, Errors: 6, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.StaticContentTest Tests run: 2, Failures: 2, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.InitialContentTest Tests run: 5, Failures: 5, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOrderTest Tests run: 9, Failures: 0, Errors: 9, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.ScriptBuiltinObjectsTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.accessManager.PrivilegesInfoTest Tests run: 5, Failures: 0, Errors: 5, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.PostRedirectTest Tests run: 6, Failures: 0, Errors: 6, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.NamespaceMappingTest Tests run: 4, Failures: 4, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletCreateTest Tests run: 12, Failures: 2, Errors: 10, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOutputContentTypeTest Tests run: 6, Failures: 5, Errors: 1, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.SyntheticResourceTest Tests run: 1, Failures: 1, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.userManager.UpdateGroupTest Tests run: 3, Failures: 3, Errors: 0, Skipped: 0 Running
[jira] Resolved: (SLING-1782) Build error: tests take a loooooooooong time
[ https://issues.apache.org/jira/browse/SLING-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-1782. -- Resolution: Fixed Ammended the MAVEN_OPTS recommendation output generated during the build in the parent POM in Rev. 997987. (This will show up, once we release the parent POM and refer to it from the projects). Also updated the recommendations on the Getting and Building Page. Build error: tests take a loong time Key: SLING-1782 URL: https://issues.apache.org/jira/browse/SLING-1782 Project: Sling Issue Type: Bug Reporter: Andreas Kuckartz Assignee: Felix Meschberger Building revision 997835 takes a loong time. I stopped that after the integration tests had run longer than half an hour and there werde some problems as one can see in the log. I did not find any more information in sling/launchpad/testing/target/surefire-reports, but there were a small number of warnings [main] HttpMethodBase.java:682 Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. --- Running org.apache.sling.launchpad.testing.TestAll Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING457Test Checking if the required Sling services are started (timeout 62 seconds)... (base URLs=http://localhost:43374 and http://localhost:43374) Sling services seem to be started, continuing with integration tests. JSP script engine configured using serverscripts/jsp-engine-setup.jsp Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.GetStarTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.JspForwardTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PathsServletTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingDefaultValuesTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.MkdirTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PutMethodServletTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtCopyTest Tests run: 8, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.FiltersTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.JavascriptWrappersTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.GetWithSuffixTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.WarSelectorServletTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletUpdateTest Tests run: 7, Failures: 0, Errors: 1, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.RedirectTest Tests run: 4, Failures: 1, Errors: 3, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.GeneratedNodeNameTest Tests run: 6, Failures: 0, Errors: 6, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.StaticContentTest Tests run: 2, Failures: 2, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.InitialContentTest Tests run: 5, Failures: 5, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOrderTest Tests run: 9, Failures: 0, Errors: 9, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.ScriptBuiltinObjectsTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.accessManager.PrivilegesInfoTest Tests run: 5, Failures: 0, Errors: 5, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.PostRedirectTest Tests run: 6, Failures: 0, Errors: 6, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.NamespaceMappingTest Tests run: 4, Failures: 4, Errors: 0, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletCreateTest Tests run: 12, Failures: 2, Errors: 10, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOutputContentTypeTest Tests run: 6, Failures: 5, Errors: 1, Skipped: 0 Running org.apache.sling.launchpad.webapp.integrationtest.SyntheticResourceTest
Welcome Clemens Wyss
Hi all, I want to let you know that the Apache Sling PMC decided to invite Clemens Wyss as a committer to the Apache Sling project based on his work on the JCR Explorer; an invitation which Clemens accepted. Thanks. Please join me in welcoming Clemens Wyss as a new committer ! Keep up the good work, Clemens, and thanks for your contributions. And feel free to briefly introduce yourself if you want ;-) Regards Felix
[REPORT] Sling Board report - September 2010
Sling is an OSGI-based scriptable web framework that uses a Java Content Repository, such as Apache Jackrabbit, to store and manage content. Sling graduated as a TLP on June 17th, 2009. There are no issues which require board attention at the moment. Community * This period showed strong activity towards the release of the Sling 6 distributable. This shows in a number of bugs being fixed and new functionality being added. * Added Justin Edelson to the PMC (2010/08/26) * Federico Paparoni successfully completed his GSoC project, creating a mini-CMS that will be useful as a substantial example application. * Added Clemens Wyss as a committer (2010/09/17) Releases * 2010/08/03 Adapter Manager 2.0.6, Engine 2.1.0, Settings 1.0.0 * 2010/08/21 Sling API 2.1.0 * 2010/08/25 Web Console Branding 1.0.0, Web Console Security Provider 1.0.0 * 2010/08/27 Authentication Core 1.0.0, Authentication Form 1.0.0, Authentication OpenID 1.0.0, Authentication Selector 1.0.0 * 2010/08/27 Authentication Core 1.0.2 * 2010/08/30 Commons ClassLoader 1.2.0, JCR ClassLoader 3.1.2 * 2010/09/06 Eventing 2.4.0, Commons Threads 3.0.2 * 2010/09/10 JCR API, JCR Base, JCR Content Loader, and Jackrabbit Server 2.1.0 Documentation * Added two non-committer documentation contributors (Jean-Christophe Kautzmann and Alison Heimoz) * Website documentation is steadily improving including the creation of targeted templates like http://sling.apache.org/site/how-to-manage-events-in-sling.html Licensing and other issues * none Regard Felix
Re: Welcome Clemens Wyss
On Fri, Sep 17, 2010 at 8:34 AM, Felix Meschberger fmesc...@gmail.com wrote: ...Please join me in welcoming Clemens Wyss as a new committer !... Welcome Clemens, and thanks for the good work! -Bertrand
RE: Welcome Clemens Wyss
A few words about myself (feel free to skip ;-) ): I (aged 42, married and father of 3 children) live in Switzerland where I studied information technologies at the ETH Zurich quite a long time ago. I then worked for approx 4 years with Smalltalk (still lovin' it), switched over to C#/.NET (dito), Python (where I (not only) played around with bobo(*)) and Ruby/Rails (dito), before entering the Java world at the beginning of this year. That said, since the beginning of this year I work for MySign (http://www.mysign.ch) Looking forward to further contribute to Sling... (*)bobo, very RESTy, but that was 1998! :-) -Original Message- From: Felix Meschberger [mailto:fmesc...@gmail.com] Sent: Friday, September 17, 2010 8:35 AM To: Sling Developers Subject: Welcome Clemens Wyss Hi all, I want to let you know that the Apache Sling PMC decided to invite Clemens Wyss as a committer to the Apache Sling project based on his work on the JCR Explorer; an invitation which Clemens accepted. Thanks. Please join me in welcoming Clemens Wyss as a new committer ! Keep up the good work, Clemens, and thanks for your contributions. And feel free to briefly introduce yourself if you want ;-) Regards Felix
Re: Welcome Clemens Wyss
On Fri, Sep 17, 2010 at 9:06 AM, Clemens Wyss clemens...@mysign.ch wrote: A few words about myself (feel free to skip ;-) ): I (aged 42, married and father of 3 children) live in Switzerland where I studied information technologies at the ETH Zurich quite a long time ago. I then worked for approx 4 years with Smalltalk (still lovin' it), switched over to C#/.NET (dito), Python (where I (not only) played around with bobo(*)) and Ruby/Rails (dito), before entering the Java world at the beginning of this year. That said, since the beginning of this year I work for MySign (http://www.mysign.ch) Looking forward to further contribute to Sling... (*)bobo, very RESTy, but that was 1998! :-) Welcome, Clemens! So when will we see Smalltalk scripting support in Sling? :) -- Vidar S. Ramdal vi...@idium.no - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 / +47 22 00 84 76 Quando omni flunkus moritatus!
Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0
On Thu, Sep 16, 2010 at 6:23 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Thu, Sep 16, 2010 at 5:27 PM, Vidar Ramdal vi...@idium.no wrote: ... CHECK SIGNATURES AND DIGESTS sling-staging/039/.index/nexus-maven-repository-index.gz gpg: md5: BAD sha1: BAD Should be SLING-1780, can you svn up and try again? Thanks, that did it, so I'm happy to give my +1 -- Vidar S. Ramdal vi...@idium.no - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 / +47 22 00 84 76 Quando omni flunkus moritatus!
Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0
Felix Meschberger wrote +1 What sounds a bit odd, though, is the bundle symbolic names: org.apache.sling.jcr.jcrinstall org.apache.sling.osgi.installer org.apache.sling.install.fileinstall Sounds like they have something in common, but not really much ... Wouldn't it make sense to have some concise naming convention for this ? For example org.apache.sling.install.core (today: ...osgi.installer) org.apache.sling.install.provider.jcr (today: ...jcr.jcrinstall) org.apache.sling.install.provider.file (today: ...install.fileinstall) Hmm, yes I agree the symbolic names are a little mess :) Ok, the first question is: should we stop the vote? Once this is published it gets harder to change it. So, given that we have no release for several years of this stuff, it doesn't matter if it takes one or two weeks longer. I would suggest that we continue the vote for the testing bundle but stop for the installer stuff (not sure if it is possible to just promote a part of the staging repo) I would also like that the package names have something do to with the symbolic name. WDYT? Carsten -- Carsten Ziegeler cziege...@apache.org
Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0
On Fri, Sep 17, 2010 at 10:03 AM, Carsten Ziegeler cziege...@apache.org wrote: ...I would also like that the package names have something do to with the symbolic name Works for me - when I chose the original names I wanted to make it clear that the OSGi installer is not sling-specific, as opposed to the jcrinstall module. I agree with fixing the symbolic names before releasing, the names suggested by Felix look good to me. -Bertrand
RE: Welcome Clemens Wyss
So when will we see Smalltalk scripting support in Sling? :) Smalltalk (at its best) is a system not a language :-) But hey, we have jRuby (and Groovy) which adopts some of the beautiful Smalltalk-concepts -Original Message- From: Vidar Ramdal [mailto:vi...@idium.no] Sent: Friday, September 17, 2010 9:48 AM To: dev@sling.apache.org Subject: Re: Welcome Clemens Wyss On Fri, Sep 17, 2010 at 9:06 AM, Clemens Wyss clemens...@mysign.ch wrote: A few words about myself (feel free to skip ;-) ): I (aged 42, married and father of 3 children) live in Switzerland where I studied information technologies at the ETH Zurich quite a long time ago. I then worked for approx 4 years with Smalltalk (still lovin' it), switched over to C#/.NET (dito), Python (where I (not only) played around with bobo(*)) and Ruby/Rails (dito), before entering the Java world at the beginning of this year. That said, since the beginning of this year I work for MySign (http://www.mysign.ch) Looking forward to further contribute to Sling... (*)bobo, very RESTy, but that was 1998! :-) Welcome, Clemens! So when will we see Smalltalk scripting support in Sling? :) -- Vidar S. Ramdal vi...@idium.no - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 / +47 22 00 84 76 Quando omni flunkus moritatus!
Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0
Hi, Agreed with cancelling the vote with respect to the installer parts and continuing for the testing parts. As for repository.a.o: I think you have to drop the entire staging and then upload again. But since the vote has already passed (and trusting you to do the right thing) I would then assume the staging repository may immediately be released, maybe with a comment indicating the successful vote for this (such that we have it in the commit list archive). Regards Felix Am 17.09.2010 10:03, schrieb Carsten Ziegeler: Felix Meschberger wrote +1 What sounds a bit odd, though, is the bundle symbolic names: org.apache.sling.jcr.jcrinstall org.apache.sling.osgi.installer org.apache.sling.install.fileinstall Sounds like they have something in common, but not really much ... Wouldn't it make sense to have some concise naming convention for this ? For example org.apache.sling.install.core (today: ...osgi.installer) org.apache.sling.install.provider.jcr (today: ...jcr.jcrinstall) org.apache.sling.install.provider.file (today: ...install.fileinstall) Hmm, yes I agree the symbolic names are a little mess :) Ok, the first question is: should we stop the vote? Once this is published it gets harder to change it. So, given that we have no release for several years of this stuff, it doesn't matter if it takes one or two weeks longer. I would suggest that we continue the vote for the testing bundle but stop for the installer stuff (not sure if it is possible to just promote a part of the staging repo) I would also like that the package names have something do to with the symbolic name. WDYT? Carsten
Hudson build is still unstable: sling-trunk-1.5 » Apache Sling OSGi Installer Integration Tests #890
See https://hudson.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.osgi.installer.it/changes
Re: [VOTE] Release Commons Testing 2.0.6, OSGi Installer 3.0.0, JCR Installer 3.0.0, and File Installer 1.0.0
Hi, I cancel hereby the vote for the OSGi Installer, JCR Installer, and File Installer - I already removed the artifacts from the staging repository (thanks to Nexus this is possible). We continue with the vote for Commons Testing of course. Thanks for your support! Carsten -- Carsten Ziegeler cziege...@apache.org
Hudson build is still unstable: sling-trunk-1.6 #579
See https://hudson.apache.org/hudson/job/sling-trunk-1.6/changes
Hudson build is still unstable: sling-trunk-1.6 » Apache Sling OSGi Installer Integration Tests #579
See https://hudson.apache.org/hudson/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.osgi.installer.it/579/
[jira] Created: (SLING-1783) Officialize j_reason request attribute
Officialize j_reason request attribute -- Key: SLING-1783 URL: https://issues.apache.org/jira/browse/SLING-1783 Project: Sling Issue Type: Improvement Components: Authentication Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: OpenID Authentication 1.0.2, Form Based Authentication 1.0.2, Auth Core 1.0.4 The OpenID and Form Based Authentication handler currently set the j_reason request attribute to convey to the login form why authentication has failed. It would make sense to officialize this back channel by defining this attribute can be returned by the AuthenticationHandler if credential extraction fails or by the AuthenticationFeedbackHandler if it can provide more information on the failed authentication. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1196) Sling Authentication - SlingAuthenticator hides LoginFailure reason
[
https://issues.apache.org/jira/browse/SLING-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-1196.
--
Assignee: Felix Meschberger
Resolution: Won't Fix
So we resolve this issue as won't fix in light of the solution implemented with
SLING-1783
Sling Authentication - SlingAuthenticator hides LoginFailure reason
---
Key: SLING-1196
URL: https://issues.apache.org/jira/browse/SLING-1196
Project: Sling
Issue Type: Improvement
Components: Authentication
Reporter: Hakim Sadikali
Assignee: Felix Meschberger
Attachments: SlingAuthenticator.java
Original Estimate: 2h
Remaining Estimate: 2h
The SlingAuthenticator does not provide the handler with the reason a login
failed, it only logs the reason and proceeds to try again:
// request authentication information and send 403 (Forbidden)
// if no handler can request authentication information.
log.info(authenticate: Unable to authenticate: {},
reason.getMessage());
log.debug(authenticate, reason);
login(request, response);
Applications often want to provide more detailed information to the end user,
username not found, password does not match username etc.
An easy solution would be to put the LoginException in the request for the
login handler to have access to it, and then remove it after the login
handler has processed the request - works but not particularly elegant.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1778) Symlinks
[ https://issues.apache.org/jira/browse/SLING-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12910564#action_12910564 ] Julian Sedding commented on SLING-1778: --- @Justin Any reason you couldn't have this be a multivalued property? I cannot imagine how that would work. Could you elaborate? Ok, thank you very much for the plentiful feedback! I'll take this through another iteration to incorporate your feedback. I'll drop the symlink idea in favor of the overlay mechanism. This should simplify the code a little and does make sense for me, since I don't have the symlink use-case at the moment. Unfortunately I don't have much time on my hands to work on this during my day job, so it may take a little while. Symlinks Key: SLING-1778 URL: https://issues.apache.org/jira/browse/SLING-1778 Project: Sling Issue Type: New Feature Components: JCR Reporter: Julian Sedding Attachments: symlinks.patch I have implemented a ResourceProvider, which allows to create symlink nodes in the JCR repository. A symlink node has a sling:symlinkTarget property, which should contain a valid JCR path. JCR content from the sling:symlinkTarget path is then exposed below the symlink node. There is a mixin node type, sling:Symlink with a mandatory property sling:symlinkTarget and an optional property sling:overlayable. Additionally, there is a convenience node type, sling:SymlinkResource, which extends from sling:symlinkTarget and nt:unstructured. ResourceProvider instances are registered for existing symlinks when the bundle is started. Modifications are taken care of via JCR observation. To get started: * apply the attached patch to a trunk checkout * build and install the bundle * create a symlink node, pointing to some existing content * access the symlink node e.g. via a browser -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Authentication Issue
Hi all, I am trying to tackle issues SLING-1400 [1] and SLING-1745 [2]. The first issue is about WebDAV clients connecting to Sling on root with an OPTIONS request and not being happy with a redirect response, obviously. The second issue is about client side JavaScript application framework which may send XHR requests to Sling, mainly POSTs destined for the POST Servlet but probably also other stuff. Such framework are also generally not very happy getting redirect responses back. Solutions for both problems would probably have to be implemented in the SlingAuthenticator.doLogin method, which is called after an unsuccessful login or after a first request noticing that authentication is required. So here are the options I came up with: * Send back a 401 response, at least for the OPTIONS request to trigger a regular HTTP Basic Authentication * Send back a 403 response, to indicate that access is currently forbidden (we discussed this option earlier [3]). My questions: - Would it be ok to special case the OPTIONS request ? - Shall we generally only send back a generic credentials request (may be a redirect or a form directly or whatever) if the original request was GET and send back either 401 or 403 for all non-GET requests, including HEAD ? - Is it a good idea to send back 401 generally ? - Should we only send back 401 if HTTP Basic authentication is at enabled fully or enabled preemptively and send back 403 if HTTP Basic authentication is switched off completely ? - Am I completely off track ? WDYT ? Regards Felix [1] https://issues.apache.org/jira/browse/SLING-1400 [2] https://issues.apache.org/jira/browse/SLING-1745 [3] http://markmail.org/message/jwsvk6swnxvvfsyz
Hudson build is still unstable: sling-trunk-1.5 #891
See https://hudson.apache.org/hudson/job/sling-trunk-1.5/changes
Hudson build is still unstable: sling-trunk-1.5 » Apache Sling OSGi Installer Integration Tests #891
See https://hudson.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.osgi.installer.it/891/
Re: Welcome Clemens Wyss
Welcome aboard Clemens. If I haven't said so already, the Explorer looks great and I'm sure is only going to get better. On 9/17/10 2:34 AM, Felix Meschberger wrote: Hi all, I want to let you know that the Apache Sling PMC decided to invite Clemens Wyss as a committer to the Apache Sling project based on his work on the JCR Explorer; an invitation which Clemens accepted. Thanks. Please join me in welcoming Clemens Wyss as a new committer ! Keep up the good work, Clemens, and thanks for your contributions. And feel free to briefly introduce yourself if you want ;-) Regards Felix
[jira] Commented: (SLING-1778) Symlinks
[
https://issues.apache.org/jira/browse/SLING-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12910621#action_12910621
]
Justin Edelson commented on SLING-1778:
---
What I'm thinking is let's say...
Node /b/bar has property text1=one
Node /b/baz has property text2=three
Node /a/foo has property text=two
Node /a/foo also has
sling:overlayPath = [/b/bar, /b/baz]
/a/foo.json will return
{
'text' : 'two',
'text1' : 'one',
'text2' : 'three',
'sling:overlayPath' : ['/b/bar', '/b/baz']
}
Symlinks
Key: SLING-1778
URL: https://issues.apache.org/jira/browse/SLING-1778
Project: Sling
Issue Type: New Feature
Components: JCR
Reporter: Julian Sedding
Attachments: symlinks.patch
I have implemented a ResourceProvider, which allows to create symlink nodes
in the JCR repository. A symlink node has a sling:symlinkTarget property,
which should contain a valid JCR path. JCR content from the
sling:symlinkTarget path is then exposed below the symlink node.
There is a mixin node type, sling:Symlink with a mandatory property
sling:symlinkTarget and an optional property sling:overlayable. Additionally,
there is a convenience node type, sling:SymlinkResource, which extends from
sling:symlinkTarget and nt:unstructured.
ResourceProvider instances are registered for existing symlinks when the
bundle is started. Modifications are taken care of via JCR observation.
To get started:
* apply the attached patch to a trunk checkout
* build and install the bundle
* create a symlink node, pointing to some existing content
* access the symlink node e.g. via a browser
--
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-1778) Symlinks
[
https://issues.apache.org/jira/browse/SLING-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12910621#action_12910621
]
Justin Edelson edited comment on SLING-1778 at 9/17/10 11:15 AM:
-
What I'm thinking is let's say...
Node /b/bar has property text1=one
Node /b/baz has property text2=three
Node /a/foo has property text=two
Node /a/foo also has
sling:overlayPath = [/b/bar, /b/baz]
/a/foo.json will return
{
'text' : 'two',
'sling:overlayPath' : ['/b/bar', '/b/baz'],
'text1' : 'one',
'text2' : 'three'
}
was (Author: justinedelson):
What I'm thinking is let's say...
Node /b/bar has property text1=one
Node /b/baz has property text2=three
Node /a/foo has property text=two
Node /a/foo also has
sling:overlayPath = [/b/bar, /b/baz]
/a/foo.json will return
{
'text' : 'two',
'text1' : 'one',
'text2' : 'three',
'sling:overlayPath' : ['/b/bar', '/b/baz']
}
Symlinks
Key: SLING-1778
URL: https://issues.apache.org/jira/browse/SLING-1778
Project: Sling
Issue Type: New Feature
Components: JCR
Reporter: Julian Sedding
Attachments: symlinks.patch
I have implemented a ResourceProvider, which allows to create symlink nodes
in the JCR repository. A symlink node has a sling:symlinkTarget property,
which should contain a valid JCR path. JCR content from the
sling:symlinkTarget path is then exposed below the symlink node.
There is a mixin node type, sling:Symlink with a mandatory property
sling:symlinkTarget and an optional property sling:overlayable. Additionally,
there is a convenience node type, sling:SymlinkResource, which extends from
sling:symlinkTarget and nt:unstructured.
ResourceProvider instances are registered for existing symlinks when the
bundle is started. Modifications are taken care of via JCR observation.
To get started:
* apply the attached patch to a trunk checkout
* build and install the bundle
* create a symlink node, pointing to some existing content
* access the symlink node e.g. via a browser
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Authentication Issue
At least in the WebDAV case, is there any way to use the Accepts header to help with making the decision as to how to respond? i.e. if Accepts contains text/html, return the login page. If it doesn't, return a 401. Perhaps this requires more testing of WebDAV clients than we can effectively do, but it does seem to make semantic sense - if a user agent says it can support (accept) HTML, we should give it HTML. Doesn't really help with XHR, but I thought the 403 response was the right way to deal with that. Justin On 9/17/10 10:59 AM, Felix Meschberger wrote: Hi all, I am trying to tackle issues SLING-1400 [1] and SLING-1745 [2]. The first issue is about WebDAV clients connecting to Sling on root with an OPTIONS request and not being happy with a redirect response, obviously. The second issue is about client side JavaScript application framework which may send XHR requests to Sling, mainly POSTs destined for the POST Servlet but probably also other stuff. Such framework are also generally not very happy getting redirect responses back. Solutions for both problems would probably have to be implemented in the SlingAuthenticator.doLogin method, which is called after an unsuccessful login or after a first request noticing that authentication is required. So here are the options I came up with: * Send back a 401 response, at least for the OPTIONS request to trigger a regular HTTP Basic Authentication * Send back a 403 response, to indicate that access is currently forbidden (we discussed this option earlier [3]). My questions: - Would it be ok to special case the OPTIONS request ? - Shall we generally only send back a generic credentials request (may be a redirect or a form directly or whatever) if the original request was GET and send back either 401 or 403 for all non-GET requests, including HEAD ? - Is it a good idea to send back 401 generally ? - Should we only send back 401 if HTTP Basic authentication is at enabled fully or enabled preemptively and send back 403 if HTTP Basic authentication is switched off completely ? - Am I completely off track ? WDYT ? Regards Felix [1] https://issues.apache.org/jira/browse/SLING-1400 [2] https://issues.apache.org/jira/browse/SLING-1745 [3] http://markmail.org/message/jwsvk6swnxvvfsyz
Hudson build is still unstable: sling-trunk-1.6 » Apache Sling OSGi Installer Integration Tests #580
See https://hudson.apache.org/hudson/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.osgi.installer.it/changes
Hudson build is still unstable: sling-trunk-1.6 #580
See https://hudson.apache.org/hudson/job/sling-trunk-1.6/changes
Hudson build is still unstable: sling-trunk-1.5 » Apache Sling OSGi Installer Integration Tests #892
See https://hudson.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.osgi.installer.it/changes
Hudson build is still unstable: sling-trunk-1.5 #892
See https://hudson.apache.org/hudson/job/sling-trunk-1.5/changes
Re: Welcome Clemens Wyss
Welcome Clemens. Ian On 18 Sep 2010, at 01:00, Justin Edelson wrote: Welcome aboard Clemens. If I haven't said so already, the Explorer looks great and I'm sure is only going to get better. Seconded :), been very useful already. On 9/17/10 2:34 AM, Felix Meschberger wrote: Hi all, I want to let you know that the Apache Sling PMC decided to invite Clemens Wyss as a committer to the Apache Sling project based on his work on the JCR Explorer; an invitation which Clemens accepted. Thanks. Please join me in welcoming Clemens Wyss as a new committer ! Keep up the good work, Clemens, and thanks for your contributions. And feel free to briefly introduce yourself if you want ;-) Regards Felix
Re: Authentication Issue
On 18 Sep 2010, at 00:59, Felix Meschberger wrote: Hi all, I am trying to tackle issues SLING-1400 [1] and SLING-1745 [2]. The first issue is about WebDAV clients connecting to Sling on root with an OPTIONS request and not being happy with a redirect response, obviously. The second issue is about client side JavaScript application framework which may send XHR requests to Sling, mainly POSTs destined for the POST Servlet but probably also other stuff. Such framework are also generally not very happy getting redirect responses back. Solutions for both problems would probably have to be implemented in the SlingAuthenticator.doLogin method, which is called after an unsuccessful login or after a first request noticing that authentication is required. So here are the options I came up with: * Send back a 401 response, at least for the OPTIONS request to trigger a regular HTTP Basic Authentication * Send back a 403 response, to indicate that access is currently forbidden (we discussed this option earlier [3]). My questions: - Would it be ok to special case the OPTIONS request ? IMHO Yes, as AFAIK its only normally seen with webdav. - Shall we generally only send back a generic credentials request (may be a redirect or a form directly or whatever) if the original request was GET and send back either 401 or 403 for all non-GET requests, including HEAD ? The credentials request should include something that doesn't need to be parsed to indicate it is a credentials request. (header or status code). Redirect or form is Ok provided the request is not Ajax. If it is, then who knows what the client will do, in which case status code is really the only correct way of responding. Can you do a 401/403 and the html, redirect in as a meta-equiv if required. - Is it a good idea to send back 401 generally ? - Should we only send back 401 if HTTP Basic authentication is at enabled fully or enabled preemptively and send back 403 if HTTP Basic authentication is switched off completely ? This prompted me to go and look at the spec[1]. 401 must be have a WWW-Authenticate which will cause the login box to appear (iirc) even with Ajax requests. And there is no way to know if the client wants to see a login box. Could be very confusing for anyone with SSO or Form based auth. Sending a bare 401 might be the right thing to do where the user is anon, but that would be illegal, perhaps the client can work out that they are not logged in, which makes 403 Ok. Ian 1 http://www.freesoft.org/CIE/RFC/2068/209.htm - Am I completely off track ? WDYT ? Regards Felix [1] https://issues.apache.org/jira/browse/SLING-1400 [2] https://issues.apache.org/jira/browse/SLING-1745 [3] http://markmail.org/message/jwsvk6swnxvvfsyz
