[VOTE] Release Apache Sling JCR Resource Resolver 2.3.10
Hi, We solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12327963 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1139/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1139 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours.
Re: [VOTE] Release Apache Sling JCR Resource Resolver 2.3.10
Am 14.10.14 um 10:27 schrieb Antonio Sanso: Hi, We solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12327963 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1139/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1139 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. +1 Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Build failed in Jenkins: sling-trunk-1.8 » Apache Sling Resource Access Security Integration Tests #292
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/292/ -- [INFO] [INFO] [INFO] Building Apache Sling Resource Access Security Integration Tests 0.0.1-SNAPSHOT [INFO] Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.testing.tools/1.0.7-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.testing.tools/1.0.7-SNAPSHOT/maven-metadata.xml (1010 B at 6.1 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.testing.tools/1.0.7-SNAPSHOT/org.apache.sling.testing.tools-1.0.7-20140715.081043-1.pom Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.testing.tools/1.0.7-SNAPSHOT/org.apache.sling.testing.tools-1.0.7-20140715.081043-1.pom (5 KB at 4.6 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient-osgi/4.1.2/httpclient-osgi-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient-osgi/4.1.2/httpclient-osgi-4.1.2.pom (7 KB at 302.7 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-client/4.1.2/httpcomponents-client-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-client/4.1.2/httpcomponents-client-4.1.2.pom (12 KB at 617.8 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient/4.1.2/httpclient-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient/4.1.2/httpclient-4.1.2.pom (6 KB at 325.0 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore/4.1.2/httpcore-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore/4.1.2/httpcore-4.1.2.pom (8 KB at 400.9 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-core/4.1.2/httpcomponents-core-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-core/4.1.2/httpcomponents-core-4.1.2.pom (10 KB at 531.6 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpmime/4.1.2/httpmime-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpmime/4.1.2/httpmime-4.1.2.pom (6 KB at 308.4 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient-cache/4.1.2/httpclient-cache-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient-cache/4.1.2/httpclient-cache-4.1.2.pom (7 KB at 386.6 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-osgi/4.1.2/httpcore-osgi-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-osgi/4.1.2/httpcore-osgi-4.1.2.pom (4 KB at 149.7 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-nio/4.1.2/httpcore-nio-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-nio/4.1.2/httpcore-nio-4.1.2.pom (6 KB at 226.4 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad/7-SNAPSHOT/maven-metadata.xml Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad/7-SNAPSHOT/org.apache.sling.launchpad-7-SNAPSHOT.pom [WARNING] The POM for org.apache.sling:org.apache.sling.launchpad:jar:standalone:7-SNAPSHOT is missing, no dependency information available Downloading: http://repo.maven.apache.org/maven2/org/slf4j/slf4j-api/1.7.6/slf4j-api-1.7.6.pom Downloaded: http://repo.maven.apache.org/maven2/org/slf4j/slf4j-api/1.7.6/slf4j-api-1.7.6.pom (3 KB at 154.5 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/slf4j/slf4j-parent/1.7.6/slf4j-parent-1.7.6.pom Downloaded: http://repo.maven.apache.org/maven2/org/slf4j/slf4j-parent/1.7.6/slf4j-parent-1.7.6.pom (12 KB at 684.0 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/slf4j/slf4j-simple/1.7.6/slf4j-simple-1.7.6.pom Downloaded: http://repo.maven.apache.org/maven2/org/slf4j/slf4j-simple/1.7.6/slf4j-simple-1.7.6.pom (2 KB at 79.9 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/jackrabbit/jackrabbit-api/2.7.5/jackrabbit-api-2.7.5.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/jackrabbit/jackrabbit-api/2.7.5/jackrabbit-api-2.7.5.pom (4 KB at 185.6 KB/sec) Downloading:
Build failed in Jenkins: sling-trunk-1.8 #292
See https://builds.apache.org/job/sling-trunk-1.8/292/changes Changes: [asanso] [maven-release-plugin] prepare for next development iteration [asanso] [maven-release-plugin] prepare release org.apache.sling.jcr.resource-2.3.10 -- [...truncated 43912 lines...] [INFO] Apache Sling System Bundle Extension: WS APIs . SUCCESS [7.088s] [INFO] Apache Sling Dynamic Class Loader Support . SUCCESS [21.175s] [INFO] Apache Sling Commons Java Compiler SUCCESS [14.987s] [INFO] Apache Sling JSON Library . SUCCESS [14.357s] [INFO] Apache Sling SLF4J Implementation (Logback) ... SUCCESS [1:02.876s] [INFO] Apache Sling OSGi LogService Implementation ... SUCCESS [11.297s] [INFO] Apache Sling MIME type mapping support SUCCESS [15.094s] [INFO] Apache Sling Commons OSGi support . SUCCESS [14.971s] [INFO] Apache Sling Scheduler Support SUCCESS [14.013s] [INFO] Apache Sling Testing Utilities SUCCESS [21.097s] [INFO] Apache Sling Thread Dumper SUCCESS [11.085s] [INFO] Apache Sling Thread Support ... SUCCESS [11.837s] [INFO] Apache Sling Authentication Service ... SUCCESS [14.850s] [INFO] Apache Sling Form Based Authentication Handler SUCCESS [14.849s] [INFO] Apache Sling Engine Implementation SUCCESS [21.545s] [INFO] Apache Sling Repository API Bundle SUCCESS [10.994s] [INFO] Apache Sling JCR Base Bundle .. SUCCESS [11.473s] [INFO] Apache Sling JCR ClassLoader .. SUCCESS [9.063s] [INFO] Apache Sling Initial Content Loader ... SUCCESS [14.076s] [INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [23.466s] [INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [11.748s] [INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support SUCCESS [11.099s] [INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [8.238s] [INFO] Apache Sling JCR Resource Resolver SUCCESS [41.024s] [INFO] Apache Sling JCR Repository Registration .. SUCCESS [11.477s] [INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [11.918s] [INFO] Apache Sling DavEx Access to repositories . SUCCESS [11.378s] [INFO] Apache Sling JCR WebConsole Bundle SUCCESS [9.365s] [INFO] Apache Sling Oak Repository Server SUCCESS [11.770s] [INFO] Apache Sling SlingRepository Integration Tests SUCCESS [47.629s] [INFO] Apache Sling Servlet Resolver . SUCCESS [14.706s] [INFO] Apache Sling Default GET Servlets . SUCCESS [12.104s] [INFO] Apache Sling Default POST Servlets SUCCESS [14.202s] [INFO] Apache Sling Compat Servlets .. SUCCESS [7.911s] [INFO] Apache Sling Scripting Implementation API . SUCCESS [10.991s] [INFO] Apache Sling Scripting Core implementation SUCCESS [23.322s] [INFO] Apache Sling Scripting JavaScript Support . SUCCESS [26.046s] [INFO] Apache Sling Scripting JSP Support SUCCESS [18.205s] [INFO] Apache Sling JSP Tag Library .. SUCCESS [16.874s] [INFO] Apache Sling JSP Standard Tag Library . SUCCESS [8.225s] [INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [13.969s] [INFO] Apache Sling Bundle Resource Provider . SUCCESS [9.102s] [INFO] Apache Sling Distributed Event Admin .. SUCCESS [14.188s] [INFO] Apache Sling Discovery API SUCCESS [8.436s] [INFO] Apache Sling Resource-Based Discovery Service . SUCCESS [2:56.284s] [INFO] Apache Sling Discovery Support Bundle . SUCCESS [9.354s] [INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [8.984s] [INFO] Apache Sling Event Support SUCCESS [7:02.779s] [INFO] Apache Sling Feature Flags SUCCESS [8.924s] [INFO] Apache Sling Filesystem Resource Provider . SUCCESS [9.201s] [INFO] Apache Sling javax.activation bundle .. SUCCESS [9.534s] [INFO] Apache Sling Service User Mapper .. SUCCESS [12.245s] [INFO] Apache Sling Settings . SUCCESS [12.341s] [INFO] Apache Sling Web Console Branding . SUCCESS [9.450s] [INFO] Apache Sling Web Console Security Provider SUCCESS [11.762s] [INFO] Apache Sling Explorer . SUCCESS [8.807s] [INFO] Apache Sling Health Check Core SUCCESS [20.596s] [INFO] Apache Sling Health Check Annotations . SUCCESS [8.768s] [INFO] Apache Sling Health Check Samples . SUCCESS [14.680s] [INFO] Apache Sling Health Check Support Components .. SUCCESS [12.094s] [INFO] Apache Sling Health Check Webconsole Plugin ... SUCCESS
Re: [VOTE] Release Apache Sling JCR Resource Resolver 2.3.10
+1 On Oct 14, 2014, at 10:27 AM, Antonio Sanso asa...@adobe.com wrote: Hi, We solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12327963 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1139/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1139 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours.
Jenkins build is unstable: sling-oak-it-1.6 » Apache Sling Launchpad Testing #188
See https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/188/
Jenkins build is unstable: sling-oak-it-1.6 #188
See https://builds.apache.org/job/sling-oak-it-1.6/188/
[jira] [Resolved] (SLING-4024) Allow the ResourceResolver Mock Factory to initialize a Resolver via JSON
[ https://issues.apache.org/jira/browse/SLING-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-4024. --- Resolution: Implemented the sling-mock incl. content loader is now in the sling svn: https://svn.apache.org/repos/asf/sling/trunk/testing/mocks/sling-mock currently only a snaphot is deployed to the apache snapshot repo, we plan to do a release soon. setting ticket to resolved. Allow the ResourceResolver Mock Factory to initialize a Resolver via JSON - Key: SLING-4024 URL: https://issues.apache.org/jira/browse/SLING-4024 Project: Sling Issue Type: Improvement Components: Testing Affects Versions: Testing ResourceResolver Mock 0.3.0 Reporter: dan mcweeney Sling can easily produce JSON for a tree of resources. It would make things much easier to be able to initialize the Resource Resolvers produced from the MockResourceResolverFactory with this JSON. It will allow people to create test fixtures based off real data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: FW: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy
Hi everyone, I guess people yet just had no chance to dig into the proposal since there are a lot of scenarios adressed throught this proposal. As far as I understood the API SPI the main driver for this proposal is the massive multisite scenario as described in the mentioned wiki page. Key aspects seem to be to get an aggregated context specific view for a configuration while lookup aspects (such as where to look up the configs and how inheritance is solved) are designed in a pluggable way that allows to implement application specific behavior. From offlist discussions I know that there might be some confusion around how the scoping should work so I just wanted to highlight the mentioned link [3] that might eliminate confusion around the wording (especially appliation). IMHO it would be an extremely valuable addition providing sufficient flexiblity to solve all the cases I do have in mind while establishing one unified methodology to deal with all the non osgi configuration without rewriting casespecific lookup (boilerplate) code over and over again. Best regards, Dominik [3] http://wcm.io/config/api/terminology.html On Sat, Oct 4, 2014 at 1:55 AM, Stefan Seifert sseif...@pro-vision.de wrote: p.s. url [1] is wrong - it should be https://cwiki.apache.org/confluence/x/So2uAg -Original Message- From: Stefan Seifert [mailto:sseif...@pro-vision.de] Sent: Saturday, October 04, 2014 1:54 AM To: dev@sling.apache.org Subject: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy this proposal is about context-specific configuration, that means configuration that cannot be stored as OSGi configurations. OSGi configurations are always system-wide, so they are not well-suited for storing configurations per context e.g. site, region or tenant. this is related to the multitenancy discussion on this list, see [1] for a summary of the past discussion. we've implementation a solution for this and are currently thinking about donating it to Apache Sling. a documentation of what is currently implemented is at [2]. the most relevant pages you should read are [3], [4], [5], [6]. the implementation is based on the requirements from [7], although not all that is listed on that page is implemented currently (but a good deal of it). source code is at [8], a sample application at [9]. the current implementation is targeted to a specific sling-based CMS - but besides the configuration editor and the parameter persistence provider it does not depend on the CMS API but only on the Sling APIs, being technically suited to be donated to Apache Sling. it's already published under apache license 2.0. i'm interested if there is more need in the community for solving the requirements i've listed, and the solutions we have implemented for it. and if there are other sling committers who want to take part in its development and enhancement as well. although we're using the current implementation from wcm.io already in our projects nothing of it's current architecture is carved in stone and i'm open to broaden the scope of requirements it should support. WDYT? stefan [1] https://cwiki.apache.org/confluence/x/zJBcAg [2] http://wcm.io/config/ [3] http://wcm.io/config/api/terminology.html [4] http://wcm.io/config/api/usage-api.html [5] http://wcm.io/config/api/usage-spi.html [6] http://wcm.io/config/editor/usage.html [7] https://wcm-io.atlassian.net/wiki/x/HIAH [8] https://github.com/wcm-io/wcm-io/tree/master/config [9] http://wcm.io/samples/config-sample-app/
Build failed in Jenkins: sling-trunk-1.8 » Apache Sling Resource Access Security Integration Tests #293
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/293/ -- [INFO] [INFO] [INFO] Building Apache Sling Resource Access Security Integration Tests 0.0.1-SNAPSHOT [INFO] Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad/7-SNAPSHOT/org.apache.sling.launchpad-7-SNAPSHOT.pom [WARNING] The POM for org.apache.sling:org.apache.sling.launchpad:jar:standalone:7-SNAPSHOT is missing, no dependency information available Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad/7-SNAPSHOT/org.apache.sling.launchpad-7-SNAPSHOT-standalone.jar [JENKINS] Archiving disabled
Build failed in Jenkins: sling-trunk-1.8 #293
See https://builds.apache.org/job/sling-trunk-1.8/293/changes Changes: [asanso] [maven-release-plugin] prepare for next development iteration [asanso] [maven-release-plugin] prepare release org.apache.sling.jcr.resource-2.3.10 -- [...truncated 28712 lines...] [INFO] Apache Sling System Bundle Extension: WS APIs . SUCCESS [6.759s] [INFO] Apache Sling Dynamic Class Loader Support . SUCCESS [17.883s] [INFO] Apache Sling Commons Java Compiler SUCCESS [15.094s] [INFO] Apache Sling JSON Library . SUCCESS [12.632s] [INFO] Apache Sling SLF4J Implementation (Logback) ... SUCCESS [38.320s] [INFO] Apache Sling OSGi LogService Implementation ... SUCCESS [6.523s] [INFO] Apache Sling MIME type mapping support SUCCESS [12.140s] [INFO] Apache Sling Commons OSGi support . SUCCESS [11.392s] [INFO] Apache Sling Scheduler Support SUCCESS [7.203s] [INFO] Apache Sling Testing Utilities SUCCESS [18.150s] [INFO] Apache Sling Thread Dumper SUCCESS [8.379s] [INFO] Apache Sling Thread Support ... SUCCESS [8.923s] [INFO] Apache Sling Authentication Service ... SUCCESS [11.245s] [INFO] Apache Sling Form Based Authentication Handler SUCCESS [14.306s] [INFO] Apache Sling Engine Implementation SUCCESS [20.695s] [INFO] Apache Sling Repository API Bundle SUCCESS [6.365s] [INFO] Apache Sling JCR Base Bundle .. SUCCESS [9.802s] [INFO] Apache Sling JCR ClassLoader .. SUCCESS [6.730s] [INFO] Apache Sling Initial Content Loader ... SUCCESS [9.467s] [INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [20.562s] [INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [11.131s] [INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support SUCCESS [8.961s] [INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [6.412s] [INFO] Apache Sling JCR Resource Resolver SUCCESS [39.043s] [INFO] Apache Sling JCR Repository Registration .. SUCCESS [9.054s] [INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [11.079s] [INFO] Apache Sling DavEx Access to repositories . SUCCESS [11.999s] [INFO] Apache Sling JCR WebConsole Bundle SUCCESS [8.088s] [INFO] Apache Sling Oak Repository Server SUCCESS [9.029s] [INFO] Apache Sling SlingRepository Integration Tests SUCCESS [48.154s] [INFO] Apache Sling Servlet Resolver . SUCCESS [14.600s] [INFO] Apache Sling Default GET Servlets . SUCCESS [19.020s] [INFO] Apache Sling Default POST Servlets SUCCESS [17.209s] [INFO] Apache Sling Compat Servlets .. SUCCESS [9.186s] [INFO] Apache Sling Scripting Implementation API . SUCCESS [9.001s] [INFO] Apache Sling Scripting Core implementation SUCCESS [23.579s] [INFO] Apache Sling Scripting JavaScript Support . SUCCESS [20.400s] [INFO] Apache Sling Scripting JSP Support SUCCESS [17.886s] [INFO] Apache Sling JSP Tag Library .. SUCCESS [15.079s] [INFO] Apache Sling JSP Standard Tag Library . SUCCESS [8.562s] [INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [10.749s] [INFO] Apache Sling Bundle Resource Provider . SUCCESS [8.737s] [INFO] Apache Sling Distributed Event Admin .. SUCCESS [15.344s] [INFO] Apache Sling Discovery API SUCCESS [6.914s] [INFO] Apache Sling Resource-Based Discovery Service . SUCCESS [2:47.600s] [INFO] Apache Sling Discovery Support Bundle . SUCCESS [8.037s] [INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [6.331s] [INFO] Apache Sling Event Support SUCCESS [6:51.032s] [INFO] Apache Sling Feature Flags SUCCESS [8.693s] [INFO] Apache Sling Filesystem Resource Provider . SUCCESS [8.342s] [INFO] Apache Sling javax.activation bundle .. SUCCESS [7.092s] [INFO] Apache Sling Service User Mapper .. SUCCESS [11.606s] [INFO] Apache Sling Settings . SUCCESS [9.414s] [INFO] Apache Sling Web Console Branding . SUCCESS [6.418s] [INFO] Apache Sling Web Console Security Provider SUCCESS [8.544s] [INFO] Apache Sling Explorer . SUCCESS [8.831s] [INFO] Apache Sling Health Check Core SUCCESS [17.923s] [INFO] Apache Sling Health Check Annotations . SUCCESS [6.468s] [INFO] Apache Sling Health Check Samples . SUCCESS [11.549s] [INFO] Apache Sling Health Check Support Components .. SUCCESS [11.502s] [INFO] Apache Sling Health Check Webconsole Plugin ... SUCCESS [11.061s] [INFO]
Jenkins build is still unstable: sling-oak-it-1.6 » Apache Sling Launchpad Testing #189
See https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/189/
Jenkins build is still unstable: sling-oak-it-1.6 #189
See https://builds.apache.org/job/sling-oak-it-1.6/189/
Re: FW: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy
Hi, It looks like a well documented and complete contribution covering non OSGi configuration and dealing with multiple contexts. I think that is a widely held generic use case, even if for many projects only one context is considered. As such, I think it has a place in Sling, if only to save downstream products going through the expense and pain of implementing the same. I am not certain where it should go. Probably a contrib area under trunk rather than something that is central to starting a Sling instance. On that basis, provided all barriers to contribution to Sling are cleared and copyright can safely be assigned to the ASF, I am +1 on accepting the contribution (with recognition and thanks for the hard work involved). Best Regards Ian On 14 October 2014 10:13, Dominik Süß dominik.su...@gmail.com wrote: Hi everyone, I guess people yet just had no chance to dig into the proposal since there are a lot of scenarios adressed throught this proposal. As far as I understood the API SPI the main driver for this proposal is the massive multisite scenario as described in the mentioned wiki page. Key aspects seem to be to get an aggregated context specific view for a configuration while lookup aspects (such as where to look up the configs and how inheritance is solved) are designed in a pluggable way that allows to implement application specific behavior. From offlist discussions I know that there might be some confusion around how the scoping should work so I just wanted to highlight the mentioned link [3] that might eliminate confusion around the wording (especially appliation). IMHO it would be an extremely valuable addition providing sufficient flexiblity to solve all the cases I do have in mind while establishing one unified methodology to deal with all the non osgi configuration without rewriting casespecific lookup (boilerplate) code over and over again. Best regards, Dominik [3] http://wcm.io/config/api/terminology.html On Sat, Oct 4, 2014 at 1:55 AM, Stefan Seifert sseif...@pro-vision.de wrote: p.s. url [1] is wrong - it should be https://cwiki.apache.org/confluence/x/So2uAg -Original Message- From: Stefan Seifert [mailto:sseif...@pro-vision.de] Sent: Saturday, October 04, 2014 1:54 AM To: dev@sling.apache.org Subject: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy this proposal is about context-specific configuration, that means configuration that cannot be stored as OSGi configurations. OSGi configurations are always system-wide, so they are not well-suited for storing configurations per context e.g. site, region or tenant. this is related to the multitenancy discussion on this list, see [1] for a summary of the past discussion. we've implementation a solution for this and are currently thinking about donating it to Apache Sling. a documentation of what is currently implemented is at [2]. the most relevant pages you should read are [3], [4], [5], [6]. the implementation is based on the requirements from [7], although not all that is listed on that page is implemented currently (but a good deal of it). source code is at [8], a sample application at [9]. the current implementation is targeted to a specific sling-based CMS - but besides the configuration editor and the parameter persistence provider it does not depend on the CMS API but only on the Sling APIs, being technically suited to be donated to Apache Sling. it's already published under apache license 2.0. i'm interested if there is more need in the community for solving the requirements i've listed, and the solutions we have implemented for it. and if there are other sling committers who want to take part in its development and enhancement as well. although we're using the current implementation from wcm.io already in our projects nothing of it's current architecture is carved in stone and i'm open to broaden the scope of requirements it should support. WDYT? stefan [1] https://cwiki.apache.org/confluence/x/zJBcAg [2] http://wcm.io/config/ [3] http://wcm.io/config/api/terminology.html [4] http://wcm.io/config/api/usage-api.html [5] http://wcm.io/config/api/usage-spi.html [6] http://wcm.io/config/editor/usage.html [7] https://wcm-io.atlassian.net/wiki/x/HIAH [8] https://github.com/wcm-io/wcm-io/tree/master/config [9] http://wcm.io/samples/config-sample-app/
[jira] [Created] (SLING-4047) Unable to schedule jobs using JobManager
Varun Nagpal created SLING-4047:
---
Summary: Unable to schedule jobs using JobManager
Key: SLING-4047
URL: https://issues.apache.org/jira/browse/SLING-4047
Project: Sling
Issue Type: Bug
Components: Engine
Affects Versions: Event 3.3.14
Reporter: Varun Nagpal
Priority: Blocker
Fix For: Event 3.3.16
I am unable to schedule Sling jobs using
jobManager.createJob(topic).schedule().cron(cronExp).add()
Getting the following exception in logs
{quote}
java.lang.NoClassDefFoundError: org/quartz/ValueSet
at org.quartz.CronExpression.getValue(CronExpression.java:1121)
at
org.quartz.CronExpression.storeExpressionVals(CronExpression.java:699)
at org.quartz.CronExpression.buildExpression(CronExpression.java:487)
at org.quartz.CronExpression.init(CronExpression.java:276)
at
org.apache.sling.event.impl.support.ScheduleInfoImpl.check(ScheduleInfoImpl.java:304)
at
org.apache.sling.event.impl.jobs.JobManagerImpl.addScheduledJob(JobManagerImpl.java:1597)
at
org.apache.sling.event.impl.jobs.JobBuilderImpl$ScheduleBuilderImpl.add(JobBuilderImpl.java:135)
at
org.apache.sling.event.impl.jobs.JobBuilderImpl$ScheduleBuilderImpl.add(JobBuilderImpl.java:130)
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (SLING-4047) Unable to schedule jobs using JobManager
[
https://issues.apache.org/jira/browse/SLING-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-4047:
---
Assignee: Carsten Ziegeler
Unable to schedule jobs using JobManager
Key: SLING-4047
URL: https://issues.apache.org/jira/browse/SLING-4047
Project: Sling
Issue Type: Bug
Components: Engine
Affects Versions: Event 3.3.14
Reporter: Varun Nagpal
Assignee: Carsten Ziegeler
Priority: Blocker
Fix For: Event 3.3.16
I am unable to schedule Sling jobs using
jobManager.createJob(topic).schedule().cron(cronExp).add()
Getting the following exception in logs
{quote}
java.lang.NoClassDefFoundError: org/quartz/ValueSet
at org.quartz.CronExpression.getValue(CronExpression.java:1121)
at
org.quartz.CronExpression.storeExpressionVals(CronExpression.java:699)
at org.quartz.CronExpression.buildExpression(CronExpression.java:487)
at org.quartz.CronExpression.init(CronExpression.java:276)
at
org.apache.sling.event.impl.support.ScheduleInfoImpl.check(ScheduleInfoImpl.java:304)
at
org.apache.sling.event.impl.jobs.JobManagerImpl.addScheduledJob(JobManagerImpl.java:1597)
at
org.apache.sling.event.impl.jobs.JobBuilderImpl$ScheduleBuilderImpl.add(JobBuilderImpl.java:135)
at
org.apache.sling.event.impl.jobs.JobBuilderImpl$ScheduleBuilderImpl.add(JobBuilderImpl.java:130)
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SLING-4047) Unable to schedule jobs using JobManager
[
https://issues.apache.org/jira/browse/SLING-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-4047.
-
Resolution: Fixed
Added the missing class in rev 1631723
Unable to schedule jobs using JobManager
Key: SLING-4047
URL: https://issues.apache.org/jira/browse/SLING-4047
Project: Sling
Issue Type: Bug
Components: Engine
Affects Versions: Event 3.3.14
Reporter: Varun Nagpal
Assignee: Carsten Ziegeler
Priority: Blocker
Fix For: Event 3.3.16
I am unable to schedule Sling jobs using
jobManager.createJob(topic).schedule().cron(cronExp).add()
Getting the following exception in logs
{quote}
java.lang.NoClassDefFoundError: org/quartz/ValueSet
at org.quartz.CronExpression.getValue(CronExpression.java:1121)
at
org.quartz.CronExpression.storeExpressionVals(CronExpression.java:699)
at org.quartz.CronExpression.buildExpression(CronExpression.java:487)
at org.quartz.CronExpression.init(CronExpression.java:276)
at
org.apache.sling.event.impl.support.ScheduleInfoImpl.check(ScheduleInfoImpl.java:304)
at
org.apache.sling.event.impl.jobs.JobManagerImpl.addScheduledJob(JobManagerImpl.java:1597)
at
org.apache.sling.event.impl.jobs.JobBuilderImpl$ScheduleBuilderImpl.add(JobBuilderImpl.java:135)
at
org.apache.sling.event.impl.jobs.JobBuilderImpl$ScheduleBuilderImpl.add(JobBuilderImpl.java:130)
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Jenkins build became unstable: sling-trunk-1.8 » Apache Sling Event Support #294
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/294/changes
Jenkins build is unstable: sling-trunk-1.8 #294
See https://builds.apache.org/job/sling-trunk-1.8/294/changes
Jenkins build is back to normal : sling-trunk-1.8 » Apache Sling Resource Access Security Integration Tests #294
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/294/
[jira] [Created] (SLING-4048) Avoid keeping jobs in memory
Carsten Ziegeler created SLING-4048: --- Summary: Avoid keeping jobs in memory Key: SLING-4048 URL: https://issues.apache.org/jira/browse/SLING-4048 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Event 3.3.16 Currently all jobs for a single instance are hold in memory and put into the queues. This is not optiomal, especially for a large amount of jobs. In addition it makes configuration changes, queue updates etc. more complicated. We should revert this and let a queue only pick a job from the resource tree when it has a free processing space. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4045) Lack of support for multi-facet (content and bundle) projects
[
https://issues.apache.org/jira/browse/SLING-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamil Ciecierski updated SLING-4045:
Attachment: aemtools.zip
Lack of support for multi-facet (content and bundle) projects
-
Key: SLING-4045
URL: https://issues.apache.org/jira/browse/SLING-4045
Project: Sling
Issue Type: Bug
Components: IDE
Affects Versions: Sling Eclipse IDE 1.0.2
Reporter: Kamil Ciecierski
Fix For: Sling Eclipse IDE 1.1.0
Attachments: aemtools.zip
I am working on the project which is +not based+ on
com.adobe.granite.archetype: sample-project-archetype. My project also
contains multiple module projects, but some of them contain both java and jsp
files under paths:
* java files: _module-name/src/main/java/groupName/..._
* jsp files: _module-name/src/main/aem/jcr_root/apps or
etc/app-name..._
Basically it looks like merged _core_ module and _ui.apps_ module from _AEM
Sample Multi-Module Project_/
When I configure my module as Content Project the *jsp* files are uploaded
to the server automatically, but the plugin does not respond on *java* files
changes.
When I configure my module as Bundle Project the *java* files are uploaded
to the server automatically, but the plugin does not respond on *jsp* files
changes.
I've also tested converting project to Faceted Form by doing:
* Right click on module project and choosing _Configure/Convert to Faceted
Form_
* Choosing _Content module_ and _Bundle module_ from _Project facet list_
* Clicking Apply and OK.
After this _org.eclipse.wst.common.project.facet.core.xml_ is generated under
the path: _module-name/.settings_ which looks like this:
{code}
?xml version=1.0 encoding=UTF-8?
faceted-project
installed facet=sling.bundle version=1.0/
installed facet=sling.content version=1.0/
/faceted-project
{code}
After this if I start editing *jsp* files at first then the content files are
uploaded to server but *java* uploading isn't working - I see _ JcrResult[
success:true]_ in Sling logs.
If I start editing *java* files at first then the java files are uploaded to
server, but *jsp* uploading isn't working - I see logs that _target\classes_
is uploaded_.
I conclusion, I can't make plugin to work correctly with the modules
containing both jsp and java files. I also don't know if you planned the
support for this kind of projects or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-4045) Lack of support for multi-facet (content and bundle) projects
[
https://issues.apache.org/jira/browse/SLING-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14170864#comment-14170864
]
Kamil Ciecierski commented on SLING-4045:
-
Hi [~rombert],
Sorry to keep you waiting so long, I've prepared and attached minimal sample
project containing module app-core which fits the situation I'd described.
The project can be built using {{mvn clean install}} command. Hope this can
help you better understand the issue.
Kind regards,
Kamil
Lack of support for multi-facet (content and bundle) projects
-
Key: SLING-4045
URL: https://issues.apache.org/jira/browse/SLING-4045
Project: Sling
Issue Type: Bug
Components: IDE
Affects Versions: Sling Eclipse IDE 1.0.2
Reporter: Kamil Ciecierski
Fix For: Sling Eclipse IDE 1.1.0
Attachments: aemtools.zip
I am working on the project which is +not based+ on
com.adobe.granite.archetype: sample-project-archetype. My project also
contains multiple module projects, but some of them contain both java and jsp
files under paths:
* java files: _module-name/src/main/java/groupName/..._
* jsp files: _module-name/src/main/aem/jcr_root/apps or
etc/app-name..._
Basically it looks like merged _core_ module and _ui.apps_ module from _AEM
Sample Multi-Module Project_/
When I configure my module as Content Project the *jsp* files are uploaded
to the server automatically, but the plugin does not respond on *java* files
changes.
When I configure my module as Bundle Project the *java* files are uploaded
to the server automatically, but the plugin does not respond on *jsp* files
changes.
I've also tested converting project to Faceted Form by doing:
* Right click on module project and choosing _Configure/Convert to Faceted
Form_
* Choosing _Content module_ and _Bundle module_ from _Project facet list_
* Clicking Apply and OK.
After this _org.eclipse.wst.common.project.facet.core.xml_ is generated under
the path: _module-name/.settings_ which looks like this:
{code}
?xml version=1.0 encoding=UTF-8?
faceted-project
installed facet=sling.bundle version=1.0/
installed facet=sling.content version=1.0/
/faceted-project
{code}
After this if I start editing *jsp* files at first then the content files are
uploaded to server but *java* uploading isn't working - I see _ JcrResult[
success:true]_ in Sling logs.
If I start editing *java* files at first then the java files are uploaded to
server, but *jsp* uploading isn't working - I see logs that _target\classes_
is uploaded_.
I conclusion, I can't make plugin to work correctly with the modules
containing both jsp and java files. I also don't know if you planned the
support for this kind of projects or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-4049) Errorhandling: Allow Configuration of Displaying Stacktraces/Request Progress
Dominique Jäggi created SLING-4049: -- Summary: Errorhandling: Allow Configuration of Displaying Stacktraces/Request Progress Key: SLING-4049 URL: https://issues.apache.org/jira/browse/SLING-4049 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Dominique Jäggi it should be configurable whether during error display (40x, 50x, etc) stacktraces or the request progress is displayed or not. for production systems it is undesirable to exhibit information that may allow an attacker to determine internal information such as used scripts, paths, classes, line numbers, etc. ideally this could be centrally configured, affecting both e.g. the JSP handlers (404.jsp) as well as any other facility outputting error conditions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is still unstable: sling-trunk-1.8 #295
See https://builds.apache.org/job/sling-trunk-1.8/changes
Jenkins build is still unstable: sling-trunk-1.8 » Apache Sling Event Support #295
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/changes
Jenkins build became unstable: sling-contrib-1.6 » Apache Sling Replication Integration Tests #1292
See https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/1292/
Re: [VOTE] Release Apache Sling JCR Resource Resolver 2.3.10
+1 Robert On Tue, Oct 14, 2014 at 11:40 AM, Antonio Sanso asa...@adobe.com wrote: +1 On Oct 14, 2014, at 10:27 AM, Antonio Sanso asa...@adobe.com wrote: Hi, We solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12327963 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1139/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1139 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours.
Re: Oak + Sling
On Tue, Oct 14, 2014 at 5:46 PM, TALHAOUI Mohamed m.talha...@rsd.com wrote: I am working on sling trunk, using launchpad standalone. I don’t get how to configure it to use oak with a mongoMK. IIRC Oak requires explicit configuration of the persistence backend. So in Sling for the oak runmode we ship a configuration for the SegmentNodeStoreService , see [1] . You can remove that config file and change it with a config for the DocumentNodeStore. I'm not familiar with the details, but the oak docs [2] should help. Robert [1]: https://svn.apache.org/repos/asf/sling/trunk/launchpad/builder/src/main/config/oak/ [2]: https://jackrabbit.apache.org/oak/docs/osgi_config.html
Re: FW: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy
Hi Dominik, Thanks for this link, but I'm still confused about scoping. Looking at http://wcm.io/config/api/usage-api.html, it seems like a Configuration object is essentially just a ValueMap. In a non-trivial application, it seems like you need some kind of namespace for configuration properties. For example, let's say that I'm integrating with multiple OAuth services. I thus have multiple configuration properties which are natually named 'secretKey'. Do I need to prefix these property keys with the service name, e.g. facebook.secretKey and linkedin.secretKey? I would expect that I could have a Map of Maps so I could say something like configuration.get(facebook).get(secretKey) ? How is this embodied in the API? Are facebook and linkedin applications? Justin On Tue, Oct 14, 2014 at 5:13 AM, Dominik Süß dominik.su...@gmail.com wrote: Hi everyone, I guess people yet just had no chance to dig into the proposal since there are a lot of scenarios adressed throught this proposal. As far as I understood the API SPI the main driver for this proposal is the massive multisite scenario as described in the mentioned wiki page. Key aspects seem to be to get an aggregated context specific view for a configuration while lookup aspects (such as where to look up the configs and how inheritance is solved) are designed in a pluggable way that allows to implement application specific behavior. From offlist discussions I know that there might be some confusion around how the scoping should work so I just wanted to highlight the mentioned link [3] that might eliminate confusion around the wording (especially appliation). IMHO it would be an extremely valuable addition providing sufficient flexiblity to solve all the cases I do have in mind while establishing one unified methodology to deal with all the non osgi configuration without rewriting casespecific lookup (boilerplate) code over and over again. Best regards, Dominik [3] http://wcm.io/config/api/terminology.html On Sat, Oct 4, 2014 at 1:55 AM, Stefan Seifert sseif...@pro-vision.de wrote: p.s. url [1] is wrong - it should be https://cwiki.apache.org/confluence/x/So2uAg -Original Message- From: Stefan Seifert [mailto:sseif...@pro-vision.de] Sent: Saturday, October 04, 2014 1:54 AM To: dev@sling.apache.org Subject: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy this proposal is about context-specific configuration, that means configuration that cannot be stored as OSGi configurations. OSGi configurations are always system-wide, so they are not well-suited for storing configurations per context e.g. site, region or tenant. this is related to the multitenancy discussion on this list, see [1] for a summary of the past discussion. we've implementation a solution for this and are currently thinking about donating it to Apache Sling. a documentation of what is currently implemented is at [2]. the most relevant pages you should read are [3], [4], [5], [6]. the implementation is based on the requirements from [7], although not all that is listed on that page is implemented currently (but a good deal of it). source code is at [8], a sample application at [9]. the current implementation is targeted to a specific sling-based CMS - but besides the configuration editor and the parameter persistence provider it does not depend on the CMS API but only on the Sling APIs, being technically suited to be donated to Apache Sling. it's already published under apache license 2.0. i'm interested if there is more need in the community for solving the requirements i've listed, and the solutions we have implemented for it. and if there are other sling committers who want to take part in its development and enhancement as well. although we're using the current implementation from wcm.io already in our projects nothing of it's current architecture is carved in stone and i'm open to broaden the scope of requirements it should support. WDYT? stefan [1] https://cwiki.apache.org/confluence/x/zJBcAg [2] http://wcm.io/config/ [3] http://wcm.io/config/api/terminology.html [4] http://wcm.io/config/api/usage-api.html [5] http://wcm.io/config/api/usage-spi.html [6] http://wcm.io/config/editor/usage.html [7] https://wcm-io.atlassian.net/wiki/x/HIAH [8] https://github.com/wcm-io/wcm-io/tree/master/config [9] http://wcm.io/samples/config-sample-app/
[jira] [Assigned] (SLING-3899) Access content for replication on behalf of the user that triggered the replication
[ https://issues.apache.org/jira/browse/SLING-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili reassigned SLING-3899: -- Assignee: Tommaso Teofili Access content for replication on behalf of the user that triggered the replication --- Key: SLING-3899 URL: https://issues.apache.org/jira/browse/SLING-3899 Project: Sling Issue Type: Improvement Components: Replication Reporter: Marius Petria Assignee: Tommaso Teofili Attachments: SLING-3899.diff Currently the content is accessed via an administrative session. We need to pass a ResourceResolver via all APIs to ensure that the content is accessed only be users that have the right. For rule triggered requests the actions should be done on the behalf of a replication-service-user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-3899) Access content for replication on behalf of the user that triggered the replication
[ https://issues.apache.org/jira/browse/SLING-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-3899. Resolution: Fixed applied patch in r1631780, thanks Marius! Access content for replication on behalf of the user that triggered the replication --- Key: SLING-3899 URL: https://issues.apache.org/jira/browse/SLING-3899 Project: Sling Issue Type: Improvement Components: Replication Reporter: Marius Petria Assignee: Tommaso Teofili Attachments: SLING-3899.diff Currently the content is accessed via an administrative session. We need to pass a ResourceResolver via all APIs to ensure that the content is accessed only be users that have the right. For rule triggered requests the actions should be done on the behalf of a replication-service-user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is still unstable: sling-trunk-1.8 » Apache Sling Event Support #296
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/changes
Jenkins build is unstable: sling-oak-it-1.6 #191
See https://builds.apache.org/job/sling-oak-it-1.6/191/changes
Jenkins build is unstable: sling-oak-it-1.6 » Apache Sling Launchpad Testing #191
See https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/191/changes
RE: FW: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy
hello justin. as described in [1] we currently took the design decision to have only a flat parameter list, namespacing can and has to be done inside the parameter names. the goal was to really support the full configuration in a single value map. but i'm aware this may not be sufficient, but wanted to start simple in this case. each parameter definition already has an application ID assigned as well, so technically it would not be a problem to have a parameter namespace per application/library that provides the parameters. i've not found yet a nice client API solution for this - chaining two get methods as in your example would be a solution. as the configuration API is designed to work with parameter constants holding the parameter definition [2] this chaining would only be needed if the configuration value map is accessed using string values. if using the parameter definition constant all information is in place. parameter definitions can have more metadata if a configuration editor is supported as well, see example [3] resulting in [4]. stefan [1] http://wcm.io/config/api/usage-spi.html#Preconditions_and_limitations [2] http://wcm.io/config/api/usage-spi.html#Providing_parameter_definitions [3] https://github.com/wcm-io/wcm-io/blob/master/samples/config-sample-app/src/main/java/io/wcm/samples/configsampleapp/config/Params.java [4] http://wcm.io/config/editor/usage.html -Original Message- From: justinedel...@gmail.com [mailto:justinedel...@gmail.com] On Behalf Of Justin Edelson Sent: Tuesday, October 14, 2014 4:58 PM To: dev@sling.apache.org Subject: Re: FW: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy Hi Dominik, Thanks for this link, but I'm still confused about scoping. Looking at http://wcm.io/config/api/usage-api.html, it seems like a Configuration object is essentially just a ValueMap. In a non-trivial application, it seems like you need some kind of namespace for configuration properties. For example, let's say that I'm integrating with multiple OAuth services. I thus have multiple configuration properties which are natually named 'secretKey'. Do I need to prefix these property keys with the service name, e.g. facebook.secretKey and linkedin.secretKey? I would expect that I could have a Map of Maps so I could say something like configuration.get(facebook).get(secretKey) ? How is this embodied in the API? Are facebook and linkedin applications? Justin On Tue, Oct 14, 2014 at 5:13 AM, Dominik Süß dominik.su...@gmail.com wrote: Hi everyone, I guess people yet just had no chance to dig into the proposal since there are a lot of scenarios adressed throught this proposal. As far as I understood the API SPI the main driver for this proposal is the massive multisite scenario as described in the mentioned wiki page. Key aspects seem to be to get an aggregated context specific view for a configuration while lookup aspects (such as where to look up the configs and how inheritance is solved) are designed in a pluggable way that allows to implement application specific behavior. From offlist discussions I know that there might be some confusion around how the scoping should work so I just wanted to highlight the mentioned link [3] that might eliminate confusion around the wording (especially appliation). IMHO it would be an extremely valuable addition providing sufficient flexiblity to solve all the cases I do have in mind while establishing one unified methodology to deal with all the non osgi configuration without rewriting casespecific lookup (boilerplate) code over and over again. Best regards, Dominik [3] http://wcm.io/config/api/terminology.html On Sat, Oct 4, 2014 at 1:55 AM, Stefan Seifert sseif...@pro-vision.de wrote: p.s. url [1] is wrong - it should be https://cwiki.apache.org/confluence/x/So2uAg -Original Message- From: Stefan Seifert [mailto:sseif...@pro-vision.de] Sent: Saturday, October 04, 2014 1:54 AM To: dev@sling.apache.org Subject: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy this proposal is about context-specific configuration, that means configuration that cannot be stored as OSGi configurations. OSGi configurations are always system-wide, so they are not well-suited for storing configurations per context e.g. site, region or tenant. this is related to the multitenancy discussion on this list, see [1] for a summary of the past discussion. we've implementation a solution for this and are currently thinking about donating it to Apache Sling. a documentation of what is currently implemented is at [2]. the most relevant pages you should read are [3], [4], [5], [6]. the implementation is based on the requirements from [7], although not all that is listed on that page is implemented currently (but a good deal of it). source code is at [8], a sample application at [9]. the current implementation is targeted to a specific sling-based CMS - but
[jira] [Commented] (SLING-4045) Lack of support for multi-facet (content and bundle) projects
[
https://issues.apache.org/jira/browse/SLING-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171073#comment-14171073
]
Robert Munteanu commented on SLING-4045:
Thanks, I'll try to take a look next week.
Lack of support for multi-facet (content and bundle) projects
-
Key: SLING-4045
URL: https://issues.apache.org/jira/browse/SLING-4045
Project: Sling
Issue Type: Bug
Components: IDE
Affects Versions: Sling Eclipse IDE 1.0.2
Reporter: Kamil Ciecierski
Fix For: Sling Eclipse IDE 1.1.0
Attachments: aemtools.zip
I am working on the project which is +not based+ on
com.adobe.granite.archetype: sample-project-archetype. My project also
contains multiple module projects, but some of them contain both java and jsp
files under paths:
* java files: _module-name/src/main/java/groupName/..._
* jsp files: _module-name/src/main/aem/jcr_root/apps or
etc/app-name..._
Basically it looks like merged _core_ module and _ui.apps_ module from _AEM
Sample Multi-Module Project_/
When I configure my module as Content Project the *jsp* files are uploaded
to the server automatically, but the plugin does not respond on *java* files
changes.
When I configure my module as Bundle Project the *java* files are uploaded
to the server automatically, but the plugin does not respond on *jsp* files
changes.
I've also tested converting project to Faceted Form by doing:
* Right click on module project and choosing _Configure/Convert to Faceted
Form_
* Choosing _Content module_ and _Bundle module_ from _Project facet list_
* Clicking Apply and OK.
After this _org.eclipse.wst.common.project.facet.core.xml_ is generated under
the path: _module-name/.settings_ which looks like this:
{code}
?xml version=1.0 encoding=UTF-8?
faceted-project
installed facet=sling.bundle version=1.0/
installed facet=sling.content version=1.0/
/faceted-project
{code}
After this if I start editing *jsp* files at first then the content files are
uploaded to server but *java* uploading isn't working - I see _ JcrResult[
success:true]_ in Sling logs.
If I start editing *java* files at first then the java files are uploaded to
server, but *jsp* uploading isn't working - I see logs that _target\classes_
is uploaded_.
I conclusion, I can't make plugin to work correctly with the modules
containing both jsp and java files. I also don't know if you planned the
support for this kind of projects or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[VOTE] Release Apache Sling IDE Tooling 1.0.4
Hi, We solved 30 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12327445 There are still some outstanding issues: https://issues.apache.org/jira/browse/SLING/component/12320908 The release candidate has been uploaded at https://dist.apache.org/repos/dist/dev/sling, The release artifact is the source bundle - sling-ide-tooling-1.0.4.zip - which can be used to build the project using mvn clean package The resulting binaries can be installed into an Eclipse instance from from the update site which is found at p2update/target/repository after building the project. For convenience, a pre-built update site - org.apache.sling.ide.p2update-1.0.4.zip - has also been uploaded. Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours Thanks, Robert
Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2641
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/2641/
Jenkins build became unstable: sling-trunk-1.6 #2641
See https://builds.apache.org/job/sling-trunk-1.6/2641/changes
[jira] [Created] (SLING-4050) Make it easier to run launchpad on Oak/Mongo
Bertrand Delacretaz created SLING-4050: -- Summary: Make it easier to run launchpad on Oak/Mongo Key: SLING-4050 URL: https://issues.apache.org/jira/browse/SLING-4050 Project: Sling Issue Type: Improvement Components: Launchpad Reporter: Bertrand Delacretaz It's currently too hard to reconfigure the standalone launchpad jar to run on mongo. The oak run mode (rightly) activates the SLING-3828 config but there's no easy way to replace it. The best is probably to define two oak run modes, one for TarMK and the other for Mongo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4050) Make it easier to run launchpad on Oak/Mongo
[
https://issues.apache.org/jira/browse/SLING-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-4050:
---
Attachment: SLING-4050.patch
Here's a patch that allows for starting the standalone launchpad (after
rebuilding it of course, mvn clean install in the launchpad/builder folder)
with Oak on mongo as follows:
{code}
java -Dsling.run.modes=oak -jar target/*standalone.jar
{code}
the mongo connection string and database name are set in the
org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService.cfg file,
for now you need to rebuild the launchpad jar if changing them (or change the
OSGi config via /system/console)
Make it easier to run launchpad on Oak/Mongo
Key: SLING-4050
URL: https://issues.apache.org/jira/browse/SLING-4050
Project: Sling
Issue Type: Improvement
Components: Launchpad
Reporter: Bertrand Delacretaz
Attachments: SLING-4050.patch
It's currently too hard to reconfigure the standalone launchpad jar to run on
mongo. The oak run mode (rightly) activates the SLING-3828 config but there's
no easy way to replace it.
The best is probably to define two oak run modes, one for TarMK and the other
for Mongo.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Oak + Sling
Hi, On Tue, Oct 14, 2014 at 4:57 PM, Robert Munteanu romb...@apache.org wrote: ...You can remove that config file and change it with a config for the DocumentNodeStore... You need a bit more than than unfortunately, I have created https://issues.apache.org/jira/browse/SLING-4050 to improve this, and attached a patch that can be used for now. I briefly tried running the launchpad/integration-tests but many of them fail, I haven't investigated so far. If someone tries that config, don't waste time if something does not work, let us know! -Bertrand
Build failed in Jenkins: sling-contrib-1.6 #1293
See https://builds.apache.org/job/sling-contrib-1.6/1293/changes Changes: [tommaso] SLING-3899 - applied Marius patch to add the resource resolved to all APIs -- [...truncated 4115 lines...] [INFO] Checking unresolved references to org.codehaus.mojo.signature:java15:1.0 [INFO] [INFO] --- maven-bundle-plugin:2.5.3:bundle (default-bundle) @ org.apache.sling.osgi.obr --- [WARNING] Bundle org.apache.sling:org.apache.sling.osgi.obr:bundle:2.0.0-SNAPSHOT : Split package, multiple jars provide the same package:org/osgi/service/obr Use Import/Export Package directive -split-package:=(merge-first|merge-last|error|first) to get rid of this warning Package found in [Jar:org.apache.felix.bundlerepository, Jar:org.osgi.service.obr] Class path [Jar:., Jar:commons-fileupload, Jar:commons-io, Jar:servlet-api, Jar:slf4j-api, Jar:bndlib, Jar:org.apache.felix.bundlerepository, Jar:org.osgi.service.obr, Jar:org.osgi.core, Jar:org.apache.felix.shell, Jar:kxml2, Jar:xmlpull, Jar:org.osgi.core, Jar:org.osgi.compendium, Jar:org.apache.felix.scr.annotations] [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java) @ org.apache.sling.osgi.obr --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ org.apache.sling.osgi.obr --- [INFO] Executing tasks main: [INFO] Executed tasks [WARNING] Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo [INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @ org.apache.sling.osgi.obr --- [INFO] Building jar: https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/obr/target/org.apache.sling.osgi.obr-2.0.0-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ org.apache.sling.osgi.obr --- [INFO] [INFO] --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) @ org.apache.sling.osgi.obr --- [INFO] Checking legal files in: org.apache.sling.osgi.obr-2.0.0-SNAPSHOT.jar [INFO] Checking legal files in: org.apache.sling.osgi.obr-2.0.0-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-bundle-plugin:2.5.3:baseline (baseline) @ org.apache.sling.osgi.obr --- [INFO] artifact org.apache.sling:org.apache.sling.osgi.obr: checking for updates from Nexus [INFO] artifact org.apache.sling:org.apache.sling.osgi.obr: checking for updates from central [INFO] Unable to find a previous version of the project in the repository [INFO] Not generating Baseline report as there is no previous version of the library to compare against [INFO] [INFO] --- maven-install-plugin:2.5.1:install (default-install) @ org.apache.sling.osgi.obr --- [INFO] Installing https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/obr/target/org.apache.sling.osgi.obr-2.0.0-SNAPSHOT.jar to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.osgi.obr/2.0.0-SNAPSHOT/org.apache.sling.osgi.obr-2.0.0-SNAPSHOT.jar [INFO] Installing https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/obr/pom.xml to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.osgi.obr/2.0.0-SNAPSHOT/org.apache.sling.osgi.obr-2.0.0-SNAPSHOT.pom [INFO] Installing https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/obr/target/org.apache.sling.osgi.obr-2.0.0-SNAPSHOT-sources.jar to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.osgi.obr/2.0.0-SNAPSHOT/org.apache.sling.osgi.obr-2.0.0-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-bundle-plugin:2.5.3:install (default-install) @ org.apache.sling.osgi.obr --- [INFO] Local OBR update disabled (enable with -DobrRepository) [JENKINS] Archiving disabled [INFO] [INFO] [INFO] Building Apache Sling Replication Core 0.0.1-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ org.apache.sling.replication.core --- [INFO] Deleting https://builds.apache.org/job/sling-contrib-1.6/ws/contrib-1.6/extensions/replication/core/target [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java) @ org.apache.sling.replication.core --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ org.apache.sling.replication.core --- [INFO] Executing tasks main: [INFO] Executed tasks [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ org.apache.sling.replication.core --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ org.apache.sling.replication.core --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory
Re: [VOTE] Release Apache Sling IDE Tooling 1.0.4
Am 14.10.14 um 17:31 schrieb Robert Munteanu: Hi, We solved 30 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12327445 There are still some outstanding issues: https://issues.apache.org/jira/browse/SLING/component/12320908 The release candidate has been uploaded at https://dist.apache.org/repos/dist/dev/sling, The release artifact is the source bundle - sling-ide-tooling-1.0.4.zip - which can be used to build the project using mvn clean package The resulting binaries can be installed into an Eclipse instance from from the update site which is found at p2update/target/repository after building the project. For convenience, a pre-built update site - org.apache.sling.ide.p2update-1.0.4.zip - has also been uploaded. Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours Thanks, Robert +1 Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Jenkins build is still unstable: sling-trunk-1.8 » Apache Sling Event Support #297
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/changes
Jenkins build is still unstable: sling-trunk-1.8 #297
See https://builds.apache.org/job/sling-trunk-1.8/changes
Jenkins build is back to stable : sling-trunk-1.6 #2642
See https://builds.apache.org/job/sling-trunk-1.6/2642/changes
Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2642
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/2642/
[jira] [Commented] (SLING-4049) Errorhandling: Allow Configuration of Displaying Stacktraces/Request Progress
[ https://issues.apache.org/jira/browse/SLING-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171198#comment-14171198 ] Felix Meschberger commented on SLING-4049: -- The error handling system is configurable and I would think that for a production setup custom errorhandler scripts should be created which don't expose stacktraces, request progress trackers, and system version. Errorhandling: Allow Configuration of Displaying Stacktraces/Request Progress - Key: SLING-4049 URL: https://issues.apache.org/jira/browse/SLING-4049 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Dominique Jäggi it should be configurable whether during error display (40x, 50x, etc) stacktraces or the request progress is displayed or not. for production systems it is undesirable to exhibit information that may allow an attacker to determine internal information such as used scripts, paths, classes, line numbers, etc. ideally this could be centrally configured, affecting both e.g. the JSP handlers (404.jsp) as well as any other facility outputting error conditions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is still unstable: sling-oak-it-1.6 #192
See https://builds.apache.org/job/sling-oak-it-1.6/changes
Jenkins build is still unstable: sling-oak-it-1.6 » Apache Sling Launchpad Testing #192
See https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/changes
Re: [VOTE] Release Apache Sling JCR Resource Resolver 2.3.10
+1 On Tue, Oct 14, 2014 at 10:53 AM, Robert Munteanu romb...@apache.org wrote: +1 Robert On Tue, Oct 14, 2014 at 11:40 AM, Antonio Sanso asa...@adobe.com wrote: +1 On Oct 14, 2014, at 10:27 AM, Antonio Sanso asa...@adobe.com wrote: Hi, We solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12327963 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1139/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1139 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours.
[jira] [Commented] (SLING-4049) Errorhandling: Allow Configuration of Displaying Stacktraces/Request Progress
[ https://issues.apache.org/jira/browse/SLING-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171217#comment-14171217 ] Carsten Ziegeler commented on SLING-4049: - I think what we should at least do is ensure that always the error handler with the highest service ranking is used, right now it picks up the first one it gets- A production instance could then simply deploy an error handler with a higher ranking than the one registered by the servlet ensure and it's ensure that the production specific wins Errorhandling: Allow Configuration of Displaying Stacktraces/Request Progress - Key: SLING-4049 URL: https://issues.apache.org/jira/browse/SLING-4049 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Dominique Jäggi it should be configurable whether during error display (40x, 50x, etc) stacktraces or the request progress is displayed or not. for production systems it is undesirable to exhibit information that may allow an attacker to determine internal information such as used scripts, paths, classes, line numbers, etc. ideally this could be centrally configured, affecting both e.g. the JSP handlers (404.jsp) as well as any other facility outputting error conditions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is back to stable : sling-trunk-1.8 » Apache Sling Event Support #298
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/298/
[jira] [Commented] (SLING-4049) Errorhandling: Allow Configuration of Displaying Stacktraces/Request Progress
[
https://issues.apache.org/jira/browse/SLING-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171279#comment-14171279
]
Felix Meschberger commented on SLING-4049:
--
The Sling Servlet Resolver has a default error handler servlet registered for
the virtual resource type {{sling/servlet/errorhandler/default}} registered
at the end of the search path by virtue of setting {{sling.servlet.prefix=-1}}.
Thus any error handler servlet with another path prefix, particularly ones not
setting {{sling.servlet.prefix}} at all would overwrite this. For example a
customer application could create a script (in whatever active language) or
servlet at {{/apps/sling/servlet/default}} and be sure to be called unless
there is some more specific error handler script or servlet.
Errorhandling: Allow Configuration of Displaying Stacktraces/Request Progress
-
Key: SLING-4049
URL: https://issues.apache.org/jira/browse/SLING-4049
Project: Sling
Issue Type: Improvement
Components: Servlets
Reporter: Dominique Jäggi
it should be configurable whether during error display (40x, 50x, etc)
stacktraces or the request progress is displayed or not.
for production systems it is undesirable to exhibit information that may
allow an attacker to determine internal information such as used scripts,
paths, classes, line numbers, etc.
ideally this could be centrally configured, affecting both e.g. the JSP
handlers (404.jsp) as well as any other facility outputting error conditions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: svn commit: r1631784 - /sling/trunk/launchpad/builder/src/main/bundles/list.xml
Hi We may have discussed this similarly in the Jackrabbit days, but alas … Don’t we want to go with the most recent Oak release from the 1.1.x line ? Or is it by intent to stay on the slow, stable 1.0.x line ? Regards Felix Am 14.10.2014 um 17:17 schrieb bdelacre...@apache.org: Author: bdelacretaz Date: Tue Oct 14 15:17:33 2014 New Revision: 1631784 URL: http://svn.apache.org/r1631784 Log: Upgrade to latest Oak 1.0.7 - launchpad/testing tests pass with -Dsling.run.modes=oak, except ResourceResolverProxyTest which failed with 1.0.6 already Modified: sling/trunk/launchpad/builder/src/main/bundles/list.xml Modified: sling/trunk/launchpad/builder/src/main/bundles/list.xml URL: http://svn.apache.org/viewvc/sling/trunk/launchpad/builder/src/main/bundles/list.xml?rev=1631784r1=1631783r2=1631784view=diff == --- sling/trunk/launchpad/builder/src/main/bundles/list.xml (original) +++ sling/trunk/launchpad/builder/src/main/bundles/list.xml Tue Oct 14 15:17:33 2014 @@ -555,7 +555,7 @@ bundle groupIdorg.apache.jackrabbit/groupId artifactIdoak-core/artifactId -version1.0.6/version +version1.0.7/version runModesoak/runModes /bundle !-- embedded in oak.server for now @@ -569,37 +569,37 @@ bundle groupIdorg.apache.jackrabbit/groupId artifactIdoak-commons/artifactId -version1.0.6/version +version1.0.7/version runModesoak/runModes /bundle bundle groupIdorg.apache.jackrabbit/groupId artifactIdoak-mk/artifactId -version1.0.6/version +version1.0.7/version runModesoak/runModes /bundle bundle groupIdorg.apache.jackrabbit/groupId artifactIdoak-mk-api/artifactId -version1.0.6/version +version1.0.7/version runModesoak/runModes /bundle bundle groupIdorg.apache.jackrabbit/groupId artifactIdoak-mk-remote/artifactId -version1.0.6/version +version1.0.7/version runModesoak/runModes /bundle bundle groupIdorg.apache.jackrabbit/groupId artifactIdoak-lucene/artifactId -version1.0.6/version +version1.0.7/version runModesoak/runModes /bundle bundle groupIdorg.apache.jackrabbit/groupId artifactIdoak-blob/artifactId -version1.0.6/version +version1.0.7/version runModesoak/runModes /bundle /startLevel
Jenkins build became unstable: sling-trunk-1.7 #1012
See https://builds.apache.org/job/sling-trunk-1.7/1012/changes
Re: svn commit: r1631784 - /sling/trunk/launchpad/builder/src/main/bundles/list.xml
On Tue, Oct 14, 2014 at 8:17 PM, Felix Meschberger fmesc...@adobe.com wrote: ...Don’t we want to go with the most recent Oak release from the 1.1.x line ? Or is it by intent to stay on the slow, stable 1.0.x line ?... I'm not sure how much work keeping up with the 1.1.x line entails - I'll give it a try when I find some time. -Bertrand
Re: svn commit: r1631784 - /sling/trunk/launchpad/builder/src/main/bundles/list.xml
On Tue, Oct 14, 2014 at 9:17 PM, Felix Meschberger fmesc...@adobe.com wrote: Hi We may have discussed this similarly in the Jackrabbit days, but alas … Don’t we want to go with the most recent Oak release from the 1.1.x line ? Or is it by intent to stay on the slow, stable 1.0.x line ? I think we should first make sure that Sling works well with stable Oak first. Robert
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #1012
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/1012/
Re: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy
I see 3 problems: - allowing to hook in a custom lookup strategy and not defining a clear lookup content model (too much magic in such things is bad, it should be obvious by just browsing the JCR, just as with resource types) - the idea of putting configurations itself under /content; configs have a different management lifecycle and ACLs - complexity of the API, Parameter generics just replicate the valuemap, but in what seems to me like an overengineered fashion one that shields too much from the power of JCR, which might lead to have people invent custom string formats instead of using JCR properties; in reality, 80% of properties are strings, 10% each are boolean or integers (subjective experience stats TM :)) Cheers, Alex On 03.10.2014, at 16:53, Stefan Seifert sseif...@pro-vision.de wrote: this proposal is about context-specific configuration, that means configuration that cannot be stored as OSGi configurations. OSGi configurations are always system-wide, so they are not well-suited for storing configurations per context e.g. site, region or tenant. this is related to the multitenancy discussion on this list, see [1] for a summary of the past discussion. we've implementation a solution for this and are currently thinking about donating it to Apache Sling. a documentation of what is currently implemented is at [2]. the most relevant pages you should read are [3], [4], [5], [6]. the implementation is based on the requirements from [7], although not all that is listed on that page is implemented currently (but a good deal of it). source code is at [8], a sample application at [9]. the current implementation is targeted to a specific sling-based CMS - but besides the configuration editor and the parameter persistence provider it does not depend on the CMS API but only on the Sling APIs, being technically suited to be donated to Apache Sling. it's already published under apache license 2.0. i'm interested if there is more need in the community for solving the requirements i've listed, and the solutions we have implemented for it. and if there are other sling committers who want to take part in its development and enhancement as well. although we're using the current implementation from wcm.io already in our projects nothing of it's current architecture is carved in stone and i'm open to broaden the scope of requirements it should support. WDYT? stefan [1] https://cwiki.apache.org/confluence/x/zJBcAg [2] http://wcm.io/config/ [3] http://wcm.io/config/api/terminology.html [4] http://wcm.io/config/api/usage-api.html [5] http://wcm.io/config/api/usage-spi.html [6] http://wcm.io/config/editor/usage.html [7] https://wcm-io.atlassian.net/wiki/x/HIAH [8] https://github.com/wcm-io/wcm-io/tree/master/config [9] http://wcm.io/samples/config-sample-app/
[jira] [Created] (SLING-4051) Warning about unset version when using replication.next
Laurie byrum created SLING-4051:
---
Summary: Warning about unset version when using replication.next
Key: SLING-4051
URL: https://issues.apache.org/jira/browse/SLING-4051
Project: Sling
Issue Type: Bug
Components: Replication
Reporter: Laurie byrum
I use the following code to replicate:
@Reference(target = (name=blah-reverse), policy = ReferencePolicy.DYNAMIC,
cardinality = ReferenceCardinality.OPTIONAL_UNARY)
ReplicationAgent replicationAgent;
private void reverseReplicate(String path) throws AgentReplicationException
{
if (replicationAgent != null) {
ReplicationRequest replicationRequest = new ReplicationRequest(0,
ReplicationActionType.ADD, path);
replicationAgent.execute(replicationRequest);
}
}
I get the following warning in my log when that happens:
14.10.2014 14:13:54.544 *WARN* [0:0:0:0:0:0:0:1 [1413321186378] POST blah
HTTP/1.1] org.apache.jackrabbit.vault.packaging.impl.PackagePropertiesImpl
Package does not specify a version. setting to ''
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: FW: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy
Hi Stefan, Thanks for clarifying. So is it accurate to say that your expectation that the *vast* majority of clients to use a strongly-typed Parameter object rather than doing a simple String lookup? To me, this seems very heavyweight, but maybe I am being short sighted (or lazy). But on the other hand, if you expect clients to use Paramter objects, why support String lookup at all? Justin On Tue, Oct 14, 2014 at 11:24 AM, Stefan Seifert sseif...@pro-vision.de wrote: hello justin. as described in [1] we currently took the design decision to have only a flat parameter list, namespacing can and has to be done inside the parameter names. the goal was to really support the full configuration in a single value map. but i'm aware this may not be sufficient, but wanted to start simple in this case. each parameter definition already has an application ID assigned as well, so technically it would not be a problem to have a parameter namespace per application/library that provides the parameters. i've not found yet a nice client API solution for this - chaining two get methods as in your example would be a solution. as the configuration API is designed to work with parameter constants holding the parameter definition [2] this chaining would only be needed if the configuration value map is accessed using string values. if using the parameter definition constant all information is in place. parameter definitions can have more metadata if a configuration editor is supported as well, see example [3] resulting in [4]. stefan [1] http://wcm.io/config/api/usage-spi.html#Preconditions_and_limitations [2] http://wcm.io/config/api/usage-spi.html#Providing_parameter_definitions [3] https://github.com/wcm-io/wcm-io/blob/master/samples/config-sample-app/src/main/java/io/wcm/samples/configsampleapp/config/Params.java [4] http://wcm.io/config/editor/usage.html -Original Message- From: justinedel...@gmail.com [mailto:justinedel...@gmail.com] On Behalf Of Justin Edelson Sent: Tuesday, October 14, 2014 4:58 PM To: dev@sling.apache.org Subject: Re: FW: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy Hi Dominik, Thanks for this link, but I'm still confused about scoping. Looking at http://wcm.io/config/api/usage-api.html, it seems like a Configuration object is essentially just a ValueMap. In a non-trivial application, it seems like you need some kind of namespace for configuration properties. For example, let's say that I'm integrating with multiple OAuth services. I thus have multiple configuration properties which are natually named 'secretKey'. Do I need to prefix these property keys with the service name, e.g. facebook.secretKey and linkedin.secretKey? I would expect that I could have a Map of Maps so I could say something like configuration.get(facebook).get(secretKey) ? How is this embodied in the API? Are facebook and linkedin applications? Justin On Tue, Oct 14, 2014 at 5:13 AM, Dominik Süß dominik.su...@gmail.com wrote: Hi everyone, I guess people yet just had no chance to dig into the proposal since there are a lot of scenarios adressed throught this proposal. As far as I understood the API SPI the main driver for this proposal is the massive multisite scenario as described in the mentioned wiki page. Key aspects seem to be to get an aggregated context specific view for a configuration while lookup aspects (such as where to look up the configs and how inheritance is solved) are designed in a pluggable way that allows to implement application specific behavior. From offlist discussions I know that there might be some confusion around how the scoping should work so I just wanted to highlight the mentioned link [3] that might eliminate confusion around the wording (especially appliation). IMHO it would be an extremely valuable addition providing sufficient flexiblity to solve all the cases I do have in mind while establishing one unified methodology to deal with all the non osgi configuration without rewriting casespecific lookup (boilerplate) code over and over again. Best regards, Dominik [3] http://wcm.io/config/api/terminology.html On Sat, Oct 4, 2014 at 1:55 AM, Stefan Seifert sseif...@pro-vision.de wrote: p.s. url [1] is wrong - it should be https://cwiki.apache.org/confluence/x/So2uAg -Original Message- From: Stefan Seifert [mailto:sseif...@pro-vision.de] Sent: Saturday, October 04, 2014 1:54 AM To: dev@sling.apache.org Subject: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy this proposal is about context-specific configuration, that means configuration that cannot be stored as OSGi configurations. OSGi configurations are always system-wide, so they are not well-suited for storing configurations per context e.g. site, region or tenant. this is related to the multitenancy discussion on this list, see [1] for a summary of the past discussion. we've
RE: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy
hello alex. -Original Message- From: Alexander Klimetschek [mailto:aklim...@adobe.com] Sent: Tuesday, October 14, 2014 10:13 PM To: dev@sling.apache.org Subject: Re: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy I see 3 problems: - allowing to hook in a custom lookup strategy and not defining a clear lookup content model (too much magic in such things is bad, it should be obvious by just browsing the JCR, just as with resource types) - the idea of putting configurations itself under /content; configs have a different management lifecycle and ACLs to shorten a discussion i've written a persistence provider that stores exactly you want it - in a shadow structure below /conf. this was only a small deviation from the existing persistence provider, documentation of ConfStructurePersistenceProvider at [1], impl at [2] still i see a need for a pluggable architecture at this point. starting on the green you are right. but we have already thousands of sling-based applications out there. and because no standard for context-specific configs existed in the past, every dev team has invented their own strategy having tens of thousands of sites with existing configuration. supporting them only needs an implementation of a custom PeristenceProvider, new configuration can be stored at /conf (the implementation supports multiple persistence providers for reading). and not all configuration parameters are so sensitive that they cannot be stored together with content. we have configuration parameters like list of news category names or parameters to tweak the style or behavior of some marketing features on the site. they should be allowed to be configured by authors and are more or less part of the content. but let's not start philosophical discussions on that. - complexity of the API, Parameter generics just replicate the valuemap, but in what seems to me like an overengineered fashion one that shields too much from the power of JCR, which might lead to have people invent custom string formats instead of using JCR properties; in reality, 80% of properties are strings, 10% each are boolean or integers (subjective experience stats TM :)) the Parameter generics only supports types supported by JCR (single and multi-valued), and a map which is stored in a string array internally. see more on this topic in my answer to justins mail. [1] http://wcm.io/config/core/persistence-providers.html [2] https://github.com/wcm-io/wcm-io/blob/master/config/core/src/main/java/io/wcm/config/core/persistence/impl/ConfStructurePersistenceProvider.java
RE: FW: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy
hello justin. yes, this is my expectation for the java code. if you only provide a string-based access to configuration parameter every developer will start to create a NameConstants class to define the much-used property names (or you will provide such a class as part of your applications API). then the developer has to remember which type belongs to which string constant. then you have to find a way where you define the default values of a parameter, and describe its edit mode capabilities. all this is covered by building a structured parameter definition. but yes, it started as a simple helper class with constants to easy access all existing parameters of an application. as a bonus there is an abstract implementation of the ParameterProvider interface which just reads the static fields of such a class and provides the defined parameters as OSGi service to the config infrastructure. you still need the string-based (or map-based) access for usecases like sightly templates where it is not so easy or uncommon to use constants for accessing map values. but in our experience the parameters are used in most cases in the java business logic behind the presentation layer, not in the presentation layer (scripts) itself. and of course the lazy developers can use this access at well in java code... stefan -Original Message- From: justinedel...@gmail.com [mailto:justinedel...@gmail.com] On Behalf Of Justin Edelson Sent: Tuesday, October 14, 2014 11:32 PM To: dev@sling.apache.org Subject: Re: FW: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy Hi Stefan, Thanks for clarifying. So is it accurate to say that your expectation that the *vast* majority of clients to use a strongly-typed Parameter object rather than doing a simple String lookup? To me, this seems very heavyweight, but maybe I am being short sighted (or lazy). But on the other hand, if you expect clients to use Paramter objects, why support String lookup at all? Justin
Re: FW: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy
Hi Stefan, To me, this sounds a bit schizophrenic - you're saying that the preferred way is to use a Parameter object, but that we need to support String-based lookup. And I'm not actually sure what which type belongs to which string constant actually means. Above all, this seems to create a confusing API. Since the expectation is that String-based lookups will work consistently, there's effectively no way to use the extra data within the Parameter object inside the lookup mechanism. For example, you mentioned the idea of using the application ID from the Parameter object as a way of expressing scope. But of course, this can't actually happen because there would be no way to do this with just Strings. I also personally find the setting of the default at the Parameter level a bit confusing. IME, defaults are *very* context-sensitive, whereas (if I understand) the Parameter objects are meant to be used across-contexts. All of which is to say that I would rather see the API have a clean separation between configuration lookup (which can be done purely with Strings) and Parameter definition. Or, to put in AEM terms, separate the functionality common to author publish (configuration lookup) from the author-side functionality (parameter defintion which leads to editing). At this point, Configuration just becomes MapString, ValueMap. The keys are are the application IDs and the resulting maps are the actual configurations for that application (which frankly I'd rather see called 'component' but that's neither here nor there). The only deviation I'd suggest from normal Map behavior is that config.get(non-existing-application-id) should return an empty ValueMap. This would allow you to do null-safe chaining, e.g. config.get(foo).get(bar) could return null, but never throw an NPE (unless config itself is null) If developers choose to adopt the Parameter objects, that's fine. Perhaps we even should have a utility method ConfigurationUtils.get(config, param) which calls config.get(param.getApplicationId()).get(param.getName(), param.getType()) But this is an optional step and the use of Parameter objects isn't implied by the Configuration API. Regards, Justin On Tue, Oct 14, 2014 at 6:58 PM, Stefan Seifert sseif...@pro-vision.de wrote: hello justin. yes, this is my expectation for the java code. if you only provide a string-based access to configuration parameter every developer will start to create a NameConstants class to define the much-used property names (or you will provide such a class as part of your applications API). then the developer has to remember which type belongs to which string constant. then you have to find a way where you define the default values of a parameter, and describe its edit mode capabilities. all this is covered by building a structured parameter definition. but yes, it started as a simple helper class with constants to easy access all existing parameters of an application. as a bonus there is an abstract implementation of the ParameterProvider interface which just reads the static fields of such a class and provides the defined parameters as OSGi service to the config infrastructure. you still need the string-based (or map-based) access for usecases like sightly templates where it is not so easy or uncommon to use constants for accessing map values. but in our experience the parameters are used in most cases in the java business logic behind the presentation layer, not in the presentation layer (scripts) itself. and of course the lazy developers can use this access at well in java code... stefan -Original Message- From: justinedel...@gmail.com [mailto:justinedel...@gmail.com] On Behalf Of Justin Edelson Sent: Tuesday, October 14, 2014 11:32 PM To: dev@sling.apache.org Subject: Re: FW: [PROPOSAL] Context-specific configuration for Apache Sling, Multitenancy Hi Stefan, Thanks for clarifying. So is it accurate to say that your expectation that the *vast* majority of clients to use a strongly-typed Parameter object rather than doing a simple String lookup? To me, this seems very heavyweight, but maybe I am being short sighted (or lazy). But on the other hand, if you expect clients to use Paramter objects, why support String lookup at all? Justin
