Re: [jira] Created: (SLING-1770) ResourceUtil.getParent(String) doesn't handle paths with workspace prefixes
Hi, Am 13.09.2010 21:20, schrieb Justin Edelson (JIRA): ResourceUtil.getParent(String) doesn't handle paths with workspace prefixes --- Key: SLING-1770 URL: https://issues.apache.org/jira/browse/SLING-1770 Project: Sling Issue Type: Bug Components: API Reporter: Justin Edelson Assignee: Justin Edelson ResourceUtil.getParent(otherwsp:/path) should return otherwsp:/. Good catch. Following up to this: what is the parent of otherwsp:/ ? The parent for / is null to incidate there is no parent to the root. Regards Felix
[jira] Resolved: (SLING-1773) Possible to store newly install bundle digests into bundle-digests.properties immediately after the bundle is installed successfully
[ https://issues.apache.org/jira/browse/SLING-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1773. - Assignee: Carsten Ziegeler Fix Version/s: OSGi Installer 3.0.0 Resolution: Fixed With SLING-1737 we now have a better state management which ensures that once a bundle is installed it is immediately marked as installed. The extra saving of digests has been completly removed. Possible to store newly install bundle digests into bundle-digests.properties immediately after the bundle is installed successfully Key: SLING-1773 URL: https://issues.apache.org/jira/browse/SLING-1773 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: JCR Installer 3.0.0 Environment: CQ5.3 Reporter: zhangchunlong Assignee: Carsten Ziegeler Priority: Minor Fix For: OSGi Installer 3.0.0 Bundle slinginstall:org.apache.sling.osgi.installer-3.0.0-R900409.jar in CQ5.3 only try to store the bundle digests into bundle-digests.properties when the server is shutting down. In case some bundles are installed and the server is not shutdown properly. eg. crash, being killed, next time when CQ5.3 starts, will try to re-install those bundles and leave the bundle status as installed. It might be good to store such information immediately after any bundle is being installed successfully if possible. To reproduce the issue: 1. create some test bundle 2. start the CQ5.3 instance, install the test bundle into some /install folder. 3. kill the CQ5.3 instance. 4. start the CQ5.3 instance again. 5. from the crx-quickstart/logs/error.log, could see the test bundle is being installed again. 6. from Felix console, the test bundle status is installed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
No success trying Sling
Hello! yesterday I wanted to try Sling again and have a look at David Mini CMS https://cwiki.apache.org/SLING/gsoc-2010-mini-cms-project.html Unexpectedly that failed (not because of David Mini CMS). First I found out that no binaries are available on the website because the links are broken: https://issues.apache.org/jira/browse/SLING-1768 (The download page states: Note that the above releases are relatively old (May 2009). If you want to experiment with bleeding edge code, building Sling yourself is not that hard.. Why are no binaries of the most recent released version made available?!) Then I spent some time finding an old file for sling in the archive and tried to install David Mini CMS on it. But that also failed because some of the dependencies are not met. Obviously and understandably David Mini CMS depends on more recent Sling components than those provided by an obsolete version of Sling. Then I tried to build Sling from the sources with Maven according to http://sling.apache.org/site/getting-and-building-sling.html But that also failed because testSemiRandomInstall fails: https://issues.apache.org/jira/browse/SLING-1737 And at the end launching Sling of cause also fails because there is no jar file to be launched. Cheers, Andreas
[jira] Commented: (SLING-1768) Download links are broken
[ https://issues.apache.org/jira/browse/SLING-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909132#action_12909132 ] Carsten Ziegeler commented on SLING-1768: - The correct download page is : http://sling.apache.org/site/downloads.cgi but nevertheless you're right that the links are broken there as well Download links are broken - Key: SLING-1768 URL: https://issues.apache.org/jira/browse/SLING-1768 Project: Sling Issue Type: Bug Components: Site Reporter: Andreas Kuckartz Priority: Blocker Most or all of the binary download links on this page are broken: http://sling.apache.org/site/downloads.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1768) Download links are broken
[ https://issues.apache.org/jira/browse/SLING-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909136#action_12909136 ] Felix Meschberger commented on SLING-1768: -- Thanks for reporting. There has been a problem transcribing the links from Confluence to the official format supported by the mirros.cgi script (backing downloads.cgi). This is now fixed. Download links are broken - Key: SLING-1768 URL: https://issues.apache.org/jira/browse/SLING-1768 Project: Sling Issue Type: Bug Components: Site Reporter: Andreas Kuckartz Priority: Blocker Most or all of the binary download links on this page are broken: http://sling.apache.org/site/downloads.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: No success trying Sling
Hi Andreas, we are very sorry about the current situation - thanks for reporting the problems! We're currently working on fixing the download page and it should be working again very soon. If during a build tests are failing, the easiest thing to get a running Sling at the end, is to disable the tests by running mvn -Dmaven.test.skip=true install It's not the way it should be, but nevertheless gets you the wanted result :) We're currently working on getting the tests running again. So this is just a temporary problem. In addition we're very hard working on getting the next big milestone, SLING-6, ready - this will be a ready to start download of the latest and greatest :) We're currently in the middle of the process, so SLING-6 should be ready in some weeks. If you have additional comments or run into other problems, please let us know. Regards Carsten Andreas Kuckartz wrote Hello! yesterday I wanted to try Sling again and have a look at David Mini CMS https://cwiki.apache.org/SLING/gsoc-2010-mini-cms-project.html Unexpectedly that failed (not because of David Mini CMS). First I found out that no binaries are available on the website because the links are broken: https://issues.apache.org/jira/browse/SLING-1768 (The download page states: Note that the above releases are relatively old (May 2009). If you want to experiment with bleeding edge code, building Sling yourself is not that hard.. Why are no binaries of the most recent released version made available?!) Then I spent some time finding an old file for sling in the archive and tried to install David Mini CMS on it. But that also failed because some of the dependencies are not met. Obviously and understandably David Mini CMS depends on more recent Sling components than those provided by an obsolete version of Sling. Then I tried to build Sling from the sources with Maven according to http://sling.apache.org/site/getting-and-building-sling.html But that also failed because testSemiRandomInstall fails: https://issues.apache.org/jira/browse/SLING-1737 And at the end launching Sling of cause also fails because there is no jar file to be launched. Cheers, Andreas -- Carsten Ziegeler cziege...@apache.org
Hudson build is still unstable: sling-trunk-1.5 #886
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 #886
See https://hudson.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.osgi.installer.it/886/
[jira] Commented: (SLING-1737) Add state management for resources
[ https://issues.apache.org/jira/browse/SLING-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909141#action_12909141 ] Carsten Ziegeler commented on SLING-1737: - I retried the tests running on Java 5 and Java 6 - and they run each time :( It seems the -Dpax.exam.log.level=DEBUG test option does not work like I expected; at least I can't find the relevant log statements in the logs you provided :( So maybe could you please rerun the tests and change directly the property value in the pom.xml? Please also make sure that you did a mvn install on the installer/osgi/installer project before you run the tests. @Justin - Are the tests for you failing with both Maven versions or just with 3.0-beta-3? - I'm just speculating here, but as I'm also using OS X with Maven 2.2.1, there must be some difference between our environments. Add state management for resources -- Key: SLING-1737 URL: https://issues.apache.org/jira/browse/SLING-1737 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: OSGi Installer 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: OSGi Installer 3.0.0 Attachments: ConfigInstallTest-debug.log.gz, debug.zip, RemovedResourceDetectionTest-debug.log.gz Currently there is no state management, so it is hard to tell if a resource has been installed, should be installed, uninstalled etc. In some situations this leads to endless loops where something is tried over and over again - although nothing needs to be done anymore or can't be done. If we add proper state management to the resources, the installer knows what needs to be done and can act accordingly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
David Mini CMS core (core) does not start (Re: No success trying Sling)
Thanks, Carsten, for your informative reply and hint! I am now running a freshly built Sling. But David Mini CMS still has problems. The bundle David Mini CMS core (core) does not start: ERROR: org.apache.sling.commons.scheduler,version=2.1 -- Cannot be resolved I have also appended the log. I did not find org.apache.sling.commons.scheduler in the list of bundles displayed in the Apache Sling Web Console. Cheers, Andreas --- 14.09.2010 10:08:21.692 *ERROR* [1704184...@qtp-1616586953-8] org.apache.felix.http.jetty %bundles.pluginTitle: Cannot start (org.osgi.framework.BundleException: Unresolved constraint in bundle core [67]: Unable to resolve 67.0: missing requirement [67.0] package; ((package=org.apache.sling.commons.scheduler)(version=2.1.0))) org.osgi.framework.BundleException: Unresolved constraint in bundle core [67]: Unable to resolve 67.0: missing requirement [67.0] package; ((package=org.apache.sling.commons.scheduler)(version=2.1.0)) at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3409) at org.apache.felix.framework.Felix.startBundle(Felix.java:1709) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:892) at org.apache.felix.webconsole.internal.core.BundlesServlet.doPost(BundlesServlet.java:327) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:428) at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:375) at org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:91) at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:77) at org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42) at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49) at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33) at org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48) at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39) at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:536) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:930) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Re: David Mini CMS core (core) does not start (Re: No success trying Sling)
Hi Andreas, you need that bundle installed to start David. You can find it in http://svn.apache.org/repos/asf/sling/trunk/bundles/commons/scheduler/ http://svn.apache.org/repos/asf/sling/trunk/bundles/commons/scheduler/Once you created the bundle, you can install it using the console. Bye, Federico 2010/9/14 Andreas Kuckartz a.kucka...@ping.de Thanks, Carsten, for your informative reply and hint! I am now running a freshly built Sling. But David Mini CMS still has problems. The bundle David Mini CMS core (core) does not start: ERROR: org.apache.sling.commons.scheduler,version=2.1 -- Cannot be resolved I have also appended the log. I did not find org.apache.sling.commons.scheduler in the list of bundles displayed in the Apache Sling Web Console. Cheers, Andreas --- 14.09.2010 10:08:21.692 *ERROR* [1704184...@qtp-1616586953-8] org.apache.felix.http.jetty %bundles.pluginTitle: Cannot start (org.osgi.framework.BundleException: Unresolved constraint in bundle core [67]: Unable to resolve 67.0: missing requirement [67.0] package; ((package=org.apache.sling.commons.scheduler)(version=2.1.0))) org.osgi.framework.BundleException: Unresolved constraint in bundle core [67]: Unable to resolve 67.0: missing requirement [67.0] package; ((package=org.apache.sling.commons.scheduler)(version=2.1.0)) at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3409) at org.apache.felix.framework.Felix.startBundle(Felix.java:1709) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:892) at org.apache.felix.webconsole.internal.core.BundlesServlet.doPost(BundlesServlet.java:327) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:428) at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:375) at org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:91) at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:77) at org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42) at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49) at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33) at org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48) at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39) at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:536) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:930) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
[jira] Resolved: (SLING-1768) Download links are broken
[ https://issues.apache.org/jira/browse/SLING-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-1768. -- Assignee: Felix Meschberger Resolution: Fixed Download links seem to be good again. Thus resolving this issue for now. Download links are broken - Key: SLING-1768 URL: https://issues.apache.org/jira/browse/SLING-1768 Project: Sling Issue Type: Bug Components: Site Reporter: Andreas Kuckartz Assignee: Felix Meschberger Priority: Blocker Most or all of the binary download links on this page are broken: http://sling.apache.org/site/downloads.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: David Mini CMS core (core) does not start (Re: No success trying Sling)
I had to manually install and start these two bundles using the console and now David Mini CMS is also running! org.apache.sling.commons.scheduler org.apache.sling.commons.threads Cheers, Andreas
Re: David Mini CMS core (core) does not start (Re: No success trying Sling)
Andreas Kuckartz wrote I had to manually install and start these two bundles using the console and now David Mini CMS is also running! org.apache.sling.commons.scheduler org.apache.sling.commons.threads Maybe we should add those to the launchpad by default? Carsten -- Carsten Ziegeler cziege...@apache.org
Re: David Mini CMS core (core) does not start (Re: No success trying Sling)
On Tue, Sep 14, 2010 at 10:42 AM, Carsten Ziegeler cziege...@apache.org wrote: Andreas Kuckartz wrote I had to manually install and start these two bundles using the console and now David Mini CMS is also running! org.apache.sling.commons.scheduler org.apache.sling.commons.threads Maybe we should add those to the launchpad by default? +1, those are commonly used. -Bertrand
PermGen space problems Re: integration tests
I am aware from another project that PermGen space problems can be really nasty... As a wild guess this might help: How to deal with “java.lang.OutOfMemoryError: PermGen space” error http://stackoverflow.com/questions/88235/how-to-deal-with-java-lang-outofmemoryerror-permgen-space-error Cheers, Andreas --- Am 14.09.2010 10:14, schrieb Felix Meschberger: It turns out, that my seemingly random failures might be related to Perm Gen issues: After increasing the Perm Gen space (actually doubling it to 512M) the full built ran through smoothly.
Re: PermGen space problems Re: integration tests
On 14 September 2010 18:56, Andreas Kuckartz a.kucka...@ping.de wrote: I am aware from another project that PermGen space problems can be really nasty... As a wild guess this might help: How to deal with “java.lang.OutOfMemoryError: PermGen space” error http://stackoverflow.com/questions/88235/how-to-deal-with-java-lang-outofmemoryerror-permgen-space-error Jackrabbit leaves some timer threads running that prevents a webapp to be fully GC'ed after shutdown. So even the fixes suggested in that stackoverflow page aren't sufficient. Am 14.09.2010 10:14, schrieb Felix Meschberger: It turns out, that my seemingly random failures might be related to Perm Gen issues: After increasing the Perm Gen space (actually doubling it to 512M) the full built ran through smoothly. -- -Tor
Re: David Mini CMS core (core) does not start (Re: No success trying Sling)
Now the first real problem with David Mini CMS: I want to save the first new page but an error message Error during save pops up and the log contains this entry: 14.09.2010 10:58:22.121 *ERROR* [127.0.0.1 [1284454702109] POST /content/david/2010/09/15/ HTTP/1.1] org.apache.sling.servlets.post.impl.operations.ModifyOperation Access Denied Access denied. I am logged in as admin. Cheers, Andreas
[jira] Commented: (SLING-1737) Add state management for resources
[ https://issues.apache.org/jira/browse/SLING-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909162#action_12909162 ] Carsten Ziegeler commented on SLING-1737: - This might be a sync problem in the OsgiInstallerImpl - Felix reported that he got similar errors while running the tests under load. Looking at the OsgiInstallerImpl it can definitly run into a deadlock (this bug has been there forever, but is more prominent now), so once I can reproduce, I'll try to fix this sync problem Add state management for resources -- Key: SLING-1737 URL: https://issues.apache.org/jira/browse/SLING-1737 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: OSGi Installer 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: OSGi Installer 3.0.0 Attachments: ConfigInstallTest-debug.log.gz, debug.zip, RemovedResourceDetectionTest-debug.log.gz Currently there is no state management, so it is hard to tell if a resource has been installed, should be installed, uninstalled etc. In some situations this leads to endless loops where something is tried over and over again - although nothing needs to be done anymore or can't be done. If we add proper state management to the resources, the installer knows what needs to be done and can act accordingly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1774) OSGi Installer Integration Tests installs test bundles
OSGi Installer Integration Tests installs test bundles -- Key: SLING-1774 URL: https://issues.apache.org/jira/browse/SLING-1774 Project: Sling Issue Type: Bug Components: Installer Reporter: Felix Meschberger When running mvn clean install of the OSGi Installer Integration Tests (installer/osgi/it) project the test JAR files are all installed as artifacts attached to the project. This does not do any harm (probably, because I would assume this project is never deployed anyway), it is probably just overkill. We should try to prevent installing/deploying these test bundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (SLING-1770) ResourceUtil.getParent(String) doesn't handle paths with workspace prefixes
On Sep 14, 2010, at 2:28 AM, Felix Meschberger fmesc...@gmail.com wrote: Hi, Am 13.09.2010 21:20, schrieb Justin Edelson (JIRA): ResourceUtil.getParent(String) doesn't handle paths with workspace prefixes --- Key: SLING-1770 URL: https://issues.apache.org/jira/browse/SLING-1770 Project: Sling Issue Type: Bug Components: API Reporter: Justin Edelson Assignee: Justin Edelson ResourceUtil.getParent(otherwsp:/path) should return otherwsp:/. Good catch. Following up to this: what is the parent of otherwsp:/ ? Should be null, I'll add a test for this. The parent for / is null to incidate there is no parent to the root. Regards Felix
[jira] Updated: (SLING-1774) OSGi Installer Integration Tests installs test bundles
[ https://issues.apache.org/jira/browse/SLING-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1774: Fix Version/s: OSGi Installer 3.0.0 Affects Version/s: OSGi Installer 3.0.0 OSGi Installer Integration Tests installs test bundles -- Key: SLING-1774 URL: https://issues.apache.org/jira/browse/SLING-1774 Project: Sling Issue Type: Bug Components: Installer Affects Versions: OSGi Installer 3.0.0 Reporter: Felix Meschberger Assignee: Carsten Ziegeler Fix For: OSGi Installer 3.0.0 When running mvn clean install of the OSGi Installer Integration Tests (installer/osgi/it) project the test JAR files are all installed as artifacts attached to the project. This does not do any harm (probably, because I would assume this project is never deployed anyway), it is probably just overkill. We should try to prevent installing/deploying these test bundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-1774) OSGi Installer Integration Tests installs test bundles
[ https://issues.apache.org/jira/browse/SLING-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-1774: --- Assignee: Carsten Ziegeler OSGi Installer Integration Tests installs test bundles -- Key: SLING-1774 URL: https://issues.apache.org/jira/browse/SLING-1774 Project: Sling Issue Type: Bug Components: Installer Affects Versions: OSGi Installer 3.0.0 Reporter: Felix Meschberger Assignee: Carsten Ziegeler Fix For: OSGi Installer 3.0.0 When running mvn clean install of the OSGi Installer Integration Tests (installer/osgi/it) project the test JAR files are all installed as artifacts attached to the project. This does not do any harm (probably, because I would assume this project is never deployed anyway), it is probably just overkill. We should try to prevent installing/deploying these test bundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1737) Add state management for resources
[ https://issues.apache.org/jira/browse/SLING-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909197#action_12909197 ] Carsten Ziegeler commented on SLING-1737: - I still can't reproduce it - even with high load :( But I fixed the potential sync problem in revision 996845 - so maybe this fixes the problems? Add state management for resources -- Key: SLING-1737 URL: https://issues.apache.org/jira/browse/SLING-1737 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: OSGi Installer 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: OSGi Installer 3.0.0 Attachments: ConfigInstallTest-debug.log.gz, debug.zip, RemovedResourceDetectionTest-debug.log.gz Currently there is no state management, so it is hard to tell if a resource has been installed, should be installed, uninstalled etc. In some situations this leads to endless loops where something is tried over and over again - although nothing needs to be done anymore or can't be done. If we add proper state management to the resources, the installer knows what needs to be done and can act accordingly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1737) Add state management for resources
[ https://issues.apache.org/jira/browse/SLING-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909211#action_12909211 ] Pontus Amberg commented on SLING-1737: -- Looks like the sync problem might have been the cause of my problems. I can now build the current trunk with no test failures. Add state management for resources -- Key: SLING-1737 URL: https://issues.apache.org/jira/browse/SLING-1737 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: OSGi Installer 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: OSGi Installer 3.0.0 Attachments: ConfigInstallTest-debug.log.gz, debug.zip, RemovedResourceDetectionTest-debug.log.gz Currently there is no state management, so it is hard to tell if a resource has been installed, should be installed, uninstalled etc. In some situations this leads to endless loops where something is tried over and over again - although nothing needs to be done anymore or can't be done. If we add proper state management to the resources, the installer knows what needs to be done and can act accordingly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1666) Check and update tests
[ https://issues.apache.org/jira/browse/SLING-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1666. - Resolution: Fixed I'll resolve this for now; however more tests wouldn't hurt Check and update tests -- Key: SLING-1666 URL: https://issues.apache.org/jira/browse/SLING-1666 Project: Sling Issue Type: Task Components: Installer Affects Versions: OSGi Installer 3.0.0 Reporter: Carsten Ziegeler Fix For: OSGi Installer 3.0.0 We should update/enhance/check the current tests if they check everything, especially with the changes to the it tests we might have lost some testing -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1747) Don't copy already installed resources
[ https://issues.apache.org/jira/browse/SLING-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1747. - Resolution: Won't Fix We can't avoid the copying as the installer needs symbolic name and version to check if the resource has been commtted on previous attempts. As this information is inside the data, we have to read from the input stream anyway. Setting to won't fix. Don't copy already installed resources -- Key: SLING-1747 URL: https://issues.apache.org/jira/browse/SLING-1747 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: OSGi Installer 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: OSGi Installer 3.0.0 Currently during the rendezvous of the osgi installer and a client (e.g. jcr install) jcr install sends all available resources which are then first processed by the osgi installer by creating local copies. In a second (async) step, these new resources are compared with available ones and if already available discarded. With larger installation this becomes very disc intensive and slow as each bundle is copied over on startup just to be deleted in the second step. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1147) Installing SNAPSHOT of bundle installed via jcrinstall causes both bundles to be active
[ https://issues.apache.org/jira/browse/SLING-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1147. - Fix Version/s: OSGi Installer 3.0.0 Resolution: Fixed With the new state management this is definitly fixed. Installing SNAPSHOT of bundle installed via jcrinstall causes both bundles to be active --- Key: SLING-1147 URL: https://issues.apache.org/jira/browse/SLING-1147 Project: Sling Issue Type: Bug Components: Installer Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor Fix For: OSGi Installer 3.0.0 (from SLING-1106) I have a bundle with version 2.0.5-tlp-SOMETHING in the repo (/libs/sling/install) Now I want to update this bundle to a snapshot version using the web console After a restart, both versions are active - the one updated through the web console and the one from the libs folder in the repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1737) Add state management for resources
[ https://issues.apache.org/jira/browse/SLING-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909222#action_12909222 ] Carsten Ziegeler commented on SLING-1737: - Great, thanks Pontus. So once we have confirmation from Justin we can hopefully close this bug. Add state management for resources -- Key: SLING-1737 URL: https://issues.apache.org/jira/browse/SLING-1737 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: OSGi Installer 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: OSGi Installer 3.0.0 Attachments: ConfigInstallTest-debug.log.gz, debug.zip, RemovedResourceDetectionTest-debug.log.gz Currently there is no state management, so it is hard to tell if a resource has been installed, should be installed, uninstalled etc. In some situations this leads to endless loops where something is tried over and over again - although nothing needs to be done anymore or can't be done. If we add proper state management to the resources, the installer knows what needs to be done and can act accordingly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1737) Add state management for resources
[ https://issues.apache.org/jira/browse/SLING-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909245#action_12909245 ] Justin Edelson commented on SLING-1737: --- ditto. going on my third good build. Add state management for resources -- Key: SLING-1737 URL: https://issues.apache.org/jira/browse/SLING-1737 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: OSGi Installer 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: OSGi Installer 3.0.0 Attachments: ConfigInstallTest-debug.log.gz, debug.zip, RemovedResourceDetectionTest-debug.log.gz Currently there is no state management, so it is hard to tell if a resource has been installed, should be installed, uninstalled etc. In some situations this leads to endless loops where something is tried over and over again - although nothing needs to be done anymore or can't be done. If we add proper state management to the resources, the installer knows what needs to be done and can act accordingly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1775) add scheduler and threads bundles to launchpad
add scheduler and threads bundles to launchpad -- Key: SLING-1775 URL: https://issues.apache.org/jira/browse/SLING-1775 Project: Sling Issue Type: Task 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] Commented: (SLING-1774) OSGi Installer Integration Tests installs test bundles
[ https://issues.apache.org/jira/browse/SLING-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909258#action_12909258 ] Carsten Ziegeler commented on SLING-1774: - I've done similar changes to the osgi installer project which also created a dummy test bundle. Revision 996905 OSGi Installer Integration Tests installs test bundles -- Key: SLING-1774 URL: https://issues.apache.org/jira/browse/SLING-1774 Project: Sling Issue Type: Bug Components: Installer Affects Versions: OSGi Installer 3.0.0 Reporter: Felix Meschberger Assignee: Carsten Ziegeler Fix For: OSGi Installer 3.0.0 When running mvn clean install of the OSGi Installer Integration Tests (installer/osgi/it) project the test JAR files are all installed as artifacts attached to the project. This does not do any harm (probably, because I would assume this project is never deployed anyway), it is probably just overkill. We should try to prevent installing/deploying these test bundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1746) Use slf4j instead of log service
[ https://issues.apache.org/jira/browse/SLING-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1746: Component/s: Installer Use slf4j instead of log service Key: SLING-1746 URL: https://issues.apache.org/jira/browse/SLING-1746 Project: Sling Issue Type: Task Components: Installer Affects Versions: OSGi Installer 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Priority: Minor Fix For: OSGi Installer 3.0.0 The installer uses currently the LogService to avoid dependencies - however nearly every log service implementation comes with various logging api's - so from a dependency pov it's no difference. The slf4j api (or any other logging api) provides more usuability, therefore we should switch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1558) Too much synchronization
[ https://issues.apache.org/jira/browse/SLING-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1558: Component/s: Installer Too much synchronization Key: SLING-1558 URL: https://issues.apache.org/jira/browse/SLING-1558 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: OSGi Installer 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: OSGi Installer 3.0.0 The OSGIInstallerImpl syncs some methods on the osgi installer thread (not all though), and the installer thread in term internally syncs all actions as well. We can just remove the outer syncs from the OsgiInstallerImpl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Releasing installer bundles?
Hi, I think the osgi installer is now ready for a release, the api looks now fine to me and the implementation now finally seems to pass all our integration tests. In addition I tried the latest code within our product and couldn't find any problems so far. So I think it's time to finally cut a first release of the installer stuff. This would include: osgi installer 3.0.0 jcr installer 3.0.0 file installer 1.0.0 I briefly tested the file installer and it seems to do what it should :) If noone objects I'll cut the releases in the next days. I think we should do a release regardless if we include these bundles in SLING-6 or not; we now worked for several years on this stuff without any real release :) Regards Carsten -- Carsten Ziegeler cziege...@apache.org
RE: [sling explorer] Form based auth with IE to no avail :-(
I would if fiddler provided me this data (headers), such as firebug does... -Original Message- From: Eric Norman [mailto:eric.d.nor...@gmail.com] Sent: Tuesday, September 14, 2010 6:42 PM To: dev@sling.apache.org Subject: Re: [sling explorer] Form based auth with IE to no avail :-( Maybe check if IE is getting/sending the sling cookie on the second request. On Sep 14, 2010 9:36 AM, Clemens Wyss clemens...@mysign.ch wrote: Sling Explorer does form based authentication, which works fine(*) with FF, Safari and Chrome. Unfortunately neither on IE6 nor on IE8 it works. Debugging revealed that the POSTed form data to '/j_security_check' is equal. Nevertheless if I gather the Sling.getSessionInfo() after the aforementioned POST on IE I get the anonymous credentials, whereas on the other browsers I get the expected credentials. What could possibly be the reason herefore? Thx for you help/hints -- Clemens
RE: [sling explorer] Form based auth with IE to no avail :-(
In order to get some more tracking data with fiddler I chnaged the URL from localhost:8080 to my notebook's host name, i.e. cws-lap:8080. Now I get a security warning from IE. Unfortunately I only have a german version and hence only the german warning text: Die Seite greift auf Informationen aus anderen Daten zu. Dies kann ein Sicherheitproblem darstellen. Möchten Sie den Vorgang fortsetzen? which more or less translates to: The page is accessing information from other data. This could be a security issue. Would you like to proceed? When I proceed I get a javascript error and the resource tree is not redered. I guess this is another problem (which is nonetheless to be solved, too?) -Original Message- From: Clemens Wyss [mailto:clemens...@mysign.ch] Sent: Tuesday, September 14, 2010 7:22 PM To: 'dev@sling.apache.org' Subject: RE: [sling explorer] Form based auth with IE to no avail :-( I would if fiddler provided me this data (headers), such as firebug does... -Original Message- From: Eric Norman [mailto:eric.d.nor...@gmail.com] Sent: Tuesday, September 14, 2010 6:42 PM To: dev@sling.apache.org Subject: Re: [sling explorer] Form based auth with IE to no avail :-( Maybe check if IE is getting/sending the sling cookie on the second request. On Sep 14, 2010 9:36 AM, Clemens Wyss clemens...@mysign.ch wrote: Sling Explorer does form based authentication, which works fine(*) with FF, Safari and Chrome. Unfortunately neither on IE6 nor on IE8 it works. Debugging revealed that the POSTed form data to '/j_security_check' is equal. Nevertheless if I gather the Sling.getSessionInfo() after the aforementioned POST on IE I get the anonymous credentials, whereas on the other browsers I get the expected credentials. What could possibly be the reason herefore? Thx for you help/hints -- Clemens
Re: Releasing installer bundles?
+1 Regards Felix Am 14.09.2010 18:46, schrieb Carsten Ziegeler: Hi, I think the osgi installer is now ready for a release, the api looks now fine to me and the implementation now finally seems to pass all our integration tests. In addition I tried the latest code within our product and couldn't find any problems so far. So I think it's time to finally cut a first release of the installer stuff. This would include: osgi installer 3.0.0 jcr installer 3.0.0 file installer 1.0.0 I briefly tested the file installer and it seems to do what it should :) If noone objects I'll cut the releases in the next days. I think we should do a release regardless if we include these bundles in SLING-6 or not; we now worked for several years on this stuff without any real release :) Regards Carsten
Re: Authentication/Authorization and jackrabbit.usermanager functionality
FYI - Created JCR-2748 and submitted a patch to provide a simple way to disable anonymous access to the security workspace. Ian - have you looked at turning the Sakai server bundle into a fragment attached to the Sling JCR Jackrabbit Server bundle? I do that with a custom FileSystem and DataSource implementation and it seems to work OK. Having this as a fragment would make it easier for other projects to consume, although I understand if that isn't really the point of Sakai. Justin On 9/13/10 7:09 PM, Ian Boston wrote: IIRC the security workspace is not set up with access controllable nodes, so you cant use a policy on a node. We did [1] for the securty workspace. 1 http://github.com/sakaiproject/nakamura/blob/master/bundles/server/src/main/java/org/apache/jackrabbit/core/security/user/DelegatedUserAccessControlProvider.java On 14 Sep 2010, at 05:34, Justin Edelson wrote: Oh... I get it. There's no ACL on the user and group nodes in the security workspace. But trying to apply an ACL to / or /rep:security returns an exception $ curl-FprincipalId=anonymous -fprivil...@jcr:all=denied http://admin:ad...@localhost:/rep:security.modifyAce.html?sling.workspace=security html head titleError while processing security:/rep:security/title /head body h1Error while processing security:/rep:security/h1 table tbody tr tdStatus/td tddiv id=Status500/div/td /tr tr tdMessage/td tddiv id=Messagejavax.jcr.RepositoryException: Failed to create ace./div/td /tr tr tdLocation/td tda href=/_rep_security id=Location/_rep_security/a/td /tr tr tdParent Location/td tda href=/ id=ParentLocation//a/td /tr tr tdPath/td tddiv id=Pathsecurity:/rep:security/div/td /tr tr tdReferer/td tda href= id=Referer/a/td /tr tr tdChangeLog/td tddiv id=ChangeLogpre/pre/div/td /tr /tbody /table pa href=Go Back/a/p pa href=/_rep_securityModified Resource/a/p pa href=/Parent of Modified Resource/a/p /body /html On 9/11/10 10:25 AM, Felix Meschberger wrote: Hi, Unless I am completely mistaken, the usermanager uses the request's session to get at the Jackrabbit UserManager to do any tasks, which is the absolutely correct thing IMHO. We should definitely leave this kind of access control to Jackrabbit (resp. the configured functionality of Jackrabbit) and not impose our own idea ontop of it. There is one situation where an admin session is always retrieved: The CreeateUser servlet. This is probably a bug and should only use an admin session for self-registration. Regards Felix Am 10.09.2010 00:47, schrieb Mike Moulton: I recently had the need to get a list of users from an AJAX style client and found the jackrabbit usermanager exposes this functionality at system/userManager/user. As a part of this discovery, I noticed the listing of JCR users is not restricted in any way. If the usermanager bundle is installed, the following endpoint is open to the public: http://localhost:8080/system/userManager/user.tidy.1.json, providing a complete user list to anyone digging around. Any usermanager command that allows modifications to the JCR first checks if the user is an admin, but it seems all the read-only commands skip this check. Is this by intention, or was this simply missed? In addition, what are the thoughts on adding some sort of authorization component beyond just the isAdmin check? Maybe inspecting the jcr:readAccessControl / jcr:modifyAccessControl for the root node? -- Mike
Re: David Mini CMS core (core) does not start (Re: No success trying Sling)
That problem disappeared with the latest Sling revision. Cheers, Andreas Am 14.09.2010 11:02, schrieb Andreas Kuckartz: Now the first real problem with David Mini CMS: I want to save the first new page but an error message Error during save pops up and the log contains this entry: 14.09.2010 10:58:22.121 *ERROR* [127.0.0.1 [1284454702109] POST /content/david/2010/09/15/ HTTP/1.1] org.apache.sling.servlets.post.impl.operations.ModifyOperation Access Denied Access denied. I am logged in as admin. Cheers, Andreas
[jira] Resolved: (SLING-1749) sling.js prevents baseurl being detected correctly when the webapp isn't on the / docroot
[ https://issues.apache.org/jira/browse/SLING-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1749. --- Resolution: Fixed this was fixed in r995889 sling.js prevents baseurl being detected correctly when the webapp isn't on the / docroot - Key: SLING-1749 URL: https://issues.apache.org/jira/browse/SLING-1749 Project: Sling Issue Type: Bug Components: Servlets Reporter: Tom Barber Assignee: Justin Edelson Fix For: Servlets Post 2.0.6 Running the svn checkout from this morning the sling.js file located in sling/bundles/servlets/post has a bug on line 416. The / being appended breaks the substring and the baseurl is always . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: SLING-1741
...ping... On Thu, Sep 9, 2010 at 10:12 PM, Justin Edelson justinedel...@gmail.com wrote: I put up a proposed patch for SLING-1741 at http://codereview.appspot.com/2144046 This didn't seem to break any integration tests, but I also commented out the whole cutting off the selector/suffix part and got no integration test failures, so I'm concerned the code involved might not be well-tested. Could someone involved in SLING-588 take a look? Thanks, Justin
RE: [sling explorer] Form based auth with IE to no avail :-(
I would if fiddler provided me this data (headers), such as firebug does... -- http://weblogs.asp.net/lorenh/archive/2008/01/10/tip-for-using-fiddler-on-localhost.aspx the '.' does it!, OMG I can now proceed debugging the IE traces... -Original Message- From: Clemens Wyss [mailto:clemens...@mysign.ch] Sent: Tuesday, September 14, 2010 7:22 PM To: 'dev@sling.apache.org' Subject: RE: [sling explorer] Form based auth with IE to no avail :-( I would if fiddler provided me this data (headers), such as firebug does... -Original Message- From: Eric Norman [mailto:eric.d.nor...@gmail.com] Sent: Tuesday, September 14, 2010 6:42 PM To: dev@sling.apache.org Subject: Re: [sling explorer] Form based auth with IE to no avail :-( Maybe check if IE is getting/sending the sling cookie on the second request. On Sep 14, 2010 9:36 AM, Clemens Wyss clemens...@mysign.ch wrote: Sling Explorer does form based authentication, which works fine(*) with FF, Safari and Chrome. Unfortunately neither on IE6 nor on IE8 it works. Debugging revealed that the POSTed form data to '/j_security_check' is equal. Nevertheless if I gather the Sling.getSessionInfo() after the aforementioned POST on IE I get the anonymous credentials, whereas on the other browsers I get the expected credentials. What could possibly be the reason herefore? Thx for you help/hints -- Clemens
