[jira] [Resolved] (SLING-8091) Add an option to specify the framework for analysing features
[ https://issues.apache.org/jira/browse/SLING-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-8091. - Resolution: Fixed Added in rev 0b00a5b The framework can be specified as a dependency globally and be overridden locally per scan > Add an option to specify the framework for analysing features > - > > Key: SLING-8091 > URL: https://issues.apache.org/jira/browse/SLING-8091 > Project: Sling > Issue Type: Improvement > Components: Maven Plugins and Archetypes >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: slingfeature-maven-plugin 1.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SLING-8091) Add an option to specify the framework for analysing features
Carsten Ziegeler created SLING-8091: --- Summary: Add an option to specify the framework for analysing features Key: SLING-8091 URL: https://issues.apache.org/jira/browse/SLING-8091 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: slingfeature-maven-plugin 1.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SLING-7920) IllegalStateException in Model-to-Feature converter for multiple repoinit sections
[
https://issues.apache.org/jira/browse/SLING-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-7920.
-
Resolution: Fixed
> IllegalStateException in Model-to-Feature converter for multiple repoinit
> sections
> --
>
> Key: SLING-7920
> URL: https://issues.apache.org/jira/browse/SLING-7920
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Feature Model Converter 0.2.2
>
>
> Trying to convert the sling-org-apache-sling-starter I get the below
> exception, as due to SLING-7919 the sling-event feature there contains two
> :repoinit sections.
> {code}
> Exception in thread "main" java.lang.IllegalStateException
> at org.apache.sling.feature.Extension.getText(Extension.java:111)
> at
> org.apache.sling.feature.modelconverter.ProvisioningToFeature.buildFromFeature(ProvisioningToFeature.java:444)
> at
> org.apache.sling.feature.modelconverter.ProvisioningToFeature.buildFeatures(ProvisioningToFeature.java:477)
> at
> org.apache.sling.feature.modelconverter.ProvisioningToFeature.convert(ProvisioningToFeature.java:113)
> at org.apache.sling.feature.modelconverter.impl.Main.main(Main.java:195)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SLING-8066) MockProperty.setValue(final String[] newValues) throws null pointer exception
[ https://issues.apache.org/jira/browse/SLING-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683277#comment-16683277 ] Pankaj Parashar commented on SLING-8066: [~sseif...@pro-vision.de], Yes, you are correct, the real jcr implementation removes property if set null. This behaviour should solve my problem. Please go ahead with your PR. > MockProperty.setValue(final String[] newValues) throws null pointer exception > -- > > Key: SLING-8066 > URL: https://issues.apache.org/jira/browse/SLING-8066 > Project: Sling > Issue Type: Bug > Components: Testing >Affects Versions: Testing JCR Mock 1.4.0 >Reporter: Pankaj Parashar >Assignee: Stefan Seifert >Priority: Blocker > Fix For: Testing JCR Mock 1.4.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > There is no null check in this api method. In our case product code is > passing a null value in the below form for a multivalve property. > currentNode.setProperty(propertyName, (String[])null); > MockProperty api throws null pointer exception when we use JCR mocking. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] tmaret closed pull request #15: SLING-8086 - Extend distribution queue SPI with the ability to clear …
tmaret closed pull request #15: SLING-8086 - Extend distribution queue SPI with the ability to clear … URL: https://github.com/apache/sling-org-apache-sling-distribution-core/pull/15 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] tmaret commented on a change in pull request #15: SLING-8086 - Extend distribution queue SPI with the ability to clear …
tmaret commented on a change in pull request #15: SLING-8086 - Extend
distribution queue SPI with the ability to clear …
URL:
https://github.com/apache/sling-org-apache-sling-distribution-core/pull/15#discussion_r232502757
##
File path: src/main/java/org/apache/sling/distribution/queue/spi/Clearable.java
##
@@ -0,0 +1,51 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+package org.apache.sling.distribution.queue.spi;
+
+import java.util.Set;
+
+import aQute.bnd.annotation.ConsumerType;
+import org.apache.sling.distribution.queue.DistributionQueueEntry;
+import org.jetbrains.annotations.NotNull;
+
+/**
+ * Trait to be added to a {@link DistributionQueue} distribution
+ * queue that supports clearing all or a batch of items via the
+ * {@link Clearable#clear} methods.
+ *
+ * @since 0.1.0
+ */
+@ConsumerType
+public interface Clearable {
+
+/**
+ * Clear all items from the the queue.
+ */
+void clear();
+
+/**
+ * Clear a set of items from the queue.
+ *
+ * @param itemIds the set of item identifiers to be cleared
+ * @return the removed items
+ */
+@NotNull
+Iterable clear(@NotNull Set itemIds);
Review comment:
Good point, thanks. I have integrated your suggestions in the branch
SLING-8086-3.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] tmaret opened a new pull request #16: SLING-8086 - Extend distribution queue SPI with the ability to clear …
tmaret opened a new pull request #16: SLING-8086 - Extend distribution queue SPI with the ability to clear … URL: https://github.com/apache/sling-org-apache-sling-distribution-core/pull/16 …and batch remove items This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: [RT] Simple File System Resource Provider
Seeing as the current filesystem resource provider does need an update to java 8 api, it would be nice to refactor / start over with that one and make it more generic / extensible? It has some caveats (like the start up scanning etc.) that would be nice to have fixed in a more elegant way. Roy > On 11 Nov 2018, at 10:55, Carsten Ziegeler wrote: > > I've recently tried to run a minimal Sling without JCR. Obviously you need at > least one resource provider to have some content, so I picked the easiest > choice, the file system resource provider. > > However, it turned out that this is not the easiest choice for this scenario > as it has a lot of features, especially support for handling content XML > files and vault files, which again brings in the whole dependency list to jcr > related bundles. In my case I just want to stream binaries and json files, so > none of the above is needed. But still I need to deploy all the bundles. In > addition there are other things like the json parsing library is embedded in > the bundle etc. > > Now, I think we should really have a simple file system resource provider > which only does the basics and has not an endless list of bundles. I see two > ways to get there: make the current provider extensible and provide all this > extra cruft as extensions or write a new simple provider. > > Thoughts? > > Regards > Carsten > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org
[jira] [Updated] (SLING-8090) Use newest OSGi annotation versions
[ https://issues.apache.org/jira/browse/SLING-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-8090: --- Description: As OSGi annotations are only processed at build time and only need support from the according build tool (bnd in our case), we should upgrade to the newest R7 version of all annotations. Those are supported by bnd 4.1 and do not imply any runtime dependencies to R7 bundles. Compare also with https://github.com/bndtools/bnd/issues/2643 and https://github.com/bndtools/bnd/pull/2603. was:As OSGi annotations are only processed at build time and only need support from the according build tool (bnd in our case), we should upgrade to the newest R7 version of all annotations. Those are supported by bnd 4.1 and do not imply any runtime dependencies to R7 bundles. > Use newest OSGi annotation versions > --- > > Key: SLING-8090 > URL: https://issues.apache.org/jira/browse/SLING-8090 > Project: Sling > Issue Type: Bug > Components: General >Reporter: Konrad Windszus >Priority: Major > Fix For: Bundle Parent 35 > > > As OSGi annotations are only processed at build time and only need support > from the according build tool (bnd in our case), we should upgrade to the > newest R7 version of all annotations. Those are supported by bnd 4.1 and do > not imply any runtime dependencies to R7 bundles. > Compare also with https://github.com/bndtools/bnd/issues/2643 and > https://github.com/bndtools/bnd/pull/2603. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SLING-8090) Use newest OSGi annotation versions
Konrad Windszus created SLING-8090: -- Summary: Use newest OSGi annotation versions Key: SLING-8090 URL: https://issues.apache.org/jira/browse/SLING-8090 Project: Sling Issue Type: Bug Components: General Reporter: Konrad Windszus Fix For: Bundle Parent 35 As OSGi annotations are only processed at build time and only need support from the according build tool (bnd in our case), we should upgrade to the newest R7 version of all annotations. Those are supported by bnd 4.1 and do not imply any runtime dependencies to R7 bundles. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [VOTE] Release Apache Sling Servlets Get 2.1.38, Take II
+1 On Sat, Nov 10, 2018 at 7:40 AM Carsten Ziegeler wrote: > +1 > > Am 10.11.2018 um 11:29 schrieb Carsten Ziegeler: > > Hi, > > > > We solved 2 issues in this release > > https://issues.apache.org/jira/projects/SLING/versions/12344154 > > > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachesling-2014 > > > > You can use this UNIX script to download the release and verify the > > signatures: > > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > > > Usage: > > sh check_staged_release.sh 2014 /tmp/sling-staging > > > > Please vote to approve this release: > > > >[ ] +1 Approve the release > >[ ] 0 Don't care > >[ ] -1 Don't release, because ... > > > > This majority vote is open for at least 72 hours. > > > > Regards > > Carsten > > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org >
[jira] [Updated] (SLING-8008) Create dedicated parent for bundle projects
[ https://issues.apache.org/jira/browse/SLING-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-8008: --- Fix Version/s: Bundle Parent 35 > Create dedicated parent for bundle projects > --- > > Key: SLING-8008 > URL: https://issues.apache.org/jira/browse/SLING-8008 > Project: Sling > Issue Type: Improvement > Components: General >Affects Versions: Parent 34 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Parent 35, Bundle Parent 35 > > Time Spent: 20m > Remaining Estimate: 0h > > As followup to the Sling Hackathon in Berlin in September (compare with > [https://www.mail-archive.com/dev@sling.apache.org/msg79953.html > |https://www.mail-archive.com/dev@sling.apache.org/msg79953.html).]there is > the proposal to split up the current parent pom into two pieces: one for > JARs/general aspect, another one for bundles (covering only those aspects). > > The reasons for this switch are: > - we would like to switch completely to bnd-maven-plugin, but without the > need for a separate bnd file > - we currently have only one parent pom for bundle modules and non-bundle > modules, making it difficult to configure the bnd-maven-plugin globally so it > gets up picked only for bundles, not for simple jar files. > - using maven profiles would be an option, but there is no nice way to > trigger the profile without ugly hacks like having an empty bnd file present. > - https://issues.apache.org/jira/browse/MJAR-193 would be another solution > (haven the bnd plugin handing over the manifest extensions to the maven jar > plugin), but this feature is not available yet > > The proposed solutions looks like this > - create an additional "sling-bundle-parent" inheriting from the existing > "sling-parent" > - all bundle-related stuff goes there and will be removed from "sling-parent" > - old maven-bundle-plugin and bnd-maven-plugin should be removed from > sling-parent > - maven-bundle-plugin should be banned from sling-bundle-parent > - one repo for both, always released together > - start with next version 36 > - make a wiki page with migration steps > - bundle modules will use "sling-bundle-parent", jar modules "sling-parent" > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SLING-8008) Create dedicated parent for bundle projects
[ https://issues.apache.org/jira/browse/SLING-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-8008. Resolution: Fixed Fix Version/s: Parent 35 Merged with https://github.com/apache/sling-parent/commit/0fe2e77db1fce3f9b81e5a7c8514c7629b69a667. > Create dedicated parent for bundle projects > --- > > Key: SLING-8008 > URL: https://issues.apache.org/jira/browse/SLING-8008 > Project: Sling > Issue Type: Improvement > Components: General >Affects Versions: Parent 34 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Parent 35 > > Time Spent: 20m > Remaining Estimate: 0h > > As followup to the Sling Hackathon in Berlin in September (compare with > [https://www.mail-archive.com/dev@sling.apache.org/msg79953.html > |https://www.mail-archive.com/dev@sling.apache.org/msg79953.html).]there is > the proposal to split up the current parent pom into two pieces: one for > JARs/general aspect, another one for bundles (covering only those aspects). > > The reasons for this switch are: > - we would like to switch completely to bnd-maven-plugin, but without the > need for a separate bnd file > - we currently have only one parent pom for bundle modules and non-bundle > modules, making it difficult to configure the bnd-maven-plugin globally so it > gets up picked only for bundles, not for simple jar files. > - using maven profiles would be an option, but there is no nice way to > trigger the profile without ugly hacks like having an empty bnd file present. > - https://issues.apache.org/jira/browse/MJAR-193 would be another solution > (haven the bnd plugin handing over the manifest extensions to the maven jar > plugin), but this feature is not available yet > > The proposed solutions looks like this > - create an additional "sling-bundle-parent" inheriting from the existing > "sling-parent" > - all bundle-related stuff goes there and will be removed from "sling-parent" > - old maven-bundle-plugin and bnd-maven-plugin should be removed from > sling-parent > - maven-bundle-plugin should be banned from sling-bundle-parent > - one repo for both, always released together > - start with next version 36 > - make a wiki page with migration steps > - bundle modules will use "sling-bundle-parent", jar modules "sling-parent" > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] kwin closed pull request #3: SLING-8008 separate parent pom for bundles
kwin closed pull request #3: SLING-8008 separate parent pom for bundles URL: https://github.com/apache/sling-parent/pull/3 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Resolved] (SLING-584) extensions dojo demo1.html doesn't work in tomcat deployment
[
https://issues.apache.org/jira/browse/SLING-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-584.
Resolution: Won't Fix
> extensions dojo demo1.html doesn't work in tomcat deployment
> -
>
> Key: SLING-584
> URL: https://issues.apache.org/jira/browse/SLING-584
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Environment: linux, jdk 1.6, tomcat apache-6.0.16
>Reporter: John Langley
>Priority: Major
>
> the dojo jcr browser doesn't work when deployed into a sling instance which
> is running w/in tomcat (deployed as a war)
> below is the error from http://localhost:8080/sling/dojox/data/demo/demo1.html
> Interestingly, the same build and bundles run in a jetty:run from w/in
> launchpad/webapp work fine.
> status : 404
> responseText : Apache Tomcat/6.0.16 - Error
> report
> HTTP Status 404 - /.1.json noshade="noshade">type Status reportmessage
> /.1.jsondescription The requested resource (/.1.json)
> is not available.Apache
> Tomcat/6.0.16
> message : Unable to load /.1.json status:404
> fileName : http://localhost:8080/sling/dojo/_base/_loader/bootstrap.js
> lineNumber : 971
> stack : Error("Unable to load /.1.json status:404")@:0
> ([object
> Object])@http://localhost:8080/sling/dojo/_base/_loader/bootstrap.js:971
> (576)@http://localhost:8080/sling/dojo/_base/_loader/bootstrap.js:888
> @:0
> name : Error
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SLING-573) google-style shorthand on query.json
[ https://issues.apache.org/jira/browse/SLING-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-573. Resolution: Won't Fix > google-style shorthand on query.json > > > Key: SLING-573 > URL: https://issues.apache.org/jira/browse/SLING-573 > Project: Sling > Issue Type: Improvement > Components: Servlets >Reporter: David Nuescheler >Priority: Major > > it would be great to allow a "q=" parameter similar to google that would > allow for simple and easy > querying of the repository in google style. > this would be an additional feature that would auto detect the querytype > based on the query. > it is neither a "sql", "xpath" or google syntax jcr:contains query... > examples: > -- > /mynode.query.json?q=SELECT%20*%20FROM%20nt%3abase > ... translates into ... > SELECT * FORM nt:base WHERE jcr:path like '/mynode/%' > -- > /mynode.query.json?q=mytest > ... translates into ... > SELECT * FORM nt:base WHERE jcr:path like '/mynode/%' and jcr:contains(*, > 'mytest') > -- > or xpath equivalent... ;) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SLING-7934) Add the ability for a resource to adapt to a JSONObject
[ https://issues.apache.org/jira/browse/SLING-7934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682809#comment-16682809 ] Carsten Ziegeler commented on SLING-7934: - I'm still a little bit struggling with how to use this. JsonObject is immutable, so any client code getting this JsonObject that wants to stream a different JSON structure than the one represented by the returned JsonObject needs to do quiet some complex manipulation to get a new JsonObject with the correct structure out of it. It's not possible to remove or add a property without creating a new JsonObject. In that case creating a JsonObject out of a resource can as easily be done by adapting the resource to a value map, although value map does not support a hierarchy only a flat list of properties. Maybe that's the issue to fix? > Add the ability for a resource to adapt to a JSONObject > --- > > Key: SLING-7934 > URL: https://issues.apache.org/jira/browse/SLING-7934 > Project: Sling > Issue Type: Improvement >Reporter: Jason E Bailey >Assignee: Jason E Bailey >Priority: Major > > There are multiple implementations all doing the same process of converting a > resource to a JSONObject. If it's that common we should just add the ability > to adapt the resource and centralize the implementation so that it's > consistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[RT] Simple File System Resource Provider
I've recently tried to run a minimal Sling without JCR. Obviously you need at least one resource provider to have some content, so I picked the easiest choice, the file system resource provider. However, it turned out that this is not the easiest choice for this scenario as it has a lot of features, especially support for handling content XML files and vault files, which again brings in the whole dependency list to jcr related bundles. In my case I just want to stream binaries and json files, so none of the above is needed. But still I need to deploy all the bundles. In addition there are other things like the json parsing library is embedded in the bundle etc. Now, I think we should really have a simple file system resource provider which only does the basics and has not an endless list of bundles. I see two ways to get there: make the current provider extensible and provide all this extra cruft as extensions or write a new simple provider. Thoughts? Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Resolved] (SLING-990) Prototype for a Sling Explorer implementation based on GWT
[ https://issues.apache.org/jira/browse/SLING-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-990. Resolution: Won't Fix > Prototype for a Sling Explorer implementation based on GWT > -- > > Key: SLING-990 > URL: https://issues.apache.org/jira/browse/SLING-990 > Project: Sling > Issue Type: New Feature > Components: Extensions >Reporter: Christophe Lombart >Priority: Major > Attachments: Sling Explorer.zip, sling-explorer-only-gwt.zip, > slingexplorer.tiff > > Original Estimate: 0h > Remaining Estimate: 0h > > Following the Sling Explorer proposal [1], I have started an implementation > with the SwartGwt UI framework [2] (based on GWT and under LGPL licence). > Not sure but I think that LGPL is compatible with the Apache project. > Until now, it is just a prototype. Can you review the code and see if this > Gwt application is well integrated with Sling ? > [1] http://cwiki.apache.org/SLING/sling-based-jcr-explorer.html > [2] http://code.google.com/p/smartgwt/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SLING-575) include fully qualified urls in json repsonses from search
[ https://issues.apache.org/jira/browse/SLING-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-575. Resolution: Won't Fix > include fully qualified urls in json repsonses from search > -- > > Key: SLING-575 > URL: https://issues.apache.org/jira/browse/SLING-575 > Project: Sling > Issue Type: Improvement > Components: Servlets >Reporter: Michael Marth >Priority: Minor > > related to https://issues.apache.org/jira/browse/SLING-574 and > https://issues.apache.org/jira/browse/SLING-573: > the fully qualified urls should also be included in the json rendering of > search results (which are not nodes, thus the new issue) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SLING-574) include fully qualified urls in json repsonses
[
https://issues.apache.org/jira/browse/SLING-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-574.
Resolution: Won't Fix
> include fully qualified urls in json repsonses
> --
>
> Key: SLING-574
> URL: https://issues.apache.org/jira/browse/SLING-574
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
>Reporter: David Nuescheler
>Priority: Major
>
> based on the conversation here:
> http://markmail.org/message/fls3gp3b45shvw7q
> i would like to suggest to include a sling:src property into nodes in the
> json responses
> this would mean that a node that was returned as
> mynode: {
> title:"my title",
> text:"text"
> }
> would not be returned as
> mynode: {
> sling:src:"http://localhost:7402/content/deep/mynode;,
> title:"my title",
> text:"text"
> }
> i am not sure if this should go into the standard json rendition but i think
> it really could.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SLING-550) Support for background servlets
[ https://issues.apache.org/jira/browse/SLING-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-550. Resolution: Won't Fix > Support for background servlets > --- > > Key: SLING-550 > URL: https://issues.apache.org/jira/browse/SLING-550 > Project: Sling > Issue Type: Improvement > Components: Extensions >Reporter: Bertrand Delacretaz >Priority: Minor > > In some cases (like the webloader example), long-running processes need to be > started, monitored and stopped. > The webloader implements this in a naive way, it might be useful to have a > more generic facility for this: a service that would: > 1) Start a script or servlet, probably passing it a fake request object that > gives access to parameters and output but is not a real HTTP request > 2) Display a status page where currently running jobs can be monitored, and > stopped if desired > 3) Collect the output of such jobs in the repository and give access to it > via a simple monitoring interface > The output of long-running jobs could be structured using html conventions > (like running step 3 of 12) to create overview > displays of all currently running jobs. > This is just an idea for now, I'm not going to work on this right away, but > it's probably good to keep in our wishlist. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SLING-518) JCR-Explorer -- Add support for a "meta" selector to support richer information about node properties
[ https://issues.apache.org/jira/browse/SLING-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-518. Resolution: Won't Fix > JCR-Explorer -- Add support for a "meta" selector to support richer > information about node properties > - > > Key: SLING-518 > URL: https://issues.apache.org/jira/browse/SLING-518 > Project: Sling > Issue Type: New Feature > Components: JCR >Reporter: Craig L. Ching >Priority: Minor > Attachments: SLING-518-001.patch > > > This is the first patch for the JCR Explorer functionality, I'll continue to > prepend "JCR-Explorer" to related JIRA issues. This implements a new JSON > rendering needed by the JCR Explorer. > I'd originally asked to enhance the existing JSON interfaces to the > repository to provide the JCR node properties as JSON objects rather than > simple key/value pairs, but Alex suggested [1] that that would break existing > operations and that I should create a new "metadata" selector to key the > different rendering. > That said, I'm not entirely thrilled about this patch. It certainly works > and was easy enough to create, however, it is mostly just a copy of the > existing JsonItemWriter and maintaining two objects that are so similar is > surely less than ideal. But I didn't see an easy way to enhance the existing > JsonItemWriter without fundamentally changing it. So I'm just "throwing this > over the wall" to get some feedback/suggestions on how best to proceed. > I haven't implemented any tests for this, I'll see what I can whip up. > Hopefully there are already test cases for JsonItemWriter and > JsonRendererServlet that I can base some tests on. > Ideally, I'd like to get this functionality sorted out and committed before I > submit the rest of the JCR Explorer implementation as the rest is > non-intrusive and dependent on this. > [1] -- > http://mail-archives.apache.org/mod_mbox/incubator-sling-dev/200805.mbox/%3c63bea5e623e09f4d92233fb12a9f794301fc8...@emailmn.mqsoftware.com%3e > NOTE: I'll attach a patch in the next comment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SLING-572) "Notes" example application
[ https://issues.apache.org/jira/browse/SLING-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-572. Resolution: Won't Fix > "Notes" example application > --- > > Key: SLING-572 > URL: https://issues.apache.org/jira/browse/SLING-572 > Project: Sling > Issue Type: Improvement > Components: Documentation >Reporter: Michael Marth >Priority: Minor > Attachments: notes-sample.patch, notes.xml, notes.xml, notes.zip > > > As discussed with Bertrand I have written a Sling example app and suggest to > put it into svn so others can benefit. Attached is the code (to be put into > /apps/notes) and initial content in sysview format. > The code has room for improvement (see bottom of blog post > http://dev.day.com/microsling/content/blogs/main/anothersampleapp.html) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SLING-513) How to run the JCR Explorer with Sling?
[ https://issues.apache.org/jira/browse/SLING-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-513. Resolution: Won't Fix > How to run the JCR Explorer with Sling? > --- > > Key: SLING-513 > URL: https://issues.apache.org/jira/browse/SLING-513 > Project: Sling > Issue Type: Improvement > Components: Documentation >Reporter: Bertrand Delacretaz >Priority: Minor > > It would be good to have a How-To document about using the JCR Explorer > (http://www.jcr-explorer.org/, or another one?) with the Sling Launchpad. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SLING-377) Make troubleshooting of initial content loading easier
[ https://issues.apache.org/jira/browse/SLING-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-377. Resolution: Won't Fix > Make troubleshooting of initial content loading easier > -- > > Key: SLING-377 > URL: https://issues.apache.org/jira/browse/SLING-377 > Project: Sling > Issue Type: Bug > Components: JCR >Reporter: Bertrand Delacretaz >Priority: Minor > > Currently, for example if an xjson file includes a property type that is not > allowed by the parent node, it is very hard to find out exactly what is > happening based on the log messages. > We need to improve the reporting of such errors, and maybe include some json > validation as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SLING-2158) JsonSerialization: Add new ":order" JSON array to transport child node ordering when needed
[
https://issues.apache.org/jira/browse/SLING-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2158.
-
Resolution: Won't Fix
> JsonSerialization: Add new ":order" JSON array to transport child node
> ordering when needed
> ---
>
> Key: SLING-2158
> URL: https://issues.apache.org/jira/browse/SLING-2158
> Project: Sling
> Issue Type: New Feature
> Components: Servlets
>Reporter: Tobias Bocanegra
>Priority: Minor
>
> as discussed in:
> http://mail-archives.apache.org/mod_mbox/sling-dev/201104.mbox/%3cbanlktimau-cv5fhyyrx-z5ktn4afmfq...@mail.gmail.com%3E
> i suggest to add a new array property containing the child node names to the
> default JSON renderer if 'requested' with an 'order' selector.
> i would include the child node names also on the end of the depth limit. this
> allows to get the child node names without the need to load them with a
> deeper request:
> eg:
> GET /content/en.0.order.json would return:
> {
> "title": "Hello, world",
> ":oder": ["sub1", "sub2"]
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SLING-2801) Sling GET servlet fails to export JSON when property contains a Double.NaN value
[ https://issues.apache.org/jira/browse/SLING-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-2801. - Resolution: Won't Fix > Sling GET servlet fails to export JSON when property contains a Double.NaN > value > > > Key: SLING-2801 > URL: https://issues.apache.org/jira/browse/SLING-2801 > Project: Sling > Issue Type: Bug > Components: Servlets >Affects Versions: Servlets Get 2.1.4 >Reporter: Tobias Bocanegra >Priority: Minor > > exporting a JSON of a node that contains a Double.NaN value returns a 500: > JSON does not allow non-finite numbers > Cannot serve request to /metadata.json in > org.apache.sling.servlets.get.DefaultGetServlet > Exception: > org.apache.sling.commons.json.JSONException: JSON does not allow non-finite > numbers > at > org.apache.sling.commons.json.JSONObject.testValidity(JSONObject.java:997) > at org.apache.sling.commons.json.JSONObject.put(JSONObject.java:885) > at > org.apache.sling.servlets.get.impl.helpers.JsonObjectCreator.createProperty(JsonObjectCreator.java:199) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
