[jira] [Comment Edited] (SLING-6694) Replace commons.json usage in org.apache.sling.jcr.contentloader

[ https://issues.apache.org/jira/browse/SLING-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15939339#comment-15939339 ] Karl Pauls edited comment on SLING-6694 at 3/23/17 10:34 PM: - This one was a

RE: [VOTE] Release Apache Sling CAConfig SPI 1.3.0, CAConfig Impl 1.3.0, CAConfig Mock Plugin 1.1.0 - vote missing

... one binding vote is missing. stefan >-Original Message- >From: Stefan Seifert [mailto:sseif...@pro-vision.de] >Sent: Monday, March 20, 2017 11:52 PM >To: 'dev@sling.apache.org' >Subject: [VOTE] Release Apache Sling CAConfig SPI 1.3.0, CAConfig Impl >1.3.0, CAConfig Mock Plugin 1.1.0

[jira] [Updated] (SLING-6694) Replace commons.json usage in org.apache.sling.jcr.contentloader

[ https://issues.apache.org/jira/browse/SLING-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-6694: -- Attachment: SLING-6694.patch This one was a pit painful but I got it to work with the new commons

[jira] [Updated] (SLING-6694) Replace commons.json usage in org.apache.sling.jcr.contentloader

[ https://issues.apache.org/jira/browse/SLING-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-6694: -- Labels: patch-available (was: ) > Replace commons.json usage in org.apache.sling.jcr.contentloader >

[jira] [Commented] (SLING-6679) Replace usage of org.apache.sling.commons.json.*

[ https://issues.apache.org/jira/browse/SLING-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15939343#comment-15939343 ] Karl Pauls commented on SLING-6679: --- I just converted (i.e., provided a patch for) the contentloader

Re: Do we have a mechanism to retire modules?

Hi Bertrand, the attic folder already exists, it is at: https://svn.apache.org/repos/asf/sling/attic/ so its not in trunk, which I think makes sense and we have been using it for quiet some time :) Regards Carsten Bertrand Delacretaz wrote > Hi, > > Thanks Carsten and Robert for the info! >

Re: [VOTE] Retire o.a.s.servlets.compat module to the Sling Attic

+1 Konrad > On 23 Mar 2017, at 10:46, Bertrand Delacretaz wrote: > > Hi, > > I'd like to retire our bundles/servlets/compat module by moving it > under https://svn.apache.org/repos/asf/sling/attic/ > > As mentioned at SLING-6686 that module is using commons.json which

Re: Do we have a mechanism to retire modules?

Ignore my answer...I should have read your readme before replying :) Carsten Carsten Ziegeler wrote > Hi Bertrand, > > the attic folder already exists, it is at: > https://svn.apache.org/repos/asf/sling/attic/ > > so its not in trunk, which I think makes sense and we have been using it > for

[jira] [Commented] (SLING-6679) Replace usage of org.apache.sling.commons.json.*

[ https://issues.apache.org/jira/browse/SLING-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938046#comment-15938046 ] Karl Pauls commented on SLING-6679: --- Ok, I will create a new org.apache.sling.commons.johnzon bundle for

RE: [VOTE] Retire o.a.s.servlets.compat module to the Sling Attic

+1

[jira] [Created] (SLING-6700) Implement johnzon bundle

Karl Pauls created SLING-6700: - Summary: Implement johnzon bundle Key: SLING-6700 URL: https://issues.apache.org/jira/browse/SLING-6700 Project: Sling Issue Type: Sub-task Components:

[jira] [Commented] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938066#comment-15938066 ] Feike Visser commented on SLING-6637: - I like to reopen this issue, and like to see if we can log

[jira] [Updated] (SLING-6636) Access request-attributes directly in Sightly

[ https://issues.apache.org/jira/browse/SLING-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feike Visser updated SLING-6636: Description: With https://issues.apache.org/jira/browse/SLING-5812 you can now pass in

[jira] [Commented] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938112#comment-15938112 ] Robert Munteanu commented on SLING-6637: Shouldn't that be passed to a use bean as an argument,

Logging config to combat "log spamming"

Hi, Is there are way of configuring the logging service so that it doesn't repeatedly spam the logs with the same message or extremely high volume messages. This may seem like an odd request, but when a Sling instance running an application goes haywire spitting out massive exception stack traces.

[jira] [Updated] (SLING-6698) Thread Usage Health Check

[ https://issues.apache.org/jira/browse/SLING-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georg Henzler updated SLING-6698: - Description: This health check should use java.lang.management.ThreadMXBean to provide the

[jira] [Updated] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feike Visser updated SLING-6637: Description: Following code: {code} {code} You get now the following exception: {code}

Re: [VOTE] Retire o.a.s.servlets.compat module to the Sling Attic

+1 regards, Karl On Thu, Mar 23, 2017 at 10:51 AM, Carsten Ziegeler wrote: > +1 > > > > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org -- Karl Pauls karlpa...@gmail.com

[jira] [Comment Edited] (SLING-6679) Replace usage of org.apache.sling.commons.json.*

[ https://issues.apache.org/jira/browse/SLING-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938046#comment-15938046 ] Karl Pauls edited comment on SLING-6679 at 3/23/17 10:07 AM: - Ok, I will

[jira] [Issue Comment Deleted] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feike Visser updated SLING-6637: Comment: was deleted (was: Reopening after discussing with [~gwalt]) > [htl] data-sly-use should

[jira] [Updated] (SLING-6698) Thread Usage Health Check

[ https://issues.apache.org/jira/browse/SLING-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georg Henzler updated SLING-6698: - Fix Version/s: Health Check Support 1.0.6 > Thread Usage Health Check > -

[jira] [Reopened] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feike Visser reopened SLING-6637: - Reopening after discussing with [~gwalt] > [htl] data-sly-use should not raise an exception when

[VOTE] Retire o.a.s.servlets.compat module to the Sling Attic

Hi, I'd like to retire our bundles/servlets/compat module by moving it under https://svn.apache.org/repos/asf/sling/attic/ As mentioned at SLING-6686 that module is using commons.json which should be replaced. But I don't think we intend to develop that module further, so we might as well

Re: [VOTE] Retire o.a.s.servlets.compat module to the Sling Attic

+1 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

Re: [VOTE] Retire o.a.s.servlets.compat module to the Sling Attic

On Thu, 2017-03-23 at 10:46 +0100, Bertrand Delacretaz wrote: > Please vote to accept this retirement, this majority vote is open for > at least 72 hours. +1 Robert signature.asc Description: This is a digitally signed message part

[jira] [Comment Edited] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938066#comment-15938066 ] Feike Visser edited comment on SLING-6637 at 3/23/17 10:28 AM: --- I like to

[jira] [Commented] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938101#comment-15938101 ] Robert Munteanu commented on SLING-6637: Out curiosity, what are these use cases? I am not a very

[jira] [Comment Edited] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938116#comment-15938116 ] Feike Visser edited comment on SLING-6637 at 3/23/17 11:11 AM: --- data-sly-use

[jira] [Commented] (SLING-6685) Replace commons.json usage in org.apache.sling.xss

[ https://issues.apache.org/jira/browse/SLING-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938056#comment-15938056 ] Karl Pauls commented on SLING-6685: --- Ok, I will provide a new patch that add the supports-comments flag

[jira] [Comment Edited] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938066#comment-15938066 ] Feike Visser edited comment on SLING-6637 at 3/23/17 11:11 AM: --- I like to

Re: Logging config to combat "log spamming"

Hi, On Thu, 2017-03-23 at 11:03 +, Ian Boston wrote: > Hi, > Is there are way of configuring the logging service so that it > doesn't > repeatedly spam the logs with the same message or extremely high > volume > messages. This may seem like an odd request, but when a Sling > instance >

[jira] [Commented] (SLING-6679) Replace usage of org.apache.sling.commons.json.*

[ https://issues.apache.org/jira/browse/SLING-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938139#comment-15938139 ] Karl Pauls commented on SLING-6679: --- [~sseif...@pro-vision.de] I agree, we need to double check that -

[jira] [Created] (SLING-6699) Clearly describe drawbacks of mounting servlets by path

Robert Munteanu created SLING-6699: -- Summary: Clearly describe drawbacks of mounting servlets by path Key: SLING-6699 URL: https://issues.apache.org/jira/browse/SLING-6699 Project: Sling

[jira] [Resolved] (SLING-6699) Clearly describe drawbacks of mounting servlets by path

[ https://issues.apache.org/jira/browse/SLING-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-6699. Resolution: Fixed

[jira] [Commented] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938106#comment-15938106 ] Feike Visser commented on SLING-6637: - Sure! For example there is a productPath saved, and you want to

Re: Do we have a mechanism to retire modules?

Hi, Thanks Carsten and Robert for the info! I have now created https://svn.apache.org/repos/asf/sling/trunk/attic with just a README that has those pointers, to hopefully make it easier to find our retired modules. -Bertrand On Wed, Mar 22, 2017 at 6:23 PM, Robert Munteanu

[jira] [Commented] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938116#comment-15938116 ] Feike Visser commented on SLING-6637: - data-sly-use now also supports the resolving from a path to a

[jira] [Commented] (SLING-6679) Replace usage of org.apache.sling.commons.json.*

[ https://issues.apache.org/jira/browse/SLING-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938127#comment-15938127 ] Stefan Seifert commented on SLING-6679: --- another small point on the patches: JsonReader, JsonParser,

[jira] [Commented] (SLING-6686) Replace commons.json usage in org.apache.sling.servlets.compat

[ https://issues.apache.org/jira/browse/SLING-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938006#comment-15938006 ] Bertrand Delacretaz commented on SLING-6686: I have started the vote on our dev list, to

[jira] [Updated] (SLING-6686) Replace commons.json usage in org.apache.sling.servlets.compat (or retire that module)

[ https://issues.apache.org/jira/browse/SLING-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-6686: --- Summary: Replace commons.json usage in org.apache.sling.servlets.compat (or retire

[jira] [Assigned] (SLING-6686) Replace commons.json usage in org.apache.sling.servlets.compat

[ https://issues.apache.org/jira/browse/SLING-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz reassigned SLING-6686: -- Assignee: Bertrand Delacretaz > Replace commons.json usage in

Re: [VOTE] Release Apache Sling CAConfig SPI 1.3.0, CAConfig Impl 1.3.0, CAConfig Mock Plugin 1.1.0

+1 regards, Karl On Mon, Mar 20, 2017 at 11:51 PM, Stefan Seifert wrote: > Hi, > > Apache Sling Context-Aware Configuration SPI 1.3.0 (2 issues) > https://issues.apache.org/jira/browse/SLING/fixforversion/12338849 > > Apache Sling Context-Aware Configuration

[jira] [Commented] (SLING-6702) Make MetricsService accessible as easily as a Logger

[ https://issues.apache.org/jira/browse/SLING-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15939853#comment-15939853 ] Chetan Mehrotra commented on SLING-6702: [~bdelacretaz] Changes look ok. Probably we need to

[jira] [Commented] (SLING-6702) Make MetricsService accessible as easily as a Logger

[ https://issues.apache.org/jira/browse/SLING-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15939847#comment-15939847 ] Chetan Mehrotra commented on SLING-6702: [~fmeschbe] The Metrics instance created from

[jira] [Assigned] (SLING-6694) Replace commons.json usage in org.apache.sling.jcr.contentloader

[ https://issues.apache.org/jira/browse/SLING-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-6694: - Assignee: Karl Pauls > Replace commons.json usage in org.apache.sling.jcr.contentloader >

[jira] [Commented] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938241#comment-15938241 ] Feike Visser commented on SLING-6637: - But we are also not throwing exceptions when you access a

[jira] [Commented] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938280#comment-15938280 ] Konrad Windszus commented on SLING-6637: your example {code} {code} is equivalent to {code}

[jira] [Comment Edited] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938154#comment-15938154 ] Konrad Windszus edited comment on SLING-6637 at 3/23/17 11:52 AM: -- bq. I

[jira] [Commented] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938154#comment-15938154 ] Konrad Windszus commented on SLING-6637: bq. I like to reopen this issue, and like to see if we

Re: [VOTE] Release Apache Sling Testing OSGi Mock 2.2.4, OSGi Mock 1.9.4

+1 regards, Karl On Thu, Mar 23, 2017 at 12:36 PM, Robert Munteanu wrote: > On Mon, 2017-03-20 at 11:33 +, Stefan Seifert wrote: >> Please vote to approve this release: > > +1 > > Robert -- Karl Pauls karlpa...@gmail.com

[jira] [Commented] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938206#comment-15938206 ] Feike Visser commented on SLING-6637: - There is a difference between resolving a Java-class or a

RE: [VOTE] Release Apache Sling Testing OSGi Mock 2.2.4, OSGi Mock 1.9.4 - vote missing

one binding vote is missing - anyone? stefan >-Original Message- >From: Stefan Seifert [mailto:sseif...@pro-vision.de] >Sent: Monday, March 20, 2017 12:33 PM >To: 'dev@sling.apache.org' >Subject: [VOTE] Release Apache Sling Testing OSGi Mock 2.2.4, OSGi Mock >1.9.4 > >Hi, > >Apache

Re: [VOTE] Release Apache Sling Testing OSGi Mock 2.2.4, OSGi Mock 1.9.4

On Mon, 2017-03-20 at 11:33 +, Stefan Seifert wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

[jira] [Commented] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938257#comment-15938257 ] Konrad Windszus commented on SLING-6637: Non existing properties used in EL don't throw exceptions

[jira] [Closed] (SLING-6641) osgi-mock: MockOsgi.setConfigForPid convenience method

[ https://issues.apache.org/jira/browse/SLING-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert closed SLING-6641. - > osgi-mock: MockOsgi.setConfigForPid convenience method >

[jira] [Closed] (SLING-6586) osgi-mock: Loading SCR metadata fails for components with name != class name

[ https://issues.apache.org/jira/browse/SLING-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert closed SLING-6586. - > osgi-mock: Loading SCR metadata fails for components with name != class name >

[jira] [Closed] (SLING-6672) osgi-mock: Switch to OSGi annotations

[ https://issues.apache.org/jira/browse/SLING-6672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert closed SLING-6672. - > osgi-mock: Switch to OSGi annotations > - > >

[jira] [Closed] (SLING-6650) osgi-mock: Fallback to component name when service.pid property not set in SCR metadata

[ https://issues.apache.org/jira/browse/SLING-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert closed SLING-6650. - > osgi-mock: Fallback to component name when service.pid property not set in > SCR metadata >

[jira] [Comment Edited] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938257#comment-15938257 ] Konrad Windszus edited comment on SLING-6637 at 3/23/17 1:11 PM: - Non

[jira] [Commented] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938260#comment-15938260 ] Feike Visser commented on SLING-6637: - This is also a block statement: {code} data-sly-test.x="${

[RESULT] [VOTE] Release Apache Sling Testing OSGi Mock 2.2.4, OSGi Mock 1.9.4

Hi, The vote has passed with the following result : +1 (binding): Stefan Seifert, Daniel Klco, Robert Munteanu, Karl Pauls I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. stefan

[RESULT] [VOTE] Release Apache Sling JCR Content Parser 1.0.0

Hi, The vote has passed with the following result : +1 (binding): Stefan Seifert, Robert Munteanu, Carsten Ziegeler I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. stefan

Question about Initial Content Loading

The documentation at https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html is a bit confusing to me and I would like to clean this up. Several tables have a column called "Entry" but this sometimes seems to refer to a "bundle header entry" and sometimes to a

[jira] [Comment Edited] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938206#comment-15938206 ] Feike Visser edited comment on SLING-6637 at 3/23/17 12:42 PM: --- There is a

[jira] [Commented] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938233#comment-15938233 ] Konrad Windszus commented on SLING-6637: I am strongly opposed to the idea of hiding the

Re: [VOTE] Release Apache Sling JCR Content Parser 1.0.0

@Stefan: I see that you just closed https://issues.apache.org/jira/browse/SLING-6592 and that this has obviously been released. Can you still quickly comment on my feedback given below? Do you want me to open a dedicated ticket in JIRA for that, so that we can fix that in a new version?

[jira] [Created] (SLING-6701) Clarify documentation for JCR Content Loader (https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html)

Konrad Windszus created SLING-6701: -- Summary: Clarify documentation for JCR Content Loader (https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html) Key: SLING-6701 URL:

[jira] [Commented] (SLING-6701) Clarify documentation for JCR Content Loader (https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html)

[ https://issues.apache.org/jira/browse/SLING-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938789#comment-15938789 ] Stefan Seifert commented on SLING-6701: --- the updates make sense to me (but do not forget to add the

[jira] [Commented] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938564#comment-15938564 ] Feike Visser commented on SLING-6637: - I see then the following pattern to avoid exceptions: {code}

[jira] [Commented] (SLING-6703) Sling Post Processor: Do not create new exception in AbstractPostResponse.setError

[ https://issues.apache.org/jira/browse/SLING-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938585#comment-15938585 ] Konrad Windszus commented on SLING-6703: Also I don't quite get why for the example from

[jira] [Comment Edited] (SLING-6703) Sling Post Processor: Do not create new exception in AbstractPostResponse.setError

[ https://issues.apache.org/jira/browse/SLING-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938585#comment-15938585 ] Konrad Windszus edited comment on SLING-6703 at 3/23/17 3:40 PM: - Also I

[jira] [Assigned] (SLING-6703) Sling Post Processor: Do not create new exception in AbstractPostResponse.setError

[ https://issues.apache.org/jira/browse/SLING-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-6703: -- Assignee: Antonio Sanso (was: Konrad Windszus) > Sling Post Processor: Do not create

Re: Logging config to combat "log spamming"

As Robert said you can use the DuplicateMessageFilter. For now you would need to configure it in a logback.xml and use that in Sling [1]. Chetan Mehrotra [1] https://sling.apache.org/documentation/development/logging.html#external-config-file On Thu, Mar 23, 2017 at 4:43 PM, Robert Munteanu

[jira] [Closed] (SLING-6592) JCR Content Parser

[ https://issues.apache.org/jira/browse/SLING-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert closed SLING-6592. - > JCR Content Parser > -- > > Key: SLING-6592 > URL:

RE: [VOTE] Release Apache Sling JCR Content Parser 1.0.0

well, the enum value is released as part of the public API, so we cannot change it now without breaking the API. it makes sense to update the Javadoc to document what exact format is expected here (you can do it directly). if we later want to add other formats we have to create new enum values.

[jira] [Commented] (SLING-6703) Sling Post Processor: Do not create new exception in AbstractPostResponse.setError

[ https://issues.apache.org/jira/browse/SLING-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938445#comment-15938445 ] Konrad Windszus commented on SLING-6703: [~asanso] The fix from you in SLING-4415 prevents the

[jira] [Commented] (SLING-6700) Implement johnzon bundle

[ https://issues.apache.org/jira/browse/SLING-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938437#comment-15938437 ] Karl Pauls commented on SLING-6700: --- I added a first pass on a wrapper library in r1788254. I deployed a

[jira] [Commented] (SLING-6679) Replace usage of org.apache.sling.commons.json.*

[ https://issues.apache.org/jira/browse/SLING-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938441#comment-15938441 ] Karl Pauls commented on SLING-6679: --- I created a johnzon bundle in commons that exports javax.json. See

[jira] [Updated] (SLING-6701) Clarify documentation for JCR Content Loader (https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html)

[ https://issues.apache.org/jira/browse/SLING-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6701: --- Attachment: SLING-6701-v01.patch [~bdelacretaz],[~cziegeler],[~olli]: Since you contributed

[jira] [Commented] (SLING-6701) Clarify documentation for JCR Content Loader (https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html)

[ https://issues.apache.org/jira/browse/SLING-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938325#comment-15938325 ] Bertrand Delacretaz commented on SLING-6701: That's painful to read, could you attach the

Re: Logging config to combat "log spamming"

Thank you all. Looks like that might do the job provided the log messages are parameterised. Best Regards Ian On 23 March 2017 at 11:23, Chetan Mehrotra wrote: > As Robert said you can use the DuplicateMessageFilter. For now you > would need to configure it in a

[jira] [Commented] (SLING-6701) Clarify documentation for JCR Content Loader (https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html)

[ https://issues.apache.org/jira/browse/SLING-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938404#comment-15938404 ] Bertrand Delacretaz commented on SLING-6701: If things are unclear IMO we need tests to

[jira] [Created] (SLING-6703) Sling Post Processor: Do not create new exception in AbstractPostResponse.setError

Konrad Windszus created SLING-6703: -- Summary: Sling Post Processor: Do not create new exception in AbstractPostResponse.setError Key: SLING-6703 URL: https://issues.apache.org/jira/browse/SLING-6703

[jira] [Created] (SLING-6702) Make MetricsService accessible as easily as a Logger

Bertrand Delacretaz created SLING-6702: -- Summary: Make MetricsService accessible as easily as a Logger Key: SLING-6702 URL: https://issues.apache.org/jira/browse/SLING-6702 Project: Sling

[jira] [Updated] (SLING-6701) Clarify documentation for JCR Content Loader (https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html)

[ https://issues.apache.org/jira/browse/SLING-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6701: --- Attachment: content-loading-jcr-contentloader-SLING-6701-v01.html Yes, I just did, but I am

[jira] [Commented] (SLING-6703) Sling Post Processor: Do not create new exception in AbstractPostResponse.setError

[ https://issues.apache.org/jira/browse/SLING-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938420#comment-15938420 ] Konrad Windszus commented on SLING-6703: This would be also closer to what the {{JSONResponse}}

[jira] [Commented] (SLING-6703) Sling Post Processor: Do not create new exception in AbstractPostResponse.setError

[ https://issues.apache.org/jira/browse/SLING-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938431#comment-15938431 ] Konrad Windszus commented on SLING-6703: This is a regression of

[jira] [Comment Edited] (SLING-6703) Sling Post Processor: Do not create new exception in AbstractPostResponse.setError

[ https://issues.apache.org/jira/browse/SLING-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938445#comment-15938445 ] Konrad Windszus edited comment on SLING-6703 at 3/23/17 2:33 PM: -

[jira] [Updated] (SLING-6515) Sling Post Processor considering validation model as well

[ https://issues.apache.org/jira/browse/SLING-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6515: --- Attachment: SLING-6515-v01.patch Attached is a WIP patch providing a basic PostProcessor

[jira] [Comment Edited] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938181#comment-15938181 ] Radu Cotescu edited comment on SLING-6637 at 3/23/17 12:18 PM: --- I tend to

[jira] [Commented] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938181#comment-15938181 ] Radu Cotescu commented on SLING-6637: - I tend to agree with Robert's view here: why do we want to move

[jira] [Assigned] (SLING-6515) Sling Post Processor considering validation model as well

[ https://issues.apache.org/jira/browse/SLING-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-6515: -- Assignee: Konrad Windszus > Sling Post Processor considering validation model as well

[jira] [Commented] (SLING-6703) Sling Post Processor: Do not create new exception in AbstractPostResponse.setError

[ https://issues.apache.org/jira/browse/SLING-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938667#comment-15938667 ] Konrad Windszus commented on SLING-6703: I just redid the test with an AEM 6.3 with a patched POST

[jira] [Commented] (SLING-6702) Make MetricsService accessible as easily as a Logger

[ https://issues.apache.org/jira/browse/SLING-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938647#comment-15938647 ] Bertrand Delacretaz commented on SLING-6702: Implemented as of revision 1788272. [~chetanm]

[jira] [Comment Edited] (SLING-6703) Sling Post Processor: Do not create new exception in AbstractPostResponse.setError

[ https://issues.apache.org/jira/browse/SLING-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938667#comment-15938667 ] Konrad Windszus edited comment on SLING-6703 at 3/23/17 4:10 PM: - I just

[jira] [Comment Edited] (SLING-6703) Sling Post Processor: Do not create new exception in AbstractPostResponse.setError

[ https://issues.apache.org/jira/browse/SLING-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938667#comment-15938667 ] Konrad Windszus edited comment on SLING-6703 at 3/23/17 4:12 PM: - I just

[jira] [Comment Edited] (SLING-6701) Clarify documentation for JCR Content Loader (https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html)

[ https://issues.apache.org/jira/browse/SLING-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938697#comment-15938697 ] Konrad Windszus edited comment on SLING-6701 at 3/23/17 4:25 PM: - Turns

[jira] [Commented] (SLING-6701) Clarify documentation for JCR Content Loader (https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html)

[ https://issues.apache.org/jira/browse/SLING-6701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15938697#comment-15938697 ] Konrad Windszus commented on SLING-6701: Turns out I got one directive wrong ({{path=...}} instead

[jira] [Updated] (SLING-6703) Sling Post Processor: Do not create hide original exception in AbstractPostResponse.setError

[ https://issues.apache.org/jira/browse/SLING-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6703: --- Summary: Sling Post Processor: Do not create hide original exception in

[jira] [Updated] (SLING-6703) Sling Post Servlet: Do not create hide original exception in AbstractPostResponse.setError

[ https://issues.apache.org/jira/browse/SLING-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6703: --- Summary: Sling Post Servlet: Do not create hide original exception in

  1   2   >