Yes, SLING-4360 added a check if the RRF is live to the method
ResourceResolver.isLive(). The problem is that you have to call that method
explicitly.
For me the use case is rather to detect programming mistakes like not listening
for ResourceResolverFactory restarts.
What about implicitly call
[
https://issues.apache.org/jira/browse/SLING-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Satya Deep Maheshwari closed SLING-4825.
> Add ability to handle webdav based DELETE requests
> -
[
https://issues.apache.org/jira/browse/SLING-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744900#comment-14744900
]
Satya Deep Maheshwari commented on SLING-4825:
--
Thanks.
> Add ability to han
[
https://issues.apache.org/jira/browse/SLING-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-5024.
---
Resolution: Fixed
rev. 1703063
https://svn.apache.org/repos/asf/sling/trunk/contrib/nosql/mon
Stefan Seifert created SLING-5024:
-
Summary: Sling NoSQL Resource Provider for MongoDB (based on
nosql.generic)
Key: SLING-5024
URL: https://issues.apache.org/jira/browse/SLING-5024
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-4881:
--
Component/s: (was: Extensions)
NoSQL
> NoSQL Generic Resource Provider: Pr
[
https://issues.apache.org/jira/browse/SLING-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-4381:
--
Component/s: (was: Extensions)
NoSQL
> Sling NoSQL Resource Provider for Co
[
https://issues.apache.org/jira/browse/SLING-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744100#comment-14744100
]
Alexander Klimetschek edited comment on SLING-5017 at 9/14/15 7:40 PM:
-
[
https://issues.apache.org/jira/browse/SLING-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744100#comment-14744100
]
Alexander Klimetschek commented on SLING-5017:
--
I see your points, but the wo
Am 14.09.15 um 18:04 schrieb Konrad Windszus:
> Thanks Carsten, indeed I am hitting SLING-4974.
> Could you point me to the commit which closes the resource resolvers after
> the restart of the factory (or after some required providers become
> unavailable)?
> I couldn’t find any related commit i
+1
On Mon, Sep 14, 2015 at 12:10 PM, Stefan Seifert
wrote:
> we need 2 more (binding) votes...
>
> stefan
>
>
> >-Original Message-
> >From: Stefan Seifert [mailto:sseif...@pro-vision.de]
> >Sent: Friday, September 11, 2015 12:06 AM
> >To: dev@sling.apache.org
> >Subject: [VOTE] Release
@any PMC member: please copy this release to the Sling dist directory.
stefan
>-Original Message-
>From: Stefan Seifert [mailto:sseif...@pro-vision.de]
>Sent: Thursday, September 10, 2015 11:11 PM
>To: dev@sling.apache.org
>Subject: [RESULT] [VOTE] Release Apache Sling Testing JCR Mock
we need 2 more (binding) votes...
stefan
>-Original Message-
>From: Stefan Seifert [mailto:sseif...@pro-vision.de]
>Sent: Friday, September 11, 2015 12:06 AM
>To: dev@sling.apache.org
>Subject: [VOTE] Release Apache Sling Models API 1.2.2, Models Impl 1.2.2
>
>Hi,
>
>Sling Models API 1.2
we need 2 more (binding) votes...
stefan
>-Original Message-
>From: Stefan Seifert [mailto:sseif...@pro-vision.de]
>Sent: Friday, September 11, 2015 12:16 AM
>To: dev@sling.apache.org
>Subject: [VOTE] Release Apache Sling Testing ResourceResolver Mock 1.1.10
>
>Hi,
>
>We solved 1 issues
Thanks Carsten, indeed I am hitting SLING-4974.
Could you point me to the commit which closes the resource resolvers after the
restart of the factory (or after some required providers become unavailable)?
I couldn’t find any related commit in
https://github.com/apache/sling/commits/trunk/bundles/
[
https://issues.apache.org/jira/browse/SLING-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus reopened SLING-5023:
> ResourceResolver bound in ObservationListenerSupport is stale after the
> configuration for t
[
https://issues.apache.org/jira/browse/SLING-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-5023.
Resolution: Duplicate
Fix Version/s: (was: SLING-4974)
> ResourceResolver bound i
[
https://issues.apache.org/jira/browse/SLING-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-5023.
Resolution: Fixed
Fix Version/s: SLING-4974
Indeed it is a duplicate. [~cziegeler] Th
Am 14.09.15 um 17:51 schrieb Konrad Windszus:
> Currently if the resource resolver factory is restarted (e.g. because the
> configuration has been changed) all resource resolvers which were being
> requested beforehand become almost useless, because they have no longer any
> providers being boun
[
https://issues.apache.org/jira/browse/SLING-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743708#comment-14743708
]
Carsten Ziegeler commented on SLING-5023:
-
Isn't this a dub of SLING-4974 ?
> Res
Currently if the resource resolver factory is restarted (e.g. because the
configuration has been changed) all resource resolvers which were being
requested beforehand become almost useless, because they have no longer any
providers being bound! This means those resolvers can only be used to retr
Konrad Windszus created SLING-5023:
--
Summary: ResourceResolver bound in ObservationListenerSupport is
stale after the configuration for the Resource Resolver Factory (PID:
org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl) is
[
https://issues.apache.org/jira/browse/SLING-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743529#comment-14743529
]
Bertrand Delacretaz edited comment on SLING-4603 at 9/14/15 1:52 PM:
---
[
https://issues.apache.org/jira/browse/SLING-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743529#comment-14743529
]
Bertrand Delacretaz commented on SLING-4603:
I agree that if Oak provides simi
[
https://issues.apache.org/jira/browse/SLING-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-5022.
-
Resolution: Fixed
Fixed in [r1702951|https://svn.apache.org/viewvc?view=revision&revision=1702951]
Radu Cotescu created SLING-5022:
---
Summary: ImporterTopLevel is not set up correctly for the
RhinoJavaScriptEngine
Key: SLING-5022
URL: https://issues.apache.org/jira/browse/SLING-5022
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-4825:
---
Fix Version/s: Launchpad Builder 8
JCR Webdav 2.3.2
> Add ability t
[
https://issues.apache.org/jira/browse/SLING-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-4825.
Resolution: Fixed
Thanks very much for your contribution, I have committed it in rev
[
https://issues.apache.org/jira/browse/SLING-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz reassigned SLING-4825:
--
Assignee: Bertrand Delacretaz
> Add ability to handle webdav based DELETE reque
[
https://issues.apache.org/jira/browse/SLING-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743428#comment-14743428
]
Bertrand Delacretaz edited comment on SLING-4819 at 9/14/15 12:16 PM:
--
[
https://issues.apache.org/jira/browse/SLING-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-4819:
---
Attachment: SLING-4819-combined.patch
Looks good to me, thanks! I'm attaching a slight
Hi,
Thanks, I've opened [1] with some suggestions. I hope it's not too much, as
it would really help to have some of it written down.
Best Regards
Ian
1 https://issues.apache.org/jira/browse/SLING-5021
On 14 September 2015 at 12:50, Stefan Egli wrote:
> Hi Ian,
>
> There's only that one docume
Ian Boston created SLING-5021:
-
Summary: Low Level Documentation for Sling Discovery.
Key: SLING-5021
URL: https://issues.apache.org/jira/browse/SLING-5021
Project: Sling
Issue Type: Wish
[
https://issues.apache.org/jira/browse/SLING-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marius Petria updated SLING-5020:
-
Description: Distribution a String[] property will end up on the other side
as String.
> Multival
Marius Petria created SLING-5020:
Summary: Multivalued properties of user nodes are not distributed
correctly
Key: SLING-5020
URL: https://issues.apache.org/jira/browse/SLING-5020
Project: Sling
Hi Ian,
There's only that one document ([0]) which you've already found. Sounds
like I should add more flesh to it - if you have suggestions as to what,
pls feel free to create a ticket and assign it to me. I'll take care of it!
Cheers,
Stefan
On 14/09/15 13:41, "Ian Boston" wrote:
>Hi,
>Is th
Hi,
Is there a detailed low level description of how Sling Discovery works and
how it stores content in the repository ?
I have Googled and can't find anything yet, other than the links below, and
the code. I would rather read something that said exactly what how Sling
Discovery is supposed to wo
[
https://issues.apache.org/jira/browse/SLING-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-5006.
Resolution: Fixed
> Allow to enable the usage of regular JCR users for service resolvers
> -
[
https://issues.apache.org/jira/browse/SLING-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743380#comment-14743380
]
Konrad Windszus commented on SLING-5006:
Extended the JcrSystemUserValidator in ht
[
https://issues.apache.org/jira/browse/SLING-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5006:
---
Fix Version/s: JCR Resource 2.5.8
> Allow to enable the usage of regular JCR users for service
[
https://issues.apache.org/jira/browse/SLING-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5006:
---
Fix Version/s: Service User Mapper 1.2.2
> Allow to enable the usage of regular JCR users for
[
https://issues.apache.org/jira/browse/SLING-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus reassigned SLING-5006:
--
Assignee: Konrad Windszus
> Allow to enable the usage of regular JCR users for service
[
https://issues.apache.org/jira/browse/SLING-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Boston resolved SLING-5018.
---
Resolution: Fixed
Fix Version/s: JCR Resource 2.3.12
Fixed by installing JCR Resource 2.3.12 c
[
https://issues.apache.org/jira/browse/SLING-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743103#comment-14743103
]
Marius Petria commented on SLING-5018:
--
JcrItemResource.getPath should not throw an I
[
https://issues.apache.org/jira/browse/SLING-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-5019.
-
Resolution: Fixed
Solved in rev 1702865
> ServiceUserMappedBundleFilter should be immedia
Carsten Ziegeler created SLING-5019:
---
Summary: ServiceUserMappedBundleFilter should be immediate
Key: SLING-5019
URL: https://issues.apache.org/jira/browse/SLING-5019
Project: Sling
Issue T
46 matches
Mail list logo
