[i18n] Integration tests fails with Oak

Hi, I moved the i18n integration tests to use Oak (instead of jackrabbit 2) and now one integration test fails. Right now, I don't see a good reason why. Any help or hint appreciated. Thanks Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

[jira] [Resolved] (SLING-5709) OakViewChecker#updateProperties() issueHeartbeat: discoveryService is null

[ https://issues.apache.org/jira/browse/SLING-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-5709. - Resolution: Fixed Assignee: Stefan Egli Fix Version/s: Discovery Oak 1.2.14

Re: [Oak] Too many OSGi configurations required

On Wednesday 21 September 2016 15:18:36 Carsten Ziegeler wrote: > > On Wednesday 21 September 2016 14:03:00 Carsten Ziegeler wrote: > >>> On Wednesday 21 September 2016 11:56:30 Carsten Ziegeler wrote: > >>> And use Testing PaxExam which comes with all required > >>> configurations. >

[CANCEL][VOTE] Release Apache Sling Discovery Commons 1.0.14 and Discovery Oak 1.2.12

Thx Daniel for spotting, not sure why I didn't spot this during testing.. I'm cancelling this release and will redo. Cheers, Stefan On 21/09/16 18:13, "Daniel Klco" wrote: >-1 This seems to depend on an unreleased version of the Sling API, >specifically: >

Re: [VOTE] Release Apache Sling Discovery Commons 1.0.14 and Discovery Oak 1.2.12

-1 This seems to depend on an unreleased version of the Sling API, specifically: org.apache.sling:org.apache.sling.api:jar:2.10.0 Released versions: http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.sling%22%20AND%20a%3A%22org.apache.sling.api%22 Please find build failure logs

Re: [VOTE] Release Apache Sling Discovery Commons 1.0.14 and Discovery Oak 1.2.12

+1 Cheers, Stefan On 21/09/16 17:06, "Stefan Egli" wrote: >Hi, > >We solved 3 issues in these 2 related releases: > >https://issues.apache.org/jira/browse/SLING/fixforversion/12335443 >https://issues.apache.org/jira/browse/SLING/fixforversion/12338203 > >Staging

[VOTE] Release Apache Sling Discovery Commons 1.0.14 and Discovery Oak 1.2.12

Hi, We solved 3 issues in these 2 related releases: https://issues.apache.org/jira/browse/SLING/fixforversion/12335443 https://issues.apache.org/jira/browse/SLING/fixforversion/12338203 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1525 You can use this

[jira] [Updated] (SLING-5598) Exclude slow tests by default with assume(sling.slow.tests.enabled)

[ https://issues.apache.org/jira/browse/SLING-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-5598: --- Fix Version/s: (was: Discovery Oak 1.2.12) (was: Discovery Commons 1.0.14)

[jira] [Updated] (SLING-5231) Remove getAdministrativeResourceResolver() usage from Discovery components

[ https://issues.apache.org/jira/browse/SLING-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-5231: --- Fix Version/s: (was: Discovery Oak 1.2.12) (was: Discovery Commons 1.0.14)

[jira] [Resolved] (SLING-5995) IdMapService should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-5995. Resolution: Fixed fixed in http://svn.apache.org/viewvc?rev=1761756=rev > IdMapService should move

[jira] [Updated] (SLING-5995) IdMapService should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-5995: --- Fix Version/s: Discovery Oak 1.2.12 Discovery Commons 1.0.14 > IdMapService should

[jira] [Updated] (SLING-5995) IdMapService should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-5995: --- Affects Version/s: Discovery Commons 1.0.12 Discovery Oak 1.2.10 >

[jira] [Resolved] (SLING-6065) in discovery: avoid OakViewChecker issueHeartbeat: discoveryService is null

[ https://issues.apache.org/jira/browse/SLING-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-6065. Resolution: Fixed removed unnecessary log.error - it's a legitimate case:

[jira] [Created] (SLING-6065) in discovery: avoid OakViewChecker issueHeartbeat: discoveryService is null

Stefan Egli created SLING-6065: -- Summary: in discovery: avoid OakViewChecker issueHeartbeat: discoveryService is null Key: SLING-6065 URL: https://issues.apache.org/jira/browse/SLING-6065 Project: Sling

Re: [Oak] Too many OSGi configurations required

> On Wednesday 21 September 2016 14:03:00 Carsten Ziegeler wrote: >>> On Wednesday 21 September 2016 11:56:30 Carsten Ziegeler wrote: >>> And use Testing PaxExam which comes with all required configurations. >> >> I want to keep my dependencies low > > One bundle (3 classes)

Re: Observation with the ResourceChangeListener

On 21/09/16 14:28, "Carsten Ziegeler" wrote: >> On 21/09/16 14:14, "Robert Munteanu" wrote: >> >>> On Wed, 2016-09-21 at 14:11 +0200, Stefan Egli wrote: On 21/09/16 11:26, "Robert Munteanu" wrote: > > On Wed,

Re: [Oak] Too many OSGi configurations required

On Wednesday 21 September 2016 14:03:00 Carsten Ziegeler wrote: > > On Wednesday 21 September 2016 11:56:30 Carsten Ziegeler wrote: > > And use Testing PaxExam which comes with all required configurations. > > I want to keep my dependencies low > >>> > >>> One bundle (3 classes)

Re: Observation with the ResourceChangeListener

> On 21/09/16 14:14, "Robert Munteanu" wrote: > >> On Wed, 2016-09-21 at 14:11 +0200, Stefan Egli wrote: >>> On 21/09/16 11:26, "Robert Munteanu" wrote: >>> On Wed, 2016-09-21 at 11:18 +0200, Carsten Ziegeler wrote: > > So we a) need to

Re: Observation with the ResourceChangeListener

On 21/09/16 14:14, "Robert Munteanu" wrote: >On Wed, 2016-09-21 at 14:11 +0200, Stefan Egli wrote: >> On 21/09/16 11:26, "Robert Munteanu" wrote: >> >> > >> > On Wed, 2016-09-21 at 11:18 +0200, Carsten Ziegeler wrote: >> > > >> > > So we a) need to

Re: Observation with the ResourceChangeListener

On Wed, 2016-09-21 at 14:11 +0200, Stefan Egli wrote: > On 21/09/16 11:26, "Robert Munteanu" wrote: > > > > > On Wed, 2016-09-21 at 11:18 +0200, Carsten Ziegeler wrote: > > > > > > So we a) need to clarify the contract and b) think about what we > > > do > > > if > > >

Re: Observation with the ResourceChangeListener

On 21/09/16 11:26, "Robert Munteanu" wrote: >On Wed, 2016-09-21 at 11:18 +0200, Carsten Ziegeler wrote: >>So we a) need to clarify the contract and b) think about what we do >> if >> someone registers for a glob pattern. Do we send removal of parents >> automatically or do we

Re: [Oak] Too many OSGi configurations required

> On Wednesday 21 September 2016 11:56:30 Carsten Ziegeler wrote: > And use Testing PaxExam which comes with all required configurations. I want to keep my dependencies low >>> >>> One bundle (3 classes) vs. lots of boilerplate code... YMMV. >> >> I tried this for the i18n module,

Re: [i18n] IT Tests failing in reactor build

> On Wednesday 21 September 2016 13:09:39 Konrad Windszus wrote: >> Is this a known issue in Pax Exam or in Maven Failsafe? I had a quick look >> through the open issues in the latter and couldn’t find a report related to >> our issues. Do you have any references or enough information to report

Re: [i18n] IT Tests failing in reactor build

On Wednesday 21 September 2016 13:09:39 Konrad Windszus wrote: > Is this a known issue in Pax Exam or in Maven Failsafe? I had a quick look > through the open issues in the latter and couldn’t find a report related to > our issues. Do you have any references or enough information to report the >

[jira] [Commented] (SLING-5995) IdMapService should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15509636#comment-15509636 ] Stefan Egli commented on SLING-5995: Note that this change requires sling.api 2.10 or newer -

Re: [Oak] Too many OSGi configurations required

On Wednesday 21 September 2016 11:56:30 Carsten Ziegeler wrote: > >>> And use Testing PaxExam which comes with all required configurations. > >> > >> I want to keep my dependencies low > > > > One bundle (3 classes) vs. lots of boilerplate code... YMMV. > > I tried this for the i18n module, but

Re: Sling JMS Based Job Support - Difference between queue name and job type

Thanks Ian for the details. That helps! Chetan Mehrotra On Wed, Sep 21, 2016 at 4:32 PM, Ian Boston wrote: > Hi, > Documentation (README.md) and JavaDoc has been updated. Hopefully that will > make it easier for everyone to follow, including myself in a few months > time. > Best

Re: [i18n] IT Tests failing in reactor build

Is this a known issue in Pax Exam or in Maven Failsafe? I had a quick look through the open issues in the latter and couldn’t find a report related to our issues. Do you have any references or enough information to report the issue upstream? Thanks, Konrad > Am 21.09.2016 um 12:59 schrieb

Re: Sling JMS Based Job Support - Difference between queue name and job type

Hi, Documentation (README.md) and JavaDoc has been updated. Hopefully that will make it easier for everyone to follow, including myself in a few months time. Best Regards Ian On 21 September 2016 at 11:08, Ian Boston wrote: > Hi, > Its been a while since I have looked at this

Re: [i18n] IT Tests failing in reactor build

On Wednesday 21 September 2016 08:15:12 Carsten Ziegeler wrote: > It seems the problem on Jenkins was related to the latest failsafe > plugin, 2.19.1 - I ran into the exact same problem yesterday while > updating the event IT tests to Oak. Downgrading to 2.18.1 solved the > problem. So I

Re: Sling JMS Based Job Support - Difference between queue name and job type

Hi, Its been a while since I have looked at this code, and I realise the JavaDoc on the API isn't quite as complete as it should be. The bundle was originally intended as an example of how to use the MoM API, but it does serve as a Job subsystem. Its probably best to talk about how a job is run

Re: [Oak] Too many OSGi configurations required

> >>> And use Testing PaxExam which comes with all required configurations. >> >> I want to keep my dependencies low > > One bundle (3 classes) vs. lots of boilerplate code... YMMV. I tried this for the i18n module, but I get Caused by: java.lang.ClassNotFoundException:

Re: Observation with the ResourceChangeListener

On Wed, 2016-09-21 at 11:18 +0200, Carsten Ziegeler wrote: > > > > On Wed, 2016-09-21 at 10:21 +0200, Carsten Ziegeler wrote: > > > > > > > > > > > > > > > > > > > > > > > On 21.9.16 9:14 , Carsten Ziegeler wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >

Re: Observation with the ResourceChangeListener

On 21/09/16 11:18, "Carsten Ziegeler" wrote: >So we a) need to clarify the contract and b) think about what we do if >someone registers for a glob pattern. Do we send removal of parents >automatically or do we expect to listener to register at /? I'd say clarifying the

Re: Observation with the ResourceChangeListener

> On Wed, 2016-09-21 at 10:21 +0200, Carsten Ziegeler wrote: >>> >>> >>> >>> On 21.9.16 9:14 , Carsten Ziegeler wrote: > > > > On 21.9.16 8:50 , Carsten Ziegeler wrote: >> >>> >>> >>> >>> On 21.9.16 8:33 , Carsten Ziegeler wrote: >

Re: Observation with the ResourceChangeListener

On 21/09/16 11:12, "Carsten Ziegeler" wrote: >> Hi, >> >> On 21/09/16 08:13, "Carsten Ziegeler" wrote: >> >>> Finally, recently some people suggested that we support all of Oaks >>> filtering possibilities for the ResourceChangeListener. I'm not a

Re: Observation with the ResourceChangeListener

> Hi, > > On 21/09/16 08:13, "Carsten Ziegeler" wrote: > >> Finally, recently some people suggested that we support all of Oaks >> filtering possibilities for the ResourceChangeListener. I'm not a fan of >> that - first of all, we should only support what is really needed.

Re: Observation with the ResourceChangeListener

On Wed, 2016-09-21 at 10:21 +0200, Carsten Ziegeler wrote: > > > > > > > > On 21.9.16 9:14 , Carsten Ziegeler wrote: > > > > > > > > > > > > > > > > > > > On 21.9.16 8:50 , Carsten Ziegeler wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 21.9.16 8:33 , Carsten

[jira] [Created] (SLING-6064) Redirect servlet should encode url for redirecting

Carsten Ziegeler created SLING-6064: --- Summary: Redirect servlet should encode url for redirecting Key: SLING-6064 URL: https://issues.apache.org/jira/browse/SLING-6064 Project: Sling Issue

[jira] [Resolved] (SLING-6063) plumber servlet doesn't persist changes anymore

[ https://issues.apache.org/jira/browse/SLING-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-6063. Resolution: Fixed Committed in https://svn.apache.org/r1761699, thanks for the patch! >

[jira] [Updated] (SLING-6063) plumber servlet doesn't persist changes anymore

[ https://issues.apache.org/jira/browse/SLING-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-6063: --- Fix Version/s: Pipes 1.0.0 > plumber servlet doesn't persist changes anymore >

[jira] [Assigned] (SLING-6063) plumber servlet doesn't persist changes anymore

[ https://issues.apache.org/jira/browse/SLING-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-6063: -- Assignee: Robert Munteanu > plumber servlet doesn't persist changes anymore >

Re: Observation with the ResourceChangeListener

Hi, On 21/09/16 08:13, "Carsten Ziegeler" wrote: >Finally, recently some people suggested that we support all of Oaks >filtering possibilities for the ResourceChangeListener. I'm not a fan of >that - first of all, we should only support what is really needed. >Second, as

Re: [VOTE] Release Apache Sling Testing Clients 1.0.0, Apache Sling Server Setup Tools 1.0.0 and Apache Sling Testing Rules 1.0.0

Sorry, I forgot I had already added https://sling.apache.org/documentation/tutorials-how-tos/testing-sling-based-applications.html#http-based-integration-tests Would it make sense to add it to the page you linked and maybe drop a couple of lines regarding the usecases? - Andrei On Wed, Sep 21,

Re: [VOTE] Release Apache Sling Testing Clients 1.0.0, Apache Sling Server Setup Tools 1.0.0 and Apache Sling Testing Rules 1.0.0

Hi Konrad, On Wed, Sep 21, 2016 at 10:18 AM Konrad Windszus wrote: > Hey Andrei, could you briefly mention those new bundles in > https://sling.apache.org/documentation/development/sling-testing-tools.html > and/or >

Re: Observation with the ResourceChangeListener

> > > On 21.9.16 9:14 , Carsten Ziegeler wrote: >>> >>> >>> On 21.9.16 8:50 , Carsten Ziegeler wrote: > > > On 21.9.16 8:33 , Carsten Ziegeler wrote: >>> Pushing filters as much into Oak has many performance advantages >>> though compared to filter messages after

[jira] [Updated] (SLING-6063) plumber servlet doesn't persist changes anymore

[ https://issues.apache.org/jira/browse/SLING-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6063: --- Component/s: Extensions > plumber servlet doesn't persist changes anymore >

[jira] [Updated] (SLING-6063) plumber servlet doesn't persist changes anymore

[ https://issues.apache.org/jira/browse/SLING-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6063: --- Affects Version/s: Pipes 1.0.0 > plumber servlet doesn't persist changes anymore >

Re: [VOTE] Release Apache Sling Testing Clients 1.0.0, Apache Sling Server Setup Tools 1.0.0 and Apache Sling Testing Rules 1.0.0

Hey Andrei, could you briefly mention those new bundles in https://sling.apache.org/documentation/development/sling-testing-tools.html and/or https://sling.apache.org/documentation/bundles/org-apache-sling-junit-bundles.html just to have the complete picture on those pages? To me the

Re: [VOTE] Release Apache Sling Testing Clients 1.0.0, Apache Sling Server Setup Tools 1.0.0 and Apache Sling Testing Rules 1.0.0

Hi Stefan. Thanks for the +1. On Tue, Sep 20, 2016 at 6:20 PM Stefan Seifert wrote: > +1 > > this is a lot of interesting stuff - do we already have some > documentation/sample project for this? > We have some docu on the junit rules [0] - the entrypoint for writing a

Re: Observation with the ResourceChangeListener

On 21.9.16 9:14 , Carsten Ziegeler wrote: On 21.9.16 8:50 , Carsten Ziegeler wrote: On 21.9.16 8:33 , Carsten Ziegeler wrote: Pushing filters as much into Oak has many performance advantages though compared to filter messages after delivery. Also Oak would easily able to support the

RE: Observation with the ResourceChangeListener

>But we have to think about other providers as well, what if I use the >mongo resource provider? Can we make the same guarantees? We have an >abstraction and have to come up with a solution that always works >without exceptions. when speaking oft he nosql resource providers based on the generic

[jira] [Assigned] (SLING-5995) IdMapService should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-5995: --- Assignee: Stefan Egli [~egli] Could you please look into this one? > IdMapService

[jira] [Assigned] (SLING-5996) DistributedEventSender should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-5996: --- Assignee: Carsten Ziegeler > DistributedEventSender should move to new

[jira] [Commented] (SLING-6000) MapEntries should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15509072#comment-15509072 ] Carsten Ziegeler commented on SLING-6000: - This is a tricky one as it is listening to changes

Re: Observation with the ResourceChangeListener

> > > On 21.9.16 8:50 , Carsten Ziegeler wrote: >>> >>> >>> On 21.9.16 8:33 , Carsten Ziegeler wrote: > Pushing filters as much into Oak has many performance advantages > though >> compared to filter messages after delivery. Also Oak would easily >> able >> to support the

Re: Observation with the ResourceChangeListener

On 21.9.16 8:50 , Carsten Ziegeler wrote: On 21.9.16 8:33 , Carsten Ziegeler wrote: Pushing filters as much into Oak has many performance advantages though compared to filter messages after delivery. Also Oak would easily able to support the delete use case described above. In all cases,

Re: Observation with the ResourceChangeListener

> > > On 21.9.16 8:33 , Carsten Ziegeler wrote: >>> Pushing filters as much into Oak has many performance advantages though >>> > compared to filter messages after delivery. Also Oak would easily able >>> > to support the delete use case described above. >>> > >> In all cases, always,

Sling JMS Based Job Support - Difference between queue name and job type

I was looking at the Sling JMS based Job SLING-5645 and trying to understand the api flow. Sender side submits a job for a given queue and job type -- Job job = jobManager.newJobBuilder(Types.jobQueue(TOPIC), Types.jobType(AsyncJobConsumer.JOB_TYPE)).addProperties(

Re: Observation with the ResourceChangeListener

On 21.9.16 8:33 , Carsten Ziegeler wrote: Pushing filters as much into Oak has many performance advantages though > compared to filter messages after delivery. Also Oak would easily able > to support the delete use case described above. > In all cases, always, guaranteed? For some

Re: Observation with the ResourceChangeListener

> > > On 21.9.16 8:13 , Carsten Ziegeler wrote: >> Finally, recently some people suggested that we support all of Oaks >> filtering possibilities for the ResourceChangeListener. I'm not a fan of >> that - first of all, we should only support what is really needed. >> Second, as soon as we

Re: Observation with the ResourceChangeListener

On 21.9.16 8:13 , Carsten Ziegeler wrote: Finally, recently some people suggested that we support all of Oaks filtering possibilities for the ResourceChangeListener. I'm not a fan of that - first of all, we should only support what is really needed. Second, as soon as we support it, it means

Re: [i18n] IT Tests failing in reactor build

It seems the problem on Jenkins was related to the latest failsafe plugin, 2.19.1 - I ran into the exact same problem yesterday while updating the event IT tests to Oak. Downgrading to 2.18.1 solved the problem. So I downgraded i18n to use that version as well and now it seems that the project is

Observation with the ResourceChangeListener

Hi, as you know we're currently in the process of moving away from the OSGi event based observation to the ResourceChangeListener interfaces. Main reason is moving to a more scalable/better performing solution. We started very simple with the ResourceChangeListener: listeners register themselves

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15508869#comment-15508869 ] Carsten Ziegeler commented on SLING-6056: - I think this is a separate issue and we have to be