Build failed in Jenkins: sling-trunk-1.6 #1638

[Apache Jenkins Server]

See 

Changes:

[rombert] SLING-2847 : Installer integration tests fail due to unresolvable
artifacts

Since pax-exam does not support the maven.repo.local system property,
add support for it in OsgiInstallerTestBase.

[cziegeler] SLING-2703 : [SlingPostServlet] PathNotFoundException logged when 
uploading file using slingpostservlet

[cziegeler] SLING-2775 :  Setting of auto properties depends on specific 
Jackrabbit behviour

--
[...truncated 16758 lines...]
INFO: Bundle org.apache.sling.auth.selector installed from 
slinginstall:org.apache.sling.auth.selector-1.0.5-SNAPSHOT.jar
INFO: Bundle org.apache.sling.commons.scheduler installed from 
slinginstall:org.apache.sling.commons.scheduler-2.3.4.jar
INFO: Bundle org.apache.sling.auth.openid installed from 
slinginstall:org.apache.sling.auth.openid-1.0.3-SNAPSHOT.jar
INFO: Bundle org.apache.sling.junit.core installed from 
slinginstall:org.apache.sling.junit.core-1.0.8.jar
INFO: Bundle org.apache.sling.servlets.resolver installed from 
slinginstall:org.apache.sling.servlets.resolver-2.2.4.jar
INFO: Bundle org.apache.sling.resourceresolver installed from 
slinginstall:org.apache.sling.resourceresolver-1.0.6.jar
INFO: Bundle org.apache.sling.servlets.get installed from 
slinginstall:org.apache.sling.servlets.get-2.1.4.jar
INFO: Bundle org.apache.sling.installer.provider.file installed from 
slinginstall:org.apache.sling.installer.provider.file-1.0.2.jar
INFO: Bundle org.apache.sling.scripting.javascript installed from 
slinginstall:org.apache.sling.scripting.javascript-2.0.12.jar
INFO: Bundle org.apache.sling.commons.classloader installed from 
slinginstall:org.apache.sling.commons.classloader-1.3.0.jar
INFO: Bundle org.apache.sling.junit.scriptable installed from 
slinginstall:org.apache.sling.junit.scriptable-1.0.8.jar
INFO: Bundle org.apache.sling.launchpad.installer installed from 
slinginstall:org.apache.sling.launchpad.installer-1.2.0.jar
INFO: Bundle org.apache.commons.lang installed from 
slinginstall:commons-lang-2.5.jar
INFO: Bundle org.apache.sling.fsresource installed from 
slinginstall:org.apache.sling.fsresource-1.1.2.jar
INFO: Bundle org.apache.sling.commons.mime installed from 
slinginstall:org.apache.sling.commons.mime-2.1.4.jar
INFO: Bundle org.apache.commons.codec installed from 
slinginstall:commons-codec-1.6.jar
INFO: Bundle org.apache.sling.scripting.api installed from 
slinginstall:org.apache.sling.scripting.api-2.1.4.jar
INFO: Bundle org.apache.commons.io installed from 
slinginstall:commons-io-1.4.jar
INFO: Bundle org.apache.sling.auth.core installed from 
slinginstall:org.apache.sling.auth.core-1.1.2.jar
INFO: Bundle org.apache.sling.settings installed from 
slinginstall:org.apache.sling.settings-1.2.2.jar
INFO: Started startup handler with target start level=30, and expected bundle 
count=104
INFO: Startup progress 1/104
INFO: Startup progress 2/104
INFO: Startup progress 3/104
INFO: Startup progress 4/104
01.05.2013 03:15:34.430 *INFO* [FelixStartLevel] org.mortbay.log Logging to 
org.apache.sling.commons.log.internal.slf4j.SlingLogger@a26818 via 
org.mortbay.log.Slf4jLog
INFO: Startup progress 4/104
INFO: Startup progress 4/104
01.05.2013 03:15:34.436 *INFO* [FelixStartLevel] 
org.apache.sling.commons.logservice Service 
[org.apache.sling.commons.logservice.internal.LogServiceFactory,8] ServiceEvent 
REGISTERED
01.05.2013 03:15:34.437 *INFO* [FelixStartLevel] 
org.apache.sling.commons.logservice Service 
[org.apache.sling.commons.logservice.internal.LogReaderServiceFactory,9] 
ServiceEvent REGISTERED
01.05.2013 03:15:34.437 *INFO* [FelixStartLevel] 
org.apache.sling.commons.logservice BundleEvent STARTED
INFO: Startup progress 4/104
01.05.2013 03:15:34.437 *INFO* [FelixStartLevel] org.apache.sling.commons.log 
BundleEvent STARTING
INFO: Startup progress 4/104
INFO: Startup progress 5/104
INFO: Startup progress 5/104
INFO: Startup progress 6/104
INFO: Startup progress 7/104
INFO: Startup progress 8/104
INFO: Startup progress 9/104
INFO: Startup progress 9/104
INFO: Startup progress 10/104
INFO: Startup progress 10/104
INFO: Startup progress 11/104
INFO: Startup progress 11/104
INFO: Startup progress 12/104
INFO: Startup progress 13/104
INFO: Startup progress 14/104
INFO: Startup progress 15/104
INFO: Startup progress 16/104
INFO: Startup progress 16/104
INFO: Startup progress 17/104
INFO: Startup progress 18/104
INFO: Startup progress 19/104
INFO: Startup progress 19/104
INFO: Startup progress 20/104
INFO: Startup progress 20/104
INFO: Startup progress 21/104
INFO: Startup progress 21/104
INFO: Startup progress 22/104
INFO: Startup progress 22/104
INFO: Startup progress 23/104
INFO: Startup progress 23/104
INFO: Startup progress 24/104
INFO: Startup progress 25/104
INFO: Startup progress 26/104
INFO: Startup progress 27/104
INFO: Startup progress 28/104
INFO: Startup progress 29/104
INFO: Startup progress 30/104
INFO: Startup progre

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Installer Integration Tests #1638

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-2847) Installer integration tests fail due to unresolvable artifacts

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646140#comment-13646140
 ] 

Robert Munteanu commented on SLING-2847:


Added support for the maven.repo.local property in 
http://svn.apache.org/viewvc?view=revision&revision=1477870 . Leaving open 
until tests are verified to pass.

> Installer integration tests fail due to unresolvable artifacts
> --
>
> Key: SLING-2847
> URL: https://issues.apache.org/jira/browse/SLING-2847
> Project: Sling
>  Issue Type: Bug
>  Components: Installer
>Reporter: Robert Munteanu
>
> Pax-Exam does not resolve dependencies which are generated using the reactor 
> build. Tthe -Dmaven.repo.local argument is not supported for locating the 
> default Maven repository, according to
> https://ops4j1.jira.com/wiki/display/paxurl/Mvn+Protocol#MvnProtocol-local
> What happens is that the reactor build installs the -SNAPSHOT artifacts in 
> the repository specified by the maven.repo.local system property, but pax is 
> looking for them somewhere else.

--
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-2847) Installer integration tests fail due to unresolvable artifacts

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-2847:
--

 Summary: Installer integration tests fail due to unresolvable 
artifacts
 Key: SLING-2847
 URL: https://issues.apache.org/jira/browse/SLING-2847
 Project: Sling
  Issue Type: Bug
  Components: Installer
Reporter: Robert Munteanu


Pax-Exam does not resolve dependencies which are generated using the reactor 
build. Tthe -Dmaven.repo.local argument is not supported for locating the 
default Maven repository, according to

https://ops4j1.jira.com/wiki/display/paxurl/Mvn+Protocol#MvnProtocol-local

What happens is that the reactor build installs the -SNAPSHOT artifacts in the 
repository specified by the maven.repo.local system property, but pax is 
looking for them somewhere else.

--
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: [VOTE] Release parent 16

[Ian Boston]

+1
Signatures all good.
I did notice some Jenkins failures on list, but will guess (since release
without build is impossible) that these are transitive.
Ian


On 1 May 2013 01:48, Mike Müller  wrote:

> +1
> Best regards
> mike
>
> > -Original Message-
> > From: Carsten Ziegeler [mailto:cziege...@apache.org]
> > Sent: Tuesday, April 30, 2013 11:58 AM
> > To: dev@sling.apache.org
> > Subject: [VOTE] Release parent 16
> >
> > Please vote for the release of a new parent pom. This contains a single
> > change, the update to the latest Maven SCR plugin (
> > https://issues.apache.org/jira/browse/SLING-2846)
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachesling-156
> >
> >
> > 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 156 /tmp/sling-staging
> >
> >
> > Please vote to approve this release:
> >
> >  [ ] +1 Approve the release
> >  [ ]  0 Don't care
> >  [ ] -1 Don't release, because ...
> >
> > This vote will be open for 72 hours.
> >
> > Regards
> > --
> > Carsten Ziegeler
> > cziege...@apache.org
>

Re: Interested in participating to GSoC 2013 with Sling

[Ian Boston]

Hi Ishan,
Dont forget the deadline for proposals is 3rd May, ie this Friday.
Best Regards
Ian


On 29 March 2013 09:35, Ian Boston  wrote:

> Hi,
>
> On 28 March 2013 01:17, Bertrand Delacretaz 
> wrote:
> > Hi,
> >
> > On Wed, Mar 27, 2013 at 2:32 PM, Ishan Thilina 
> wrote:
> >> ...The JMX agent I wrote collected JMX data and published them to a
> Cassandra
> >> cluster (Please take a look at [2]). So I have experience working with
> >> Cassandra too. So I think I am a good candidate to carry out this
> project.
> >> Can anyone please guide me on how I should continue..?...
> >
> > Thanks very much for your interest - IMO the next steps would be for
> > you and the potential project's mentor (Ian I assume, as you created
> > SLING-2798?) to agree on a set of goals and initial requirements.
>
>
> Yes, sorry, catching up on email.
>
> The aim here is to create a ResourceProvider which is mounted at a
> fixed location in the resource tree
> eg /content/cassandra
> and provide Resource implementations backed by Cassandra data.
> eg
> /content/cassandra/columnFamilyA/rowIDB/column  might deliver a
> Cassandra Resource implementation contain a set of properties.
>
> better would be
> /content/cassandra/a/real/human/readable/path
>
> would convert /a/real/human/readable/path into a cassandra row/column
> and deliver that.
>
> Once a read only implementation is done, we will want to add path
> based access control.
> Then make it read write.
> Then see how well it performs with certain patterns of load and use.
>
> The details of exactly how this is done, the design, the mapping, are
> all part of the project.
>
>
> If you get to the end of that, then your a RockStar!
>
>
> But first, as Bertrand says, discover more about Sling and keep an eye
> on the dates and timeline for GSoC. The deadlines are real hard
> deadlines.
>
> Good luck.
> Ian
>
>
> >
> > Note that as per
> > http://www.google-melange.com/gsoc/events/google/gsoc2013 the list of
> > participating organizations is not confirmed by Google so far, so
> > there's no guarantee that this will happen, and the ASF would get a
> > limited number of slots anyway so it's hard to predict how many slots
> > Sling would get, if any.
> >
> > At this point the best way to maximize your chances is probably to get
> > familiar with Sling, you can start at
> >
> http://sling.apache.org/documentation/getting-started/discover-sling-in-15-minutes.html
> > and I suggest following up by studying the slingbucks and espblog
> > samples.
> >
> > -Bertrand
> >
> >>
> >> [1]. https://issues.apache.org/jira/browse/SLING-2798
> >> [2]. http://wso2.org/library/articles/2013/02/jmx-monitoring-wso2-bam
> >> [3]. http://wso2.com/products/business-activity-monitor/
>

Re: GSOC 2013 - Test and Fix Apache Oak Integration with Sling

[Ian Boston]

Dont forget, the deadline for proposals is 3rd May (Probably end of day
PST).


On 30 April 2013 10:28, Ian Boston  wrote:

> Hi,
> I put that one up. The need is genuine, here is some background.
>
> Apache Sling uses a content repository to store its content. You can think
> of it like a file system but its a lot more sophisticated than that. The
> standard content repository is Apache Jackrabbit. Version 1.x and 2.x of
> Apache Jackrabbit were focused on delivering blisteringly fast read access
> to content in deep content hierarchies where 99% of the activity was read
> and 1% was write. It does that outstandingly well. Time has moved on, the
> web has become more social and applications typically have higher levels of
> write acces. Content trees have become more user generated and hence are
> often flatter with few levels and millions of children.
>
> Apache Oak is the next generation of Apache Jackrabbit which aims to
> support much higher levels of write, and much wider flatter
> content hierarchies. It has also been designed to support cloud like
> deployments on NoSQL infrastructure  There is support for storage on
> MongoDB already and other backends are almost certainly possible. Where
> Jackrabbit 2.x was capable of being deployed in small clusters, Oak should
> be suitable for large clusters.
>
> For Apache Sling to use Apache Oak the Apache Jackrabbit server component
> has been replaced with an Apache Oak version. Fortunately all the projects
> mentioned interact constantly and so the basics of this all work. What
> hasn't been done yet is to bring up an Sling instance running on Oak and
> run the 100s of Sling integration tests against that instance. If that can
> be achieved it will create a high level of confidence that Sling will run
> on Oak.
>
> As of today, here is what works:
> An instance of Sling running on Oak that starts up and accepts requests
> using Basic http authentication.[1]
> An initial attempt at getting the integration testing framework running,
> which almost starts.
>
> The GSoC project will need to:
>
> Make the integration test framework run.
> Identify tests that fail.
> Fix tests that fail by providing patches to Sling or to Apache Oak.
> (Optionally) write some tests that exercise some of the features of Oak
> (high levels of write, large numbers of children).
>
> If you want to take up this challenge you are going to need to be willing
> to learn about OSGi and you will have to be prepared on interact with both
> the Sling and Jackrabbit/Oak communities, as most of the solutions to
> problems you find will be in the community, such is Apache!
>
> Ian
>
> 1 http://svn.apache.org/repos/asf/sling/whiteboard/ieb/oak/
> (there is a commit pending here, within the hour).
>
>
>
> On 30 April 2013 08:38, Marcus Santos  wrote:
>
>> Hi everyone,
>>
>> I'm interested to contribute on the project "Test and Fix Apache Oak
>> Integration with Sling" under GSOC. How can I talk with the mentor to know
>> more about it and expose my doubts?
>>
>> Best regards,
>> Marcus Santos
>>
>
>

Re: GSoC 2013 - Apache Solr backend for Apache Sling

[Ian Boston]

Hi
Some comments in line,
but please remember to submit this proposal at the GSoC site so that it can
be reviewed.
The deadline is

3rd May 2013

Ie this Friday.

Ian
(More below).


On 30 April 2013 19:15, Ilya Velesevich  wrote:

> Hi Everyone,
>
> I‘m working on proposal for “Apache Solr backend for Apache Sling” task as
> part of Google Summer of Code 2013 –
> https://issues.apache.org/jira/browse/SLING-2795. Thus far I was reading
> articles/watching videos/looking through source code to investigate the
> topic in more depth. Now I want to describe my vision on task and
> implementation approach. All your comments/suggestions would be very
> helpful in order to improve my proposal and bring more value of
> implementing the task.
>
> I see several parts of the task.
>
> *1.   **Provide CRUDL operations for Solr data through Sling API.*
>
> This will allow creating Sling resources residing in Solr server and
> querying them through Sling API using Solr search capabilities. Solr query
> syntax should be used for queries.
>
> From Sling API perspective custom *ResourceProvider *(and *Resource*)
> implementation will be created additionally implementing *
> QueriableResourceProvider* and *ModifyingResourceProvider*. (If necessary *
> RefreshableResourceProvider* and *DynamicResourceProvider* interfaces will
> also be implemented). To communicate with Solr server Solrj API will be
> used.
>


yes (and you might want to think about runing Solr embedded for dev
purposes).


>
> *2.   **Provide convenient ways to create Solr resources based on
> different data.*
>
> *2.1.**Create Solr resource based on arbitrary Sling resource*. This
> will allow adding Sling resources to Solr server for efficient search. The
> created Solr resource will also hold a reference (most likely, resource
> path) to the original Sling resource. The *Adaptable* concept seems to be a
> reasonable way of implementing this functionality – to “convert” arbitrary
> Sling resource to Solr resource and resolve original Sling resource based
> on Solr resource.
>
> Also I think that not all metadata of Sling resource should be used when
> creating corresponding Solr resource – so this task should also include
> some configuration to specify metadata necessary to be passed to Solr
> resource. Additionally, some transformations on resource metadata could be
> supported here.
>



I think you should think initially about just getting or resolving Solr
resources using the ResourceResolver.

Later you can add creating those resources via the
ModifyingResourceProvider. If you think of a Resource as a map of
properties, then it fits the Solr document model reasonably well. Ie a
Resource maps 1:1 with a Solr Document.



>
> * 2.2.*When creating Solr resources not all data could be efficiently
> stored in Solr – for instance, large binary files. If this is the
> situation, one could create Sling resource (for instance, FileSystem or
> Jackrabbit) and then create Solr resource based on that Sling resource –
> this’ll allow both efficient search through Solr and effective storing
> options. As an optimization, these steps could be done automatically based
> on some configuration. So *when Solr resource is created we could analyze
> it
> * (analyze metadata, trying to adapt to certain types) *and create
> additional supporting resources in other parts of Sling virtual resource
> tree if necessary*. What do you think – is it necessary to implement such
> functionality or 2.1 option will be sufficient? What useful scenarios do
> you see for this task besides the “large binary” scenario?
>


Resources may have properties that are streams. How the stream is stored
and delivered is an implementation detail of the ResourceProvider and the
object it provides. So a SolrResourceProvider might provide SolrResource
objects, which expose a SolrResourceDocument when
resource.adaptTo(SolrResourceDocument.class) is invoked.

The SolrResourceDocument might then have a getBodyStream() method.


>
> *3.   **Provide solution to support search for arbitrary Sling
> resources through Sling API using Solr capabilities.*
>
> From my point of view this one needs some external solutions to support
> things like full index, incremental index, creating different schedules,
> etc. I see that Solr DataImportHandler or Apache ManifoldCF could be
> utilized for this task. So the concept of solution here would be to write
> necessary implementation so that Sling virtual resource tree could be used
> as a data source for one of the components mentioned above. What do you
> think about this approach? Could you advice some other alternatives to Solr
> DataImportHandler and Apache ManifoldCF for implementing this task?
>
>
>
> Also I’ve got couple of questions on Sling API:
>
>- Am I right that the “best practice” way to provide bundle with custom
> *
>ResourceProvider* implementation is to use Apache Felix Maven SCR Plugin
>and specify certain SCR annotatio

[jira] [Commented] (SLING-2795) Apache Solr backend for Apache Sling

[Ian Boston (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646031#comment-13646031
 ] 

Ian Boston commented on SLING-2795:
---

[~pchel] Dont forget to submit a proposal before 3rd May, ie this friday.

> 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] http://sling.apache.org/site/resources.html

--
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-2798) Apache Cassandra backend for Sling: GSoC2013 Project

[Ian Boston (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646030#comment-13646030
 ] 

Ian Boston commented on SLING-2798:
---

Dishara submitted  a proposal see 
http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/ddwijewardana/18001

> 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
> Attachments: Sling Cassandra backend Architecture.jpg
>
>
> 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] [Commented] (SLING-2799) Elastic Search backend for Sling: GSoC2013

[Ian Boston (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646027#comment-13646027
 ] 

Ian Boston commented on SLING-2799:
---

[~hatim] Dont forget the deadline for student applications is 3rd May. ie This 
Friday.

> 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
>  Labels: elasticsearch, gsoc, gsoc2013, java, osgi, sling
>
> 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] [Commented] (SLING-2800) Test and Fix Apache Oak Integration with Sling: GSoC2013

[Ian Boston (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646025#comment-13646025
 ] 

Ian Boston commented on SLING-2800:
---

[~mvcs] Dont forget the deadline for student applications is 3rd May. ie This 
Friday.

> 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
>  Labels: gsoc, gsoc2013, java, oak, osgi
>
> 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

[jira] [Resolved] (SLING-2703) [SlingPostServlet] PathNotFoundException logged when uploading file using slingpostservlet

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved SLING-2703.
-

Resolution: Fixed

I changed the code to check whether the node is new (transient) or not. If it 
is new, it first checks whether jcr:content is available. Otherwise same 
behaviour as before

Revision: 1477722

> [SlingPostServlet] PathNotFoundException logged when uploading file using 
> slingpostservlet
> --
>
> Key: SLING-2703
> URL: https://issues.apache.org/jira/browse/SLING-2703
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: JCR Resource 2.2.6
>Reporter: Shashank Gupta
>Assignee: Carsten Ziegeler
>Priority: Minor
> Fix For: JCR Resource 2.2.8
>
>
> The nt:file node along with content is created successfully. 
> Complete exception trace:
> 03.01.2013 18:40:53.686 *INFO* [127.0.0.1 [1357218653685] POST /content/page 
> HTTP/1.1] org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource 
> setMetaData: Problem extracting metadata information for /content/page/image 
> javax.jcr.PathNotFoundException: jcr:content
>   at org.apache.jackrabbit.core.NodeImpl$8.perform(NodeImpl.java:2151)
>   at org.apache.jackrabbit.core.NodeImpl$8.perform(NodeImpl.java:2145)
>   at 
> org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
>   at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
>   at org.apache.jackrabbit.core.NodeImpl.getNode(NodeImpl.java:2145)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource.setMetaData(JcrNodeResource.java:276)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource.(JcrNodeResource.java:97)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.create(JcrResourceProvider.java:421)
>   at 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.create(ResourceResolverImpl.java:1063)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.createWithChanges(SlingFileUploadHandler.java:305)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.getOrCreateChildResource(SlingFileUploadHandler.java:287)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.setFile(SlingFileUploadHandler.java:144)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.setFile(SlingFileUploadHandler.java:269)
>   at 
> org.apache.sling.servlets.post.impl.operations.ModifyOperation.writeContent(ModifyOperation.java:409)
>   at 
> org.apache.sling.servlets.post.impl.operations.ModifyOperation.doRun(ModifyOperation.java:101)
>   at 
> org.apache.sling.servlets.post.AbstractPostOperation.run(AbstractPostOperation.java:92)
>   at 
> org.apache.sling.servlets.post.impl.SlingPostServlet.doPost(SlingPostServlet.java:202)
>   at 
> org.apache.sling.api.servlets.SlingAllMethodsServlet.mayService(SlingAllMethodsServlet.java:148)
>   at 
> org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:344)
>   at 
> org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:375)
>   at 
> org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:508)
>   at 
> org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:45)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:64)
>   at 
> com.day.cq.wcm.core.impl.WCMDebugFilter.doFilter(WCMDebugFilter.java:148)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
>   at 
> com.day.cq.wcm.core.impl.WCMComponentFilter.filterRootInclude(WCMComponentFilter.java:333)
>   at 
> com.day.cq.wcm.core.impl.WCMComponentFilter.doFilter(WCMComponentFilter.java:160)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
>   at 
> org.apache.sling.engine.impl.SlingRequestProcessorImpl.processComponent(SlingRequestProcessorImpl.java:254)
>   at 
> org.apache.sling.engine.impl.filter.RequestSlingFilterChain.render(RequestSlingFilterChain.java:49)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:64)
>   at 
> com.day.cq.wcm.core.impl.warp.TimeWarpFilter.doFilter(TimeWarpFilter.java:106)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
>   at 
> com.day.cq.wcm.mobile.core.impl.redirect.Redirec

[jira] [Updated] (SLING-2703) [SlingPostServlet] PathNotFoundException logged when uploading file using slingpostservlet

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler updated SLING-2703:


Fix Version/s: (was: Servlets Post 2.3.0)
   JCR Resource 2.2.8

> [SlingPostServlet] PathNotFoundException logged when uploading file using 
> slingpostservlet
> --
>
> Key: SLING-2703
> URL: https://issues.apache.org/jira/browse/SLING-2703
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: JCR Resource 2.2.6
>Reporter: Shashank Gupta
>Priority: Minor
> Fix For: JCR Resource 2.2.8
>
>
> The nt:file node along with content is created successfully. 
> Complete exception trace:
> 03.01.2013 18:40:53.686 *INFO* [127.0.0.1 [1357218653685] POST /content/page 
> HTTP/1.1] org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource 
> setMetaData: Problem extracting metadata information for /content/page/image 
> javax.jcr.PathNotFoundException: jcr:content
>   at org.apache.jackrabbit.core.NodeImpl$8.perform(NodeImpl.java:2151)
>   at org.apache.jackrabbit.core.NodeImpl$8.perform(NodeImpl.java:2145)
>   at 
> org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
>   at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
>   at org.apache.jackrabbit.core.NodeImpl.getNode(NodeImpl.java:2145)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource.setMetaData(JcrNodeResource.java:276)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource.(JcrNodeResource.java:97)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.create(JcrResourceProvider.java:421)
>   at 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.create(ResourceResolverImpl.java:1063)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.createWithChanges(SlingFileUploadHandler.java:305)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.getOrCreateChildResource(SlingFileUploadHandler.java:287)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.setFile(SlingFileUploadHandler.java:144)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.setFile(SlingFileUploadHandler.java:269)
>   at 
> org.apache.sling.servlets.post.impl.operations.ModifyOperation.writeContent(ModifyOperation.java:409)
>   at 
> org.apache.sling.servlets.post.impl.operations.ModifyOperation.doRun(ModifyOperation.java:101)
>   at 
> org.apache.sling.servlets.post.AbstractPostOperation.run(AbstractPostOperation.java:92)
>   at 
> org.apache.sling.servlets.post.impl.SlingPostServlet.doPost(SlingPostServlet.java:202)
>   at 
> org.apache.sling.api.servlets.SlingAllMethodsServlet.mayService(SlingAllMethodsServlet.java:148)
>   at 
> org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:344)
>   at 
> org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:375)
>   at 
> org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:508)
>   at 
> org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:45)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:64)
>   at 
> com.day.cq.wcm.core.impl.WCMDebugFilter.doFilter(WCMDebugFilter.java:148)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
>   at 
> com.day.cq.wcm.core.impl.WCMComponentFilter.filterRootInclude(WCMComponentFilter.java:333)
>   at 
> com.day.cq.wcm.core.impl.WCMComponentFilter.doFilter(WCMComponentFilter.java:160)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
>   at 
> org.apache.sling.engine.impl.SlingRequestProcessorImpl.processComponent(SlingRequestProcessorImpl.java:254)
>   at 
> org.apache.sling.engine.impl.filter.RequestSlingFilterChain.render(RequestSlingFilterChain.java:49)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:64)
>   at 
> com.day.cq.wcm.core.impl.warp.TimeWarpFilter.doFilter(TimeWarpFilter.java:106)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
>   at 
> com.day.cq.wcm.mobile.core.impl.redirect.RedirectFilter.doFilter(RedirectFilter.java:290)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
>   at 
> org.apa

[jira] [Assigned] (SLING-2703) [SlingPostServlet] PathNotFoundException logged when uploading file using slingpostservlet

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler reassigned SLING-2703:
---

Assignee: Carsten Ziegeler

> [SlingPostServlet] PathNotFoundException logged when uploading file using 
> slingpostservlet
> --
>
> Key: SLING-2703
> URL: https://issues.apache.org/jira/browse/SLING-2703
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: JCR Resource 2.2.6
>Reporter: Shashank Gupta
>Assignee: Carsten Ziegeler
>Priority: Minor
> Fix For: JCR Resource 2.2.8
>
>
> The nt:file node along with content is created successfully. 
> Complete exception trace:
> 03.01.2013 18:40:53.686 *INFO* [127.0.0.1 [1357218653685] POST /content/page 
> HTTP/1.1] org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource 
> setMetaData: Problem extracting metadata information for /content/page/image 
> javax.jcr.PathNotFoundException: jcr:content
>   at org.apache.jackrabbit.core.NodeImpl$8.perform(NodeImpl.java:2151)
>   at org.apache.jackrabbit.core.NodeImpl$8.perform(NodeImpl.java:2145)
>   at 
> org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
>   at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
>   at org.apache.jackrabbit.core.NodeImpl.getNode(NodeImpl.java:2145)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource.setMetaData(JcrNodeResource.java:276)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource.(JcrNodeResource.java:97)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.create(JcrResourceProvider.java:421)
>   at 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.create(ResourceResolverImpl.java:1063)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.createWithChanges(SlingFileUploadHandler.java:305)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.getOrCreateChildResource(SlingFileUploadHandler.java:287)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.setFile(SlingFileUploadHandler.java:144)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.setFile(SlingFileUploadHandler.java:269)
>   at 
> org.apache.sling.servlets.post.impl.operations.ModifyOperation.writeContent(ModifyOperation.java:409)
>   at 
> org.apache.sling.servlets.post.impl.operations.ModifyOperation.doRun(ModifyOperation.java:101)
>   at 
> org.apache.sling.servlets.post.AbstractPostOperation.run(AbstractPostOperation.java:92)
>   at 
> org.apache.sling.servlets.post.impl.SlingPostServlet.doPost(SlingPostServlet.java:202)
>   at 
> org.apache.sling.api.servlets.SlingAllMethodsServlet.mayService(SlingAllMethodsServlet.java:148)
>   at 
> org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:344)
>   at 
> org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:375)
>   at 
> org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:508)
>   at 
> org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:45)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:64)
>   at 
> com.day.cq.wcm.core.impl.WCMDebugFilter.doFilter(WCMDebugFilter.java:148)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
>   at 
> com.day.cq.wcm.core.impl.WCMComponentFilter.filterRootInclude(WCMComponentFilter.java:333)
>   at 
> com.day.cq.wcm.core.impl.WCMComponentFilter.doFilter(WCMComponentFilter.java:160)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
>   at 
> org.apache.sling.engine.impl.SlingRequestProcessorImpl.processComponent(SlingRequestProcessorImpl.java:254)
>   at 
> org.apache.sling.engine.impl.filter.RequestSlingFilterChain.render(RequestSlingFilterChain.java:49)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:64)
>   at 
> com.day.cq.wcm.core.impl.warp.TimeWarpFilter.doFilter(TimeWarpFilter.java:106)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
>   at 
> com.day.cq.wcm.mobile.core.impl.redirect.RedirectFilter.doFilter(RedirectFilter.java:290)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
>   at 
> org.apache.sling.e

[jira] [Updated] (SLING-2703) [SlingPostServlet] PathNotFoundException logged when uploading file using slingpostservlet

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler updated SLING-2703:


Affects Version/s: (was: Servlets Post 2.2.0)
   JCR Resource 2.2.6

> [SlingPostServlet] PathNotFoundException logged when uploading file using 
> slingpostservlet
> --
>
> Key: SLING-2703
> URL: https://issues.apache.org/jira/browse/SLING-2703
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: JCR Resource 2.2.6
>Reporter: Shashank Gupta
>Priority: Minor
> Fix For: Servlets Post 2.3.0
>
>
> The nt:file node along with content is created successfully. 
> Complete exception trace:
> 03.01.2013 18:40:53.686 *INFO* [127.0.0.1 [1357218653685] POST /content/page 
> HTTP/1.1] org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource 
> setMetaData: Problem extracting metadata information for /content/page/image 
> javax.jcr.PathNotFoundException: jcr:content
>   at org.apache.jackrabbit.core.NodeImpl$8.perform(NodeImpl.java:2151)
>   at org.apache.jackrabbit.core.NodeImpl$8.perform(NodeImpl.java:2145)
>   at 
> org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
>   at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
>   at org.apache.jackrabbit.core.NodeImpl.getNode(NodeImpl.java:2145)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource.setMetaData(JcrNodeResource.java:276)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource.(JcrNodeResource.java:97)
>   at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.create(JcrResourceProvider.java:421)
>   at 
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.create(ResourceResolverImpl.java:1063)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.createWithChanges(SlingFileUploadHandler.java:305)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.getOrCreateChildResource(SlingFileUploadHandler.java:287)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.setFile(SlingFileUploadHandler.java:144)
>   at 
> org.apache.sling.servlets.post.impl.helper.SlingFileUploadHandler.setFile(SlingFileUploadHandler.java:269)
>   at 
> org.apache.sling.servlets.post.impl.operations.ModifyOperation.writeContent(ModifyOperation.java:409)
>   at 
> org.apache.sling.servlets.post.impl.operations.ModifyOperation.doRun(ModifyOperation.java:101)
>   at 
> org.apache.sling.servlets.post.AbstractPostOperation.run(AbstractPostOperation.java:92)
>   at 
> org.apache.sling.servlets.post.impl.SlingPostServlet.doPost(SlingPostServlet.java:202)
>   at 
> org.apache.sling.api.servlets.SlingAllMethodsServlet.mayService(SlingAllMethodsServlet.java:148)
>   at 
> org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:344)
>   at 
> org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:375)
>   at 
> org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:508)
>   at 
> org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:45)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:64)
>   at 
> com.day.cq.wcm.core.impl.WCMDebugFilter.doFilter(WCMDebugFilter.java:148)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
>   at 
> com.day.cq.wcm.core.impl.WCMComponentFilter.filterRootInclude(WCMComponentFilter.java:333)
>   at 
> com.day.cq.wcm.core.impl.WCMComponentFilter.doFilter(WCMComponentFilter.java:160)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
>   at 
> org.apache.sling.engine.impl.SlingRequestProcessorImpl.processComponent(SlingRequestProcessorImpl.java:254)
>   at 
> org.apache.sling.engine.impl.filter.RequestSlingFilterChain.render(RequestSlingFilterChain.java:49)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:64)
>   at 
> com.day.cq.wcm.core.impl.warp.TimeWarpFilter.doFilter(TimeWarpFilter.java:106)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
>   at 
> com.day.cq.wcm.mobile.core.impl.redirect.RedirectFilter.doFilter(RedirectFilter.java:290)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:60)
>   at 

RE: [VOTE] Release API 2.4.2

[Mike Müller]

+1
Best regards
mike

> -Original Message-
> From: Carsten Ziegeler [mailto:cziege...@apache.org]
> Sent: Tuesday, April 30, 2013 10:16 AM
> To: dev@sling.apache.org
> Subject: [VOTE] Release API 2.4.2
> 
> Hi,
> 
> I just fixed two errors in ResourceUtil (SLING-2844 and SLING-2845) which
> imho warrant a new release. So here we go
> 
> Please vote for the release of API 2.4.2
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-155
> 
> 
> 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 155 /tmp/sling-staging
> 
> 
> Please vote to approve this release:
> 
>  [ ] +1 Approve the release
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...
> 
> This vote will be open for 72 hours.
> 
> Regards
> 
> --
> Carsten Ziegeler
> cziege...@apache.org

RE: [VOTE] Release parent 16

[Mike Müller]

+1
Best regards
mike

> -Original Message-
> From: Carsten Ziegeler [mailto:cziege...@apache.org]
> Sent: Tuesday, April 30, 2013 11:58 AM
> To: dev@sling.apache.org
> Subject: [VOTE] Release parent 16
> 
> Please vote for the release of a new parent pom. This contains a single
> change, the update to the latest Maven SCR plugin (
> https://issues.apache.org/jira/browse/SLING-2846)
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-156
> 
> 
> 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 156 /tmp/sling-staging
> 
> 
> Please vote to approve this release:
> 
>  [ ] +1 Approve the release
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...
> 
> This vote will be open for 72 hours.
> 
> Regards
> --
> Carsten Ziegeler
> cziege...@apache.org

[jira] [Resolved] (SLING-2775) Setting of auto properties depends on specific Jackrabbit behviour

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved SLING-2775.
-

Resolution: Fixed

Tests pass, I think we can set this to fixed

> Setting of auto properties depends on specific Jackrabbit behviour
> --
>
> Key: SLING-2775
> URL: https://issues.apache.org/jira/browse/SLING-2775
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Post 2.2.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Servlets Post 2.3.0
>
>
> The post servlet ignores a ConstraintViolationException when trying to set an 
> auto property (SlingPropertyValueHandler#setProperty method. This has been 
> introduced by SLING-1619
> According to SLING-2763 this is specific Jackrabbit behaviour and might fail 
> with other implementations (e.g. Oak) as the check might not occur when 
> setting the property but when saving.
> Looking at the comments of SLING-1619, I'm not sure if adding this check for 
> the ConstraintViolationException was the right thing to do anyway.

--
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] [Assigned] (SLING-2775) Setting of auto properties depends on specific Jackrabbit behviour

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler reassigned SLING-2775:
---

Assignee: Carsten Ziegeler

> Setting of auto properties depends on specific Jackrabbit behviour
> --
>
> Key: SLING-2775
> URL: https://issues.apache.org/jira/browse/SLING-2775
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Post 2.2.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Servlets Post 2.3.0
>
>
> The post servlet ignores a ConstraintViolationException when trying to set an 
> auto property (SlingPropertyValueHandler#setProperty method. This has been 
> introduced by SLING-1619
> According to SLING-2763 this is specific Jackrabbit behaviour and might fail 
> with other implementations (e.g. Oak) as the check might not occur when 
> setting the property but when saving.
> Looking at the comments of SLING-1619, I'm not sure if adding this check for 
> the ConstraintViolationException was the right thing to do anyway.

--
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-2775) Setting of auto properties depends on specific Jackrabbit behviour

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645674#comment-13645674
 ] 

Carsten Ziegeler commented on SLING-2775:
-

Instead of simply ignoring a potential exception when setting the property - 
which will fail with Oak (or other JCR implementations), I went to long way and 
do a nodetype check, find the property definiton for the auto property and see 
if it is managed by the repository. If so, the value is ignored.

Revision: 1477692

> Setting of auto properties depends on specific Jackrabbit behviour
> --
>
> Key: SLING-2775
> URL: https://issues.apache.org/jira/browse/SLING-2775
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Post 2.2.0
>Reporter: Carsten Ziegeler
> Fix For: Servlets Post 2.3.0
>
>
> The post servlet ignores a ConstraintViolationException when trying to set an 
> auto property (SlingPropertyValueHandler#setProperty method. This has been 
> introduced by SLING-1619
> According to SLING-2763 this is specific Jackrabbit behaviour and might fail 
> with other implementations (e.g. Oak) as the check might not occur when 
> setting the property but when saving.
> Looking at the comments of SLING-1619, I'm not sure if adding this check for 
> the ConstraintViolationException was the right thing to do anyway.

--
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: [VOTE] Release parent 16

[Robert Munteanu]

> Please vote for the release of a new parent pom. This contains a single
> change, the update to the latest Maven SCR plugin (
> https://issues.apache.org/jira/browse/SLING-2846)

+1

Robert

[VOTE] Release parent 16

[Carsten Ziegeler]

Please vote for the release of a new parent pom. This contains a single
change, the update to the latest Maven SCR plugin (
https://issues.apache.org/jira/browse/SLING-2846)

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-156


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 156 /tmp/sling-staging


Please vote to approve this release:

 [ ] +1 Approve the release
 [ ]  0 Don't care
 [ ] -1 Don't release, because ...

This vote will be open for 72 hours.

Regards
-- 
Carsten Ziegeler
cziege...@apache.org

[jira] [Resolved] (SLING-2846) Use latest Maven SCR Plugin 1.12.0

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved SLING-2846.
-

Resolution: Fixed

Updated to plugin 1.12.0 and scr annotations 1.9.2

> Use latest Maven SCR Plugin 1.12.0
> --
>
> Key: SLING-2846
> URL: https://issues.apache.org/jira/browse/SLING-2846
> Project: Sling
>  Issue Type: Improvement
>  Components: General
>Affects Versions: Parent 15
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Parent 16
>
>
> The latest version contains some important bug fixes, especially for metatype 
> generation

--
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-2846) Use latest Maven SCR Plugin 1.12.0

[Carsten Ziegeler (JIRA)]

Carsten Ziegeler created SLING-2846:
---

 Summary: Use latest Maven SCR Plugin 1.12.0
 Key: SLING-2846
 URL: https://issues.apache.org/jira/browse/SLING-2846
 Project: Sling
  Issue Type: Improvement
  Components: General
Affects Versions: Parent 15
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: Parent 16


The latest version contains some important bug fixes, especially for metatype 
generation

--
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: [VOTE] Release API 2.4.2

[Robert Munteanu]

> I just fixed two errors in ResourceUtil (SLING-2844 and SLING-2845) which
> imho warrant a new release. So here we go
>
> Please vote for the release of API 2.4.2
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-155

+1

Robert

Build failed in Jenkins: sling-trunk-1.6 #1636

[Apache Jenkins Server]

See 

Changes:

[cziegeler] SLING-2829 : Be prepared to handle read failures in value map

--
[...truncated 16880 lines...]
INFO: Bundle org.apache.sling.auth.openid installed from 
slinginstall:org.apache.sling.auth.openid-1.0.3-SNAPSHOT.jar
INFO: Bundle org.apache.sling.junit.core installed from 
slinginstall:org.apache.sling.junit.core-1.0.8.jar
INFO: Bundle org.apache.sling.servlets.resolver installed from 
slinginstall:org.apache.sling.servlets.resolver-2.2.4.jar
INFO: Bundle org.apache.sling.resourceresolver installed from 
slinginstall:org.apache.sling.resourceresolver-1.0.6.jar
INFO: Bundle org.apache.sling.servlets.get installed from 
slinginstall:org.apache.sling.servlets.get-2.1.4.jar
INFO: Bundle org.apache.sling.installer.provider.file installed from 
slinginstall:org.apache.sling.installer.provider.file-1.0.2.jar
INFO: Bundle org.apache.sling.scripting.javascript installed from 
slinginstall:org.apache.sling.scripting.javascript-2.0.12.jar
INFO: Bundle org.apache.sling.commons.classloader installed from 
slinginstall:org.apache.sling.commons.classloader-1.3.0.jar
INFO: Bundle org.apache.sling.junit.scriptable installed from 
slinginstall:org.apache.sling.junit.scriptable-1.0.8.jar
INFO: Bundle org.apache.sling.launchpad.installer installed from 
slinginstall:org.apache.sling.launchpad.installer-1.2.0.jar
INFO: Bundle org.apache.commons.lang installed from 
slinginstall:commons-lang-2.5.jar
INFO: Bundle org.apache.sling.fsresource installed from 
slinginstall:org.apache.sling.fsresource-1.1.2.jar
INFO: Bundle org.apache.sling.commons.mime installed from 
slinginstall:org.apache.sling.commons.mime-2.1.4.jar
INFO: Bundle org.apache.commons.codec installed from 
slinginstall:commons-codec-1.6.jar
INFO: Bundle org.apache.sling.scripting.api installed from 
slinginstall:org.apache.sling.scripting.api-2.1.4.jar
INFO: Bundle org.apache.commons.io installed from 
slinginstall:commons-io-1.4.jar
INFO: Bundle org.apache.sling.auth.core installed from 
slinginstall:org.apache.sling.auth.core-1.1.2.jar
INFO: Bundle org.apache.sling.settings installed from 
slinginstall:org.apache.sling.settings-1.2.2.jar
INFO: Started startup handler with target start level=30, and expected bundle 
count=104
INFO: Startup progress 1/104
INFO: Startup progress 2/104
INFO: Startup progress 3/104
INFO: Startup progress 4/104
30.04.2013 07:01:07.024 *INFO* [FelixStartLevel] org.mortbay.log Logging to 
org.apache.sling.commons.log.internal.slf4j.SlingLogger@b04f37 via 
org.mortbay.log.Slf4jLog
INFO: Startup progress 4/104
INFO: Startup progress 4/104
30.04.2013 07:01:07.031 *INFO* [FelixStartLevel] 
org.apache.sling.commons.logservice Service 
[org.apache.sling.commons.logservice.internal.LogServiceFactory,8] ServiceEvent 
REGISTERED
30.04.2013 07:01:07.031 *INFO* [FelixStartLevel] 
org.apache.sling.commons.logservice Service 
[org.apache.sling.commons.logservice.internal.LogReaderServiceFactory,9] 
ServiceEvent REGISTERED
30.04.2013 07:01:07.031 *INFO* [FelixStartLevel] 
org.apache.sling.commons.logservice BundleEvent STARTED
INFO: Startup progress 4/104
30.04.2013 07:01:07.031 *INFO* [FelixStartLevel] org.apache.sling.commons.log 
BundleEvent STARTING
INFO: Startup progress 4/104
INFO: Startup progress 5/104
INFO: Startup progress 5/104
INFO: Startup progress 6/104
INFO: Startup progress 7/104
INFO: Startup progress 8/104
INFO: Startup progress 9/104
INFO: Startup progress 9/104
INFO: Startup progress 10/104
INFO: Startup progress 10/104
INFO: Startup progress 11/104
INFO: Startup progress 11/104
INFO: Startup progress 12/104
INFO: Startup progress 13/104
INFO: Startup progress 14/104
INFO: Startup progress 14/104
INFO: Startup progress 15/104
INFO: Startup progress 16/104
INFO: Startup progress 17/104
INFO: Startup progress 18/104
INFO: Startup progress 19/104
INFO: Startup progress 19/104
INFO: Startup progress 20/104
INFO: Startup progress 20/104
INFO: Startup progress 21/104
INFO: Startup progress 21/104
INFO: Startup progress 22/104
INFO: Startup progress 22/104
INFO: Startup progress 23/104
INFO: Startup progress 23/104
INFO: Startup progress 24/104
INFO: Startup progress 25/104
INFO: Startup progress 26/104
INFO: Startup progress 27/104
INFO: Startup progress 28/104
INFO: Startup progress 29/104
INFO: Startup progress 30/104
INFO: Startup progress 31/104
INFO: Startup progress 31/104
INFO: Startup progress 32/104
INFO: Startup progress 32/104
INFO: Startup progress 33/104
INFO: Startup progress 33/104
INFO: Startup progress 33/104
INFO: Startup progress 34/104
INFO: Startup progress 35/104
INFO: Startup progress 36/104
INFO: Startup progress 36/104
INFO: Startup progress 37/104
INFO: Startup progress 38/104
INFO: Startup progress 38/104
INFO: Startup progress 38/104
INFO: Startup progress 39/104
INFO: Startup progress 39/104
INFO: Startup progress 39/104
INFO: Startup progress 40/104
INFO: Startup progress 40/104
INFO: 

GSoC 2013 - Apache Solr backend for Apache Sling

[Ilya Velesevich]

Hi Everyone,

I‘m working on proposal for “Apache Solr backend for Apache Sling” task as
part of Google Summer of Code 2013 –
https://issues.apache.org/jira/browse/SLING-2795. Thus far I was reading
articles/watching videos/looking through source code to investigate the
topic in more depth. Now I want to describe my vision on task and
implementation approach. All your comments/suggestions would be very
helpful in order to improve my proposal and bring more value of
implementing the task.

I see several parts of the task.

*1.   **Provide CRUDL operations for Solr data through Sling API.*

This will allow creating Sling resources residing in Solr server and
querying them through Sling API using Solr search capabilities. Solr query
syntax should be used for queries.

>From Sling API perspective custom *ResourceProvider *(and *Resource*)
implementation will be created additionally implementing *
QueriableResourceProvider* and *ModifyingResourceProvider*. (If necessary *
RefreshableResourceProvider* and *DynamicResourceProvider* interfaces will
also be implemented). To communicate with Solr server Solrj API will be
used.

*2.   **Provide convenient ways to create Solr resources based on
different data.*

*2.1.**Create Solr resource based on arbitrary Sling resource*. This
will allow adding Sling resources to Solr server for efficient search. The
created Solr resource will also hold a reference (most likely, resource
path) to the original Sling resource. The *Adaptable* concept seems to be a
reasonable way of implementing this functionality – to “convert” arbitrary
Sling resource to Solr resource and resolve original Sling resource based
on Solr resource.

Also I think that not all metadata of Sling resource should be used when
creating corresponding Solr resource – so this task should also include
some configuration to specify metadata necessary to be passed to Solr
resource. Additionally, some transformations on resource metadata could be
supported here.

* 2.2.*When creating Solr resources not all data could be efficiently
stored in Solr – for instance, large binary files. If this is the
situation, one could create Sling resource (for instance, FileSystem or
Jackrabbit) and then create Solr resource based on that Sling resource –
this’ll allow both efficient search through Solr and effective storing
options. As an optimization, these steps could be done automatically based
on some configuration. So *when Solr resource is created we could analyze it
* (analyze metadata, trying to adapt to certain types) *and create
additional supporting resources in other parts of Sling virtual resource
tree if necessary*. What do you think – is it necessary to implement such
functionality or 2.1 option will be sufficient? What useful scenarios do
you see for this task besides the “large binary” scenario?

*3.   **Provide solution to support search for arbitrary Sling
resources through Sling API using Solr capabilities.*

>From my point of view this one needs some external solutions to support
things like full index, incremental index, creating different schedules,
etc. I see that Solr DataImportHandler or Apache ManifoldCF could be
utilized for this task. So the concept of solution here would be to write
necessary implementation so that Sling virtual resource tree could be used
as a data source for one of the components mentioned above. What do you
think about this approach? Could you advice some other alternatives to Solr
DataImportHandler and Apache ManifoldCF for implementing this task?



Also I’ve got couple of questions on Sling API:

   - Am I right that the “best practice” way to provide bundle with custom *
   ResourceProvider* implementation is to use Apache Felix Maven SCR Plugin
   and specify certain SCR annotations (like *@Component*, *@Service* and
   some others) on corresponding classes – *ResourceProvider* or *
   ResourceProviderFactory* implementation in this case?


   - I see that *ResourceResolver* is intended to be used by clients to
   obtain and work with Sling resources. Also it seems to me that it is
   unlikely necessary to create custom *ResourceResolver* implementation
   for the Solr integration task. But still, could you please specify some
   valid typical cases when one would need to create custom *
   ResourceResolver*?


   - Suppose I have configured same resource provider implementation (like
   file system resource provider or possible Solr resource provider) under two
   urls “/url1” and “/url2”. Now I want to perform *findResources*/*
   queryResources* but only for the resources residing under “/url1”. Is it
   possible to limit search results in such way? (Probably I missed something,
   but looking through source code it seems that query results from all
   queriable resource providers supporting given query language will be
   combined regardless where in the resource tree corresponding provider is
   configured)



Please write any feedback/thoughts you have 

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Event Support #1636

[Apache Jenkins Server]

See 

Re: [VOTE] Release API 2.4.2

[Ian Boston]

+1
The change set following from [1] looks good and all signatures are good
from Nexus.
Ian


1 https://issues.apache.org/jira/browse/SLING/fixforversion/12324113


On 30 April 2013 18:32, Jeff Young  wrote:

> +1
>
> (I was about to ask for a test for SLING-2844, but I see you already added
> one.)
>
> Cheers,
> Jeff.
>
>
> > -Original Message-
> > From: Carsten Ziegeler [mailto:cziege...@apache.org]
> > Sent: 30 April 2013 09:16
> > To: dev@sling.apache.org
> > Subject: [VOTE] Release API 2.4.2
> >
> > Hi,
> >
> > I just fixed two errors in ResourceUtil (SLING-2844 and SLING-2845) which
> > imho warrant a new release. So here we go
> >
> > Please vote for the release of API 2.4.2
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachesling-155
> >
> >
> > 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 155 /tmp/sling-staging
> >
> >
> > Please vote to approve this release:
> >
> >  [ ] +1 Approve the release
> >  [ ]  0 Don't care
> >  [ ] -1 Don't release, because ...
> >
> > This vote will be open for 72 hours.
> >
> > Regards
> >
> > --
> > Carsten Ziegeler
> > cziege...@apache.org
>

RE: [VOTE] Release API 2.4.2

[Jeff Young]

+1

(I was about to ask for a test for SLING-2844, but I see you already added one.)

Cheers,
Jeff.


> -Original Message-
> From: Carsten Ziegeler [mailto:cziege...@apache.org]
> Sent: 30 April 2013 09:16
> To: dev@sling.apache.org
> Subject: [VOTE] Release API 2.4.2
> 
> Hi,
> 
> I just fixed two errors in ResourceUtil (SLING-2844 and SLING-2845) which
> imho warrant a new release. So here we go
> 
> Please vote for the release of API 2.4.2
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-155
> 
> 
> 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 155 /tmp/sling-staging
> 
> 
> Please vote to approve this release:
> 
>  [ ] +1 Approve the release
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...
> 
> This vote will be open for 72 hours.
> 
> Regards
> 
> --
> Carsten Ziegeler
> cziege...@apache.org

[VOTE] Release API 2.4.2

[Carsten Ziegeler]

Hi,

I just fixed two errors in ResourceUtil (SLING-2844 and SLING-2845) which
imho warrant a new release. So here we go

Please vote for the release of API 2.4.2

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-155


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 155 /tmp/sling-staging


Please vote to approve this release:

 [ ] +1 Approve the release
 [ ]  0 Don't care
 [ ] -1 Don't release, because ...

This vote will be open for 72 hours.

Regards

-- 
Carsten Ziegeler
cziege...@apache.org

[jira] [Resolved] (SLING-2845) ResourceUtil.getOrCreateResource should catch PersistenceException when calling create

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved SLING-2845.
-

Resolution: Fixed

Catching exception now and checking if the resource is available (revision 
1477494)

> ResourceUtil.getOrCreateResource should catch PersistenceException when 
> calling create
> --
>
> Key: SLING-2845
> URL: https://issues.apache.org/jira/browse/SLING-2845
> Project: Sling
>  Issue Type: Bug
>  Components: API
>Affects Versions: API 2.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: API 2.4.2
>
>
> If a resource is created concurrently, the call to ResourceResolver#create() 
> might throw a persistence exception. In that case we should retry

--
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-2845) ResourceUtil.getOrCreateResource should catch PersistenceException when calling create

[Carsten Ziegeler (JIRA)]

Carsten Ziegeler created SLING-2845:
---

 Summary: ResourceUtil.getOrCreateResource should catch 
PersistenceException when calling create
 Key: SLING-2845
 URL: https://issues.apache.org/jira/browse/SLING-2845
 Project: Sling
  Issue Type: Bug
  Components: API
Affects Versions: API 2.4.0
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: API 2.4.2


If a resource is created concurrently, the call to ResourceResolver#create() 
might throw a persistence exception. In that case we should retry

--
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] [Resolved] (SLING-2844) ResourceUtil.isA() and findResourceSuperType() should check for null resource

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved SLING-2844.
-

Resolution: Fixed

Added extra null checks in revision 1477492, and added simple tests for 
checking this

> ResourceUtil.isA() and findResourceSuperType()  should check for null resource
> --
>
> Key: SLING-2844
> URL: https://issues.apache.org/jira/browse/SLING-2844
> Project: Sling
>  Issue Type: Bug
>  Components: API
>Affects Versions: API 2.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: API 2.4.2
>
>
> ResourceUitl.isA() delegates to the resource resolver of the resource however 
> if the resource is null, this results in a NPE
> THe method should first check th resource for null and return false if it is 
> null

--
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-2844) ResourceUtil.isA() and findResourceSuperType() should check for null resource

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13645348#comment-13645348
 ] 

Carsten Ziegeler commented on SLING-2844:
-

The same applies for findResourceSuperType()

> ResourceUtil.isA() and findResourceSuperType()  should check for null resource
> --
>
> Key: SLING-2844
> URL: https://issues.apache.org/jira/browse/SLING-2844
> Project: Sling
>  Issue Type: Bug
>  Components: API
>Affects Versions: API 2.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: API 2.4.2
>
>
> ResourceUitl.isA() delegates to the resource resolver of the resource however 
> if the resource is null, this results in a NPE
> THe method should first check th resource for null and return false if it is 
> null

--
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-2844) ResourceUtil.isA() and findResourceSuperType() should check for null resource

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler updated SLING-2844:


Summary: ResourceUtil.isA() and findResourceSuperType()  should check for 
null resource  (was: ResourceUtil.isA() should check for null resource)

> ResourceUtil.isA() and findResourceSuperType()  should check for null resource
> --
>
> Key: SLING-2844
> URL: https://issues.apache.org/jira/browse/SLING-2844
> Project: Sling
>  Issue Type: Bug
>  Components: API
>Affects Versions: API 2.4.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: API 2.4.2
>
>
> ResourceUitl.isA() delegates to the resource resolver of the resource however 
> if the resource is null, this results in a NPE
> THe method should first check th resource for null and return false if it is 
> null

--
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-2844) ResourceUtil.isA() should check for null resource

[Carsten Ziegeler (JIRA)]

Carsten Ziegeler created SLING-2844:
---

 Summary: ResourceUtil.isA() should check for null resource
 Key: SLING-2844
 URL: https://issues.apache.org/jira/browse/SLING-2844
 Project: Sling
  Issue Type: Bug
  Components: API
Affects Versions: API 2.4.0
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: API 2.4.2


ResourceUitl.isA() delegates to the resource resolver of the resource however 
if the resource is null, this results in a NPE
THe method should first check th resource for null and return false if it is 
null

--
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