Re: Sling Posthandling - thougts about the current behavior

Hi everyone, I stand corrected, such a feature would not remove the SlingServlets entirely from the picture, since they are still needed for GET requests. +1 for the "pipeline of operations" concept. __ Dan -- View this message in context: http://apache-sling.73963.n3.nabble.com/Sling-Posth

Re: [Status Update] Apache Cassandra backend for Sling

Hi, Have you tried the TypeInferringSerializer for the value serializer ? That claims to be detect what the column value is based on the Byte array. Failing that, I would consider making everything byte[] and using your own serializer that writes and read values to a byte[] using DataInputStream D

Build failed in Jenkins: sling-trunk-1.7 #77

See Changes: [justin] SLING-2937 - using Long.valueOf() in getLong() to ensure correct parsing -- [...truncated 29274 lines...] at org.sonatype.aether.impl.internal.TrackingFileManager.lo

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #77

See

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling JCR Installer #77

See

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #77

See

[jira] [Commented] (SLING-2937) Sling JSONObject getlong incorrect parsing

[ https://issues.apache.org/jira/browse/SLING-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695039#comment-13695039 ] Nirmal commented on SLING-2937: --- Yes, you are correct. Yet if this is long parsable string,

Jenkins build is unstable: sling-trunk-1.6 #1707

See

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Launchpad Testing #1707

See

Jenkins build is unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #1707

See

[jira] [Updated] (SLING-2937) Sling JSONObject getlong incorrect parsing

[ https://issues.apache.org/jira/browse/SLING-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-2937: -- Component/s: (was: General) Commons Fix Version/s: Commons JSON 2.0

[jira] [Resolved] (SLING-2937) Sling JSONObject getlong incorrect parsing

[ https://issues.apache.org/jira/browse/SLING-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-2937. --- Resolution: Fixed fixed in 1497518 But I would really suggest using properly formed JSON.

[jira] [Assigned] (SLING-2937) Sling JSONObject getlong incorrect parsing

[ https://issues.apache.org/jira/browse/SLING-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson reassigned SLING-2937: - Assignee: Justin Edelson > Sling JSONObject getlong incorrect parsing > -

[jira] [Commented] (SLING-2937) Sling JSONObject getlong incorrect parsing

[ https://issues.apache.org/jira/browse/SLING-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694976#comment-13694976 ] Justin Edelson commented on SLING-2937: --- Don't you mean {code} String jsonStr1 = "{\

Re: [Status Update] Apache Cassandra backend for Sling

Hi Ian, I am having a problem with CQL.. For example: CqlQuery** cqlQuery = new CqlQuery* *(keyspace, new StringSerializer(),new StringSerializer(), new LongSerializer(); cqlQuery.setQuery("insert into mytable (KEY,password,gender,userid) values (3,'pass1','male',34);"); Qu

[jira] [Updated] (SLING-2937) Sling JSONObject getlong incorrect parsing

[ https://issues.apache.org/jira/browse/SLING-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nirmal updated SLING-2937: -- Affects Version/s: Commons JSON 2.0.6 > Sling JSONObject getlong incorrect parsing > --

[jira] [Created] (SLING-2937) Sling JSONObject getlong incorrect parsing

Nirmal created SLING-2937: - Summary: Sling JSONObject getlong incorrect parsing Key: SLING-2937 URL: https://issues.apache.org/jira/browse/SLING-2937 Project: Sling Issue Type: Bug Componen

[DISCUSS] SLING-2936 - passing selector as POST parameter

Recently there have been some concerns raised about using selectors to direct a request between servlets when handling a POST request. Strictly speaking, a selector in the URI should be a way of indicating the way that the response should be rendered, not how the request should be handled. That sa

[jira] [Commented] (SLING-2936) allow selectors to be passed via request parameter instead of URL

[ https://issues.apache.org/jira/browse/SLING-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694810#comment-13694810 ] Justin Edelson commented on SLING-2936: --- Patch here: http://codereview.appspot.com/1

[jira] [Created] (SLING-2936) allow selectors to be passed via request parameter instead of URL

Justin Edelson created SLING-2936: - Summary: allow selectors to be passed via request parameter instead of URL Key: SLING-2936 URL: https://issues.apache.org/jira/browse/SLING-2936 Project: Sling

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

See Changes: [bdelacretaz] SLING-2822 - inactive.bundles.count optionally takes a list of bundles to check -- [...truncated 9870 lines...] main: [INFO] --- maven-antrun-plugin:1.7:run (set-bu

Jenkins build is back to normal : sling-trunk-1.6 » Sling Adapter Annotations #1706

See

Jenkins build is back to normal : sling-trunk-1.6 » Apache Sling Jackrabbit UserManager Support #1706

See

Re: Sling Posthandling - thougts about the current behavior

On Thu, Jun 27, 2013 at 2:03 PM, Daniel Platon wrote: > ...I think such a feature would make binding the SlingServlets to > resource type obsolete... Now you got my attention...but you'll need to clarify your use case and ideas I guess ;-) -Bertrand

Re: Sling Posthandling - thougts about the current behavior

Hi everyone, Although I don't have that much experience with Sling, I'd +1 any feature that allows the developer to attach behaviour to content (at least this is what a PostProcessor sounds to me). I made extensive use of such a feature when I use to developer content management application on Doc

Jenkins build is still unstable: sling-trunk-1.7 #76

See

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #76

See

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing WAR version #76

See

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Sample Integration Tests #76

See

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #76

See

RE: Sling Posthandling - thougts about the current behavior

+1 That would be very nice. Jeff. > -Original Message- > From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] > Sent: 27 June 2013 08:26 > To: dev@sling.apache.org > Subject: Re: Sling Posthandling - thougts about the current behavior > > On Thu, Jun 27, 2013 at 12:52 AM, Ian Bost

Re: Sling Posthandling - thougts about the current behavior

On Thu, Jun 27, 2013 at 12:52 AM, Ian Boston wrote: > ...I have long thought SlingPostOperations should be registered against the > resource type in the same way SlingServlets are registered against a > resource type Absolutely - there are other things (validation etc.) where we would benefit