Re: Sling Web Resource Optimizers
Hi Bob, On Tue, Mar 26, 2013 at 5:03 AM, Bob Paulin b...@bobpaulin.com wrote: ...Sling supports numerous server side scripting languages for working with JCR but I'm curious if Sling might ever be intended to support front end scripting languages. Projects such as wro4j (http://alexo.github.com/wro4j) support these things but don't have the convenience of the JCR to store compiled resources I like the idea, and your CoffeeScript example demonstrates it very nicely. Having such tings in our /contrib source code folder would be great IMO, as long as each module has meaningful automated tests they should be easy to maintain. There's a set of common logic and requirements for this server-side compiling of client-side code, at least on the caching side, and that can probably be generalized. -Bertrand
Re: Sling Web Resource Optimizers
On Tue, Mar 26, 2013 at 6:46 AM, Lukas Eder lukas.e...@gmail.com wrote: ...maybe, Sling could host popular third-party contributions... Definitely - we already have /contrib for that. For me an important criterion for accepting such contributions is their sustainability. Code that's well tested and easy to understand helps, and we're certainly open to voting in authors of such code in as committers, even if we don't expect them to hack in the core too much initially. -Bertrand
[jira] [Updated] (SLING-2795) Apache Solr backend for Apache Sling
[ https://issues.apache.org/jira/browse/SLING-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-2795: --- Description: This is a proposal for GSoC 2013: create a Java/OSGi backend that allows Sling to use an Apache Solr server for content storage. Interested students are welcome to get in touch with the Sling community via its mailing lists to discuss the project, see http://sling.apache.org/project-information.html#mailing-lists Recent additions to the Sling resource management support using any existing content store as a backend for content storage, and creating an example ResourceProvider [1] that uses Apache Solr as its backend would be a good example of that. This support for arbitrary content stores is relatively new in Sling, so we might discover some missing features or incomplete implementations along the way. The student will need to interact closely with the Sling community to discuss any improvements needed to reach this project's goals. As Solr is probably not well suited for storing large binaries, a hybrid store will probably be needed, where small data items are stored directly in Solr and large, binary values stored on a filesystem-based structure like the Jackrabbit DataStore. Advanced Java skills are required, as is good knowledge of HTTP protocols and clients and knowledge of automated testing tools to be able to validate the results. The following pages give more information about GSoC @apache: * http://www.google-melange.com/gsoc/homepage/google/gsoc2013 * http://community.apache.org/gsoc.html * http://s.apache.org/gsoc2013ideas [1] http://sling.apache.org/site/resources.html was: This is a proposal for GSoC 2013: create a Java/OSGi backend that allows Sling to use an Apache Solr server for content storage. Recent additions to the Sling resource management support using any existing content store as a backend for content storage, and creating an example ResourceProvider [1] that uses Apache Solr as its backend would be a good example of that. This support for arbitrary content stores is relatively new in Sling, so we might discover some missing features or incomplete implementations along the way. The student will need to interact closely with the Sling community to discuss any improvements needed to reach this project's goals. As Solr is probably not well suited for storing large binaries, a hybrid store will probably be needed, where small data items are stored directly in Solr and large, binary values stored on a filesystem-based structure like the Jackrabbit DataStore. Advanced Java skills are required, as is good knowledge of HTTP protocols and clients and knowledge of automated testing tools to be able to validate the results. The following pages give more information about GSoC @apache: * http://www.google-melange.com/gsoc/homepage/google/gsoc2013 * http://community.apache.org/gsoc.html * http://s.apache.org/gsoc2013ideas [1] http://sling.apache.org/site/resources.html Apache Solr backend for Apache Sling Key: SLING-2795 URL: https://issues.apache.org/jira/browse/SLING-2795 Project: Sling Issue Type: Bug Components: Samples Reporter: Bertrand Delacretaz Labels: gsoc, gsoc2013, java, osgi, sling, solr This is a proposal for GSoC 2013: create a Java/OSGi backend that allows Sling to use an Apache Solr server for content storage. Interested students are welcome to get in touch with the Sling community via its mailing lists to discuss the project, see http://sling.apache.org/project-information.html#mailing-lists Recent additions to the Sling resource management support using any existing content store as a backend for content storage, and creating an example ResourceProvider [1] that uses Apache Solr as its backend would be a good example of that. This support for arbitrary content stores is relatively new in Sling, so we might discover some missing features or incomplete implementations along the way. The student will need to interact closely with the Sling community to discuss any improvements needed to reach this project's goals. As Solr is probably not well suited for storing large binaries, a hybrid store will probably be needed, where small data items are stored directly in Solr and large, binary values stored on a filesystem-based structure like the Jackrabbit DataStore. Advanced Java skills are required, as is good knowledge of HTTP protocols and clients and knowledge of automated testing tools to be able to validate the results. The following pages give more information about GSoC @apache: * http://www.google-melange.com/gsoc/homepage/google/gsoc2013 * http://community.apache.org/gsoc.html * http://s.apache.org/gsoc2013ideas [1]
[jira] [Updated] (SLING-1437) GSoC project: create more unit and integration tests for Sling and expand test coverage information
[ https://issues.apache.org/jira/browse/SLING-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-1437: --- Summary: GSoC project: create more unit and integration tests for Sling and expand test coverage information (was: GSoC 2010: create more unit and integration tests for Sling) GSoC project: create more unit and integration tests for Sling and expand test coverage information --- Key: SLING-1437 URL: https://issues.apache.org/jira/browse/SLING-1437 Project: Sling Issue Type: Task Components: Testing Reporter: Bertrand Delacretaz Labels: gsoc, gsoc2010sling, gsoc2013, java, mentor, testing Sling already has fairly good test coverage, but there's always room for improvement. The goal of this Google Summer of Code project is to create more unit and integration tests for Sling. Interested students are welcome to get in touch with the Sling community via its mailing lists to discuss the project, see http://sling.apache.org/project-information.html#mailing-lists The student will have to get familiar with the Sling codebase, identify areas where tests are missing, write unit and integration tests to improve the test coverage, and submit the result as patches that the Sling committers can verify and hopefully apply. Another aspect is measuring and reporting (automatically, ideally as part of our Hudson builds) the actual test coverage - that's easy for unit tests which run as part of the module builds, but seems to be harder for integration tests which run in a separate JVM than the one that executes tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-1437) GSoC 2010: create more unit and integration tests for Sling
[ https://issues.apache.org/jira/browse/SLING-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-1437: --- Description: Sling already has fairly good test coverage, but there's always room for improvement. The goal of this Google Summer of Code project is to create more unit and integration tests for Sling. Interested students are welcome to get in touch with the Sling community via its mailing lists to discuss the project, see http://sling.apache.org/project-information.html#mailing-lists The student will have to get familiar with the Sling codebase, identify areas where tests are missing, write unit and integration tests to improve the test coverage, and submit the result as patches that the Sling committers can verify and hopefully apply. Another aspect is measuring and reporting (automatically, ideally as part of our Hudson builds) the actual test coverage - that's easy for unit tests which run as part of the module builds, but seems to be harder for integration tests which run in a separate JVM than the one that executes tests. was: Sling already has fairly good test coverage, but there's always room for improvement. The goal of this Google Summer of Code project is to create more unit and integration tests for Sling. The student will have to get familiar with the Sling codebase, identify areas where tests are missing, write unit and integration tests to improve the test coverage, and submit the result as patches that the Sling committers can verify and hopefully apply. Another aspect is measuring and reporting (automatically, ideally as part of our Hudson builds) the actual test coverage - that's easy for unit tests which run as part of the module builds, but seems to be harder for integration tests which run in a separate JVM than the one that executes tests. See http://tinyurl.com/asfgsoc for the full list of GSoC 2010 projects at the ASF, and http://community.apache.org/gsoc for general GSoC information. GSoC 2010: create more unit and integration tests for Sling --- Key: SLING-1437 URL: https://issues.apache.org/jira/browse/SLING-1437 Project: Sling Issue Type: Task Components: Testing Reporter: Bertrand Delacretaz Labels: gsoc, gsoc2010sling, gsoc2013, java, mentor, testing Sling already has fairly good test coverage, but there's always room for improvement. The goal of this Google Summer of Code project is to create more unit and integration tests for Sling. Interested students are welcome to get in touch with the Sling community via its mailing lists to discuss the project, see http://sling.apache.org/project-information.html#mailing-lists The student will have to get familiar with the Sling codebase, identify areas where tests are missing, write unit and integration tests to improve the test coverage, and submit the result as patches that the Sling committers can verify and hopefully apply. Another aspect is measuring and reporting (automatically, ideally as part of our Hudson builds) the actual test coverage - that's easy for unit tests which run as part of the module builds, but seems to be harder for integration tests which run in a separate JVM than the one that executes tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Feedback on the current ResourceAccessSecurity API
Hi Mike, Thanks for your replies - as usual I'm a stickler for names...I think good naming helps a lot in making APIs understandable. On Mon, Mar 25, 2013 at 8:14 PM, Mike Müller mike...@mysign.ch wrote: ... Bertrand wrote: // Calling that canRead would be more consistent with other names public Resource checkReadPermission( Resource resource ); I choosed another naming because canCreate, canDelete, etc. returns a boolean, but checkReadPermission returns a Resource. Maybe it's more visible with a different methode name. What's the goal of returning a Resource? Is one expected to use the returned one instead of the one that's passed into the method? If yes I'd suggest getReadableResource(Resource). ... // Having to extract username as a String feels a bit funny - maybe // you need an opaque ResourceCredentials object... ...At this time ResourceResolver has a method named getUserID() which returns a String... As Carsten says, passing the ResourceResolver in such cases is probably the best way to provide context. ... Maybe canSetValue // can cover both cases, by first checking if the value exists.. Yes good point, we could make this easier with just one method. ok ... public String sanitizeQuery( String query, String language, String user ) throws AccessSecurityException; ...Think of a mongodb like persistence layer with millions of resources saved. No we've got a user which has access to only 10 resources. Now he makes a query like SELECT * FROM allresources (just as an example in an SQL like language). This query would now return millions of resources and every resource in the returning list would be checked by ResourceAccessSecurity#canRead. With sanitizeQuery the query could be injected with some limiting statements like SELECT * FROM allresources WHERE owner=userid. In this case a list of only 10 resources would be returned. Nevertheless every returned resource would be checked by canRead, but the performance would be much much better than in the first case Could this be done by having the ResourceProvider implement a QueryOptimizer API instead? The ResourceResolver can then check if the provider implements this and call that method in that case. It doesn't feel right to me to mix that method with security stuff as it has nothing to do with security AFAICS. -Bertrand
Interested in participating to GSoC 2013 with Sling
Hi, I am a student from the Faculty of Engineering, Universtiy of Moratuwa, Sri Lanka who is currently in my 4th year (final year) majoring in Computer Science and Engineering. I was a GSoC participant in 2012 for Creative Commons and was able to successfully complete the assigned project[1]. I would like to contribute to Sling in GSoC 2013. I did my 6 months of internship in WSO2[2], which is a middleware company who's products are entirely built on OSGI. There, I was part of a test hackathon which was carried out for around 2 months for one of their products, named WSO2 Governance Registry(GReg) [3]. There I wrote various integration tests for the product. Few of my test cases included testing JCR related functionality of GReg, so I have an understanding on what is JCR and how it can be used. Also I have used JUnit in some of my project work that I carried out in the university. So I believe that I have the ability to work on both the ideas listed in [4], and [5] (I wanted to do [5] even in GSoC 2012, but somehow missed the opportunity). To be honest, I've never used Sling nor Solr. So I know that i might not seem the best candidate for [4]. But after taking a look at both Sling and Solr, I have the confidence that I'll be able to complete the project. I honestly believe that I have enough knowledge to complete [5]. My LinkedIn profile can be accessed via [6]. That will list most of the important activities carried out by me and the recommendations that I've got for my work in WSO2 (you might need to log in to LinkedIn). I'm pretty sure that with proper guidance I can complete either [4] or [5]. Please give me any advice, guidance you'd like to extend. [1]. http://code.creativecommons.org/viewgit/cc.libreoffice.git/ [2]. http://wso2.com/ [3]. http://wso2.com/products/governance-registry/ [4]. https://issues.apache.org/jira/browse/SLING-2795 [5]. https://issues.apache.org/jira/browse/SLING-1437 [6]. http://www.linkedin.com/pub/ishan-somasiri/25/bab/951 -- Ishan Thilina Somasiri - 3rd year undergraduate, Computer Science and Engineering Department, University of Moratuwa. - Ishan's info: www.ishans.info මගේ සටහන්: www.siblog.ishans.info Ishan's way: www.blog.ishans.info -
[jira] [Created] (SLING-2798) Apache Cassandra backing for Sling: GSoC2013 Project
Ian Boston created SLING-2798: - Summary: Apache Cassandra backing for Sling: GSoC2013 Project Key: SLING-2798 URL: https://issues.apache.org/jira/browse/SLING-2798 Project: Sling Issue Type: Bug Components: Samples Reporter: Ian Boston This is a proposal for GSoC2013: create an Resource Provider that allows resources stored in Apache Cassandra to be exposed as Sling Resources. Resources[1] are the basic building blocks of Sling. ResourceProviders[2] allow data sources to be added to the core ResourceProvider within Sling allowing those data sources to provide Resources at pre-determined locations in the resource tree. To put it in more familiar terms, implementing and adding a Resource provider is like mounting or mapping a network drive. A more recent addition to the facilities available in Sling include updatable ResourceProviders. Apache Cassandra[3] is a column database (NoSQL) which aims to provide linear scalability to web scale. It is used by many of the best known names on the internet. Initially this will provide read only resource access, but if there is time in the project will allow read write access to a cassandra cluster. Advanced Java skills are required, some knowledge of OSGi, Sling, Cassandra will be valuable. The following pages give more information about GSoC @apache: * http://www.google-melange.com/gsoc/homepage/google/gsoc2013 * http://community.apache.org/gsoc.html * http://s.apache.org/gsoc2013ideas 1 http://sling.apache.org/site/resources.html 2 http://sling.apache.org/apidocs/sling6/org/apache/sling/api/resource/ResourceProvider.html 3 http://cassandra.apache.org/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (SLING-2799) Elastic Search backend for Sling: GSoC2013
Ian Boston created SLING-2799: - Summary: Elastic Search backend for Sling: GSoC2013 Key: SLING-2799 URL: https://issues.apache.org/jira/browse/SLING-2799 Project: Sling Issue Type: Bug Components: Samples Reporter: Ian Boston This is a proposal for GSoC2013: create an Resource Provider that allows resources stored in Elastic Search to be exposed as Sling Resources. Resources[1] are the basic building blocks of Sling. ResourceProviders[2] allow data sources to be added to the core ResourceProvider within Sling allowing those data sources to provide Resources at pre-determined locations in the resource tree. To put it in more familiar terms, implementing and adding a Resource provider is like mounting or mapping a network drive. A more recent addition to the facilities available in Sling include updatable ResourceProviders. Elastic Search[3] is a elastically scalable search engine based on Lucene that has NoSQL like storage capabilities. Although written in Java, and used by many Java applications, it is used by a multitude of scripting communities (Python, Ruby, Php) as it exposes a RESTfull Json interface. Its NoSQL like capabilities are supported by the ability to index in real time over multiple shards and replicas. Notable users of Elastic Search include Wordpress, GitHub, FourSquare, Sony and many others. Initially this will provide read only resource access, but if there is time in the project will allow read write access to a Elastic Search cluster. Advanced Java skills are required, some knowledge of OSGi, Sling, Elastic Search will be valuable as will a detailed knowledge of HTTP and RESTfull architectures. The following pages give more information about GSoC @apache: * http://www.google-melange.com/gsoc/homepage/google/gsoc2013 * http://community.apache.org/gsoc.html * http://s.apache.org/gsoc2013ideas 1 http://sling.apache.org/site/resources.html 2 http://sling.apache.org/apidocs/sling6/org/apache/sling/api/resource/ResourceProvider.html 3 http://www.elasticsearch.org/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (SLING-2800) Test and Fix Apache Oak Integration with Sling: GSoC2013
Ian Boston created SLING-2800: - Summary: Test and Fix Apache Oak Integration with Sling: GSoC2013 Key: SLING-2800 URL: https://issues.apache.org/jira/browse/SLING-2800 Project: Sling Issue Type: Bug Components: JCR Reporter: Ian Boston This is a proposal for GSoC2013: Apache Oak[1] is creating the next version of Apache Jackrabbit. It will be highly scalable, capable of web scale deployment. Apache Sling will use Apache Oak as its central repository, however, this work is very new. The taks of making Sling available on Oak[2] is almost complete, however the task of integration testing has not been started. Within Sling there are a large number of integration tests that verify the operation of Sling. This GSoC project is to work with Apache Sling ontop of Apache Oak and fix the integration tests providing patches to Apache Sling and potentially to Apache Oak. Who ever gets accepted to work on this project will learn an immense amount about the internals of both Sling and Oak and, assuming there are bugs will provide an extremely valuable contribution Sling and potentially Oak. There is some risk in applying for this project, as Sling may work perfectly ontop of Oak first time, although I think this is unlikely. Advanced Java skills are required, knowledge of Integration testing, JUnit and OSGi are also required. Some knowledge of JCR, Jackrabbit, Sling and Oak will be advantageous. The following pages give more information about GSoC @apache: * http://www.google-melange.com/gsoc/homepage/google/gsoc2013 * http://community.apache.org/gsoc.html * http://s.apache.org/gsoc2013ideas 1 http://jackrabbit.apache.org/oak/ 2 SLING-2788 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: GSoC 2013: there's still space for ideas
On 26 March 2013 21:06, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Sat, Mar 23, 2013 at 10:25 PM, Ian Boston i...@tfd.co.uk wrote: ...Is there room for other updatable resource providers as a GSoC project. I am thinking of perhapse, Cassandra and/or Elastic Search Hi, I have created 3 issues following your template, tagged in the same way. I will be happy to mentor and help, having done GSoC a couple of times in the past. If you think there is too much overlap please just shout. Also, I've not done a GSoC inside Apache before. Whats the process, is there central co-ordination? I saw some traffic one of the central lists about items, and noticed a potential applicant showing interest. Ian https://issues.apache.org/jira/browse/SLING-2798 https://issues.apache.org/jira/browse/SLING-2799 https://issues.apache.org/jira/browse/SLING-2800 Definitely - it's hard to estimate out how much time a student would need for that, so additional providers can either be extensions to SLING-2795, or projects on their own. ...If a really strong GSoC candidate comes up, and the suite of integration test have failures running on an Oak repository, fixing those one by one might be a benefit to both Sling and Oak... Agreed. -Bertrand
not able to run standalone jar file (6) from download site
hi, I downloaded the sling standalone jar file from the website and tried to run it with java 7. I also dropped down to Java 6, that makes everything work fine - not sure if this is a known issue or if I should file a defect. Ruben ( http://sling.apache.org/downloads.cgi ) java -jar org.apache.sling.launchpad-6-standalone.jar start 26.03.2013 15:09:01.453 *INFO* [main] Setting sling.home=sling (default) 26.03.2013 15:09:01.454 *INFO* [Sling Control Listener@hw8win/192.168.56.1:63000] Sling Control Server started 26.03.2013 15:09:01.454 *INFO* [main] Starting Sling in sling (C:\projects\sling\sling) 26.03.2013 15:09:01.462 *INFO* [main] Checking launcher JAR in folder sling 26.03.2013 15:09:01.470 *INFO* [main] Installing new launcher: jar:file:/C:/projects/sling/org.apache.sling.launchpad-6-standalone.jar!/resources/org.apache.sli ng.launchpad.base.jar, 2.3.0 (org.apache.sling.launchpad.base.jar.1364335741470) 26.03.2013 15:09:01.472 *INFO* [main] Loading launcher class org.apache.sling.launchpad.base.app.MainDelegate from org.apache.sling.launchpad.base.jar.136433574 1470 26.03.2013 15:09:01.486 *INFO* [main] Starting launcher ... 26.03.2013 15:09:01.488 *INFO* [main] HTTP server port: 8080 26.03.2013 15:09:01.541 *ERROR* [main] Failed to Start OSGi framework org.osgi.framework.BundleException: Uncaught Instantiation Issue: java.lang.ArrayIndexOutOfBoundsException: -1 at org.apache.sling.launchpad.base.impl.Sling.init(Sling.java:245) at org.apache.sling.launchpad.base.app.MainDelegate$1.init(MainDelegate.java:159) at org.apache.sling.launchpad.base.app.MainDelegate.start(MainDelegate.java:159) at org.apache.sling.launchpad.app.Main.startSling(Main.java:244) at org.apache.sling.launchpad.app.Main.init(Main.java:107) at org.apache.sling.launchpad.app.Main.main(Main.java:56) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.ArrayList.elementData(Unknown Source) at java.util.ArrayList.get(Unknown Source) at org.apache.felix.framework.BundleImpl.getCurrentModule(BundleImpl.java:1046) at org.apache.felix.framework.BundleImpl.getSymbolicName(BundleImpl.java:863) at org.apache.sling.launchpad.base.impl.SlingFelix.getSymbolicName(SlingFelix.java:32) at org.apache.felix.framework.Felix.toString(Felix.java:1012) at org.apache.felix.framework.Logger.doLog(Logger.java:128) at org.apache.felix.framework.Logger._log(Logger.java:181) at org.apache.felix.framework.Logger.log(Logger.java:114) at org.apache.felix.framework.ExtensionManager.init(ExtensionManager.java:201) at org.apache.felix.framework.Felix.init(Felix.java:374) at org.apache.sling.launchpad.base.impl.SlingFelix.init(SlingFelix.java:39) at org.apache.sling.launchpad.base.impl.Sling.init(Sling.java:235) ... 5 more 26.03.2013 15:09:01.591 *ERROR* [main] There was a problem launching Sling 26.03.2013 15:09:01.596 *INFO* [Sling Terminator] Java VM is shutting down
[jira] [Commented] (SLING-2477) Configuration via sling:OsgiConfig nodes does not support all types
[
https://issues.apache.org/jira/browse/SLING-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614655#comment-13614655
]
Ian Boston commented on SLING-2477:
---
Revisiting this, with trepidation since we didn't reach consensus.
Since we should use the same format to writeback, and wanting to achieve
consensus before doing anything, would it be wrong to support reading of both
formats ?
ie
name{int}: 1000
and
name: I1000
It should be possible to accommodate both styles.
Configuration via sling:OsgiConfig nodes does not support all types
---
Key: SLING-2477
URL: https://issues.apache.org/jira/browse/SLING-2477
Project: Sling
Issue Type: Bug
Components: Installer
Affects Versions: JCR Installer 3.1.2
Reporter: Alexander Klimetschek
Assignee: Ian Boston
Attachments: SLING-2477.patch
Most notably, the common service.ranking needs to be an Integer, while the
jcr property mapping only allows for Long types at the moment. The problem
is that JCR has a smaller set of property types than the OSGi config admin
(JCR: String, Boolean, Long, Double, Decimal; OSGi: String, Boolean, Long,
Integer, Float, Double, and probably more differences...).
Similarly to properties files (which do it in the value like
'service.ranking=I-1' with I=Integer), there must be a way to
explicitly specify the type regardless of the JCR type. For example, encoding
it in the property name like service.ranking{int}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2477) Configuration via sling:OsgiConfig nodes does not support all types
[
https://issues.apache.org/jira/browse/SLING-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614725#comment-13614725
]
Carsten Ziegeler commented on SLING-2477:
-
I didn't see a technical reason against the I1000 notation, so let's go with
this. Supporting two formats might create confusion which imho is not worth the
potential/questionable benefit.
As Sam Ruby mentioned around 2002: Apache is in theory a meritocracy but in
practice a do-ocracy
Configuration via sling:OsgiConfig nodes does not support all types
---
Key: SLING-2477
URL: https://issues.apache.org/jira/browse/SLING-2477
Project: Sling
Issue Type: Bug
Components: Installer
Affects Versions: JCR Installer 3.1.2
Reporter: Alexander Klimetschek
Assignee: Ian Boston
Attachments: SLING-2477.patch
Most notably, the common service.ranking needs to be an Integer, while the
jcr property mapping only allows for Long types at the moment. The problem
is that JCR has a smaller set of property types than the OSGi config admin
(JCR: String, Boolean, Long, Double, Decimal; OSGi: String, Boolean, Long,
Integer, Float, Double, and probably more differences...).
Similarly to properties files (which do it in the value like
'service.ranking=I-1' with I=Integer), there must be a way to
explicitly specify the type regardless of the JCR type. For example, encoding
it in the property name like service.ranking{int}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2798) Apache Cassandra backend for Sling: GSoC2013 Project
[ https://issues.apache.org/jira/browse/SLING-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Boston updated SLING-2798: -- Summary: Apache Cassandra backend for Sling: GSoC2013 Project (was: Apache Cassandra backing for Sling: GSoC2013 Project) Apache Cassandra backend for Sling: GSoC2013 Project Key: SLING-2798 URL: https://issues.apache.org/jira/browse/SLING-2798 Project: Sling Issue Type: Bug Components: Samples Reporter: Ian Boston Labels: cassandra, gsoc, gsoc2013, java, osgi, sling This is a proposal for GSoC2013: create an Resource Provider that allows resources stored in Apache Cassandra to be exposed as Sling Resources. Resources[1] are the basic building blocks of Sling. ResourceProviders[2] allow data sources to be added to the core ResourceProvider within Sling allowing those data sources to provide Resources at pre-determined locations in the resource tree. To put it in more familiar terms, implementing and adding a Resource provider is like mounting or mapping a network drive. A more recent addition to the facilities available in Sling include updatable ResourceProviders. Apache Cassandra[3] is a column database (NoSQL) which aims to provide linear scalability to web scale. It is used by many of the best known names on the internet. Initially this will provide read only resource access, but if there is time in the project will allow read write access to a cassandra cluster. Advanced Java skills are required, some knowledge of OSGi, Sling, Cassandra will be valuable. The following pages give more information about GSoC @apache: * http://www.google-melange.com/gsoc/homepage/google/gsoc2013 * http://community.apache.org/gsoc.html * http://s.apache.org/gsoc2013ideas 1 http://sling.apache.org/site/resources.html 2 http://sling.apache.org/apidocs/sling6/org/apache/sling/api/resource/ResourceProvider.html 3 http://cassandra.apache.org/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
