[jira] [Updated] (SLING-5827) HeltthCheckMetadata ClassCast Exception

[ https://issues.apache.org/jira/browse/SLING-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivo Leitão updated SLING-5827: -- Description: I'm getting a classcastexception in the healthcheck component. This is happenning only

[jira] [Updated] (SLING-5827) HeltthCheckMetadata ClassCast Exception

[ https://issues.apache.org/jira/browse/SLING-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivo Leitão updated SLING-5827: -- Description: I'm getting a classcastexception in the healthcheck component. This is happenning only

[jira] [Created] (SLING-5827) HeltthCheckMetadata ClassCast Exception

Ivo Leitão created SLING-5827: - Summary: HeltthCheckMetadata ClassCast Exception Key: SLING-5827 URL: https://issues.apache.org/jira/browse/SLING-5827 Project: Sling Issue Type: Bug

[jira] [Resolved] (SLING-5753) Use.init() not invoked for Java Use object which is also a Sling Model

[ https://issues.apache.org/jira/browse/SLING-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-5753. - Resolution: Won't Fix Assignee: Radu Cotescu > Use.init() not invoked for Java Use object

[jira] [Commented] (SLING-5753) Use.init() not invoked for Java Use object which is also a Sling Model

[ https://issues.apache.org/jira/browse/SLING-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366344#comment-15366344 ] Radu Cotescu commented on SLING-5753: - I have to agree with Justin's comment \[0\]: implementing this

[jira] [Commented] (SLING-5632) [Sightly] URI manipulation options that process a path should not alter URIs that don't provide path information

[ https://issues.apache.org/jira/browse/SLING-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366180#comment-15366180 ] Radu Cotescu commented on SLING-5632: - [~fvisser], I've changed the issue's summary in order to better

[jira] [Assigned] (SLING-5632) [sightly] Support for external links with @ extension

[ https://issues.apache.org/jira/browse/SLING-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu reassigned SLING-5632: --- Assignee: Radu Cotescu > [sightly] Support for external links with @ extension >

[jira] [Updated] (SLING-5632) [Sightly] URI manipulation options that process a path should not alter URIs that don't provide path information

[ https://issues.apache.org/jira/browse/SLING-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-5632: Summary: [Sightly] URI manipulation options that process a path should not alter URIs that don't

[jira] [Updated] (SLING-5632) [sightly] Support for external links with @ extension

[ https://issues.apache.org/jira/browse/SLING-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-5632: Fix Version/s: Scripting Sightly Engine 1.0.20 > [sightly] Support for external links with @

[jira] [Updated] (SLING-5632) [sightly] Support for external links with @ extension

[ https://issues.apache.org/jira/browse/SLING-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-5632: Description: Code example {noformat} Our link {noformat} This normally works ok, but in case

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366120#comment-15366120 ] Bertrand Delacretaz commented on SLING-5824: bq. This to me seem like a great bypass for out

[jira] [Commented] (SLING-5692) Add Integration Tests for Scripting FreeMarker

[ https://issues.apache.org/jira/browse/SLING-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366129#comment-15366129 ] Oliver Lietz commented on SLING-5692: - module {{org.apache.sling.scripting.freemarker.it}} merged into

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366125#comment-15366125 ] Christanto commented on SLING-5824: --- But this is just another GET request. I don't understand. >

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366111#comment-15366111 ] Carsten Ziegeler commented on SLING-5824: - I was wondering about the same as Antonio - as you say

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366105#comment-15366105 ] Christanto commented on SLING-5824: --- This is about converting POST to GET, not the other way around. >

[jira] [Updated] (SLING-5692) Add Integration Tests for Scripting FreeMarker

[ https://issues.apache.org/jira/browse/SLING-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-5692: Fix Version/s: (was: Scripting FreeMarker 1.0.2) Scripting FreeMarker 1.0.0

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366094#comment-15366094 ] Antonio Sanso commented on SLING-5824: -- just my 0.02 $ . We really need to be careful here. This to

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366061#comment-15366061 ] Christanto commented on SLING-5824: --- Yes the script is trivial. The code at issue description is pretty

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366015#comment-15366015 ] Bertrand Delacretaz commented on SLING-5824: bq. Both POST.jsp above have identical code,

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366010#comment-15366010 ] Carsten Ziegeler commented on SLING-5824: - With a generic filter you punish every request by

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365997#comment-15365997 ] Christanto commented on SLING-5824: --- bq. IIUC this happens in client code, so what prevents you from

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365991#comment-15365991 ] Bertrand Delacretaz commented on SLING-5824: bq. If the URL is not long we are using GET. If

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365968#comment-15365968 ] Christanto commented on SLING-5824: --- bq. But once you start using POST from client, as you mentioned in

[jira] [Commented] (SLING-5824) Servlet Filter to do POST tunnelling to GET

[ https://issues.apache.org/jira/browse/SLING-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365947#comment-15365947 ] Amit Gupta commented on SLING-5824: --- >GET is still preferable for the use case, as it allows bookmarking

Re: Javadoc and Java 8

On Thu, Jul 7, 2016 at 9:41 AM, Carsten Ziegeler wrote: > ...Fixing the javadoc for java 8 is not the nicest task in the world, but > you can usually do this fairly quickly I agree with that - the problem is that this pollutes diffs when comparing the code of a previous

[jira] [Comment Edited] (SLING-5682) special json array import for sling post servlet to post orderered structures

[ https://issues.apache.org/jira/browse/SLING-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365842#comment-15365842 ] Nicolas Peltier edited comment on SLING-5682 at 7/7/16 9:02 AM: thx

[jira] [Commented] (SLING-5682) special json array import for sling post servlet to post orderered structures

[ https://issues.apache.org/jira/browse/SLING-5682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365842#comment-15365842 ] Nicolas Peltier commented on SLING-5682: thx [~bdelacretaz]! > special json array import for

[jira] [Updated] (SLING-5826) add a change layer for sling pipes that modify content

[ https://issues.apache.org/jira/browse/SLING-5826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-5826: --- Description: would be nice to have a layer like operations & modification for post servlet

[jira] [Created] (SLING-5826) add a change layer for sling pipes that modify content

Nicolas Peltier created SLING-5826: -- Summary: add a change layer for sling pipes that modify content Key: SLING-5826 URL: https://issues.apache.org/jira/browse/SLING-5826 Project: Sling

Re: Javadoc and Java 8

Carsten Ziegeler wrote > Oliver Lietz wrote >> hi all, >> >> Javadoc became much stricter with doclint in Java 8 and releasing some >> (most?) >> of our modules with Java 8 will fail with Javadoc errors. >> >> Should Javadoc errors block a release? >> >> Should we enable Javadoc for regular

Re: Javadoc and Java 8

Oliver Lietz wrote > hi all, > > Javadoc became much stricter with doclint in Java 8 and releasing some > (most?) > of our modules with Java 8 will fail with Javadoc errors. > > Should Javadoc errors block a release? > > Should we enable Javadoc for regular builds? > > We can disable doclint