Re: [DISCUSS] Deprecate query part of Sling Event API

On 08.01.19 17:12, Carsten Ziegeler wrote: I agree, variant B sounds like the better option ... The only downside is that this doesn't force anyone to think about her job usage as everything just runs as before. Only if you want to improve you can and adjust the configurations. That's a

Re: Sling Type System: started a wiki page for concepts, ideas, motivation

Hi, On Wed, Jan 9, 2019 at 9:57 AM Jason E Bailey wrote: > > On Tue, Jan 8, 2019, at 7:43 PM, Christanto Leonardo wrote: > > > > ``` > > + /mycontent2 > > - jcr:primaryNodeType = "nt:unstructured" > > - sling:resourceType = "my/page" > > - my:created = "2019-01-01T00:00:00Z" > > -

Re: Sling Type System: started a wiki page for concepts, ideas, motivation

Hi, On Tue, Jan 8, 2019 at 9:54 PM Bertrand Delacretaz wrote: > Hi, > > On Tue, Jan 8, 2019 at 2:15 PM Bertrand Delacretaz > wrote: > > ...That common ground might be a Java API used to access the underlying > > models, exposing their semantics in a way that clearly defines how > > they are

Re: Sling Type System: started a wiki page for concepts, ideas, motivation

On Tue, Jan 8, 2019, at 7:43 PM, Christanto Leonardo wrote: > > ``` > + /mycontent2 > - jcr:primaryNodeType = "nt:unstructured" > - sling:resourceType = "my/page" > - my:created = "2019-01-01T00:00:00Z" > - my:title = "Title 1" > ``` > > Here, you simply define a DataModel for

Re: Sling Type System: started a wiki page for concepts, ideas, motivation

Hi, > One of the core tenants of Sling is that everything is a Resource. One of my expectations of a Type system is that I can create a type by POST and retrieve the structure of the type via a GET. That the definitions of a Type are themselves resources. > > I may be missing this from your

Re: Sling Type System: started a wiki page for concepts, ideas, motivation

Hi, On Tue, Jan 8, 2019 at 11:08 PM Jason E Bailey wrote: > I really appreciate the thought that you put into this. > > If you are utilizing the JCR Resource Provider to store a resource you > have to declare a jcr:primaryType, and you are then bound by the definition > of the node as to what

Re: [DISCUSS] Deprecate query part of Sling Event API

Yeah I must admit I'm confused as well, looking through the email threads the original proposal is to return and a iterator rather than a collection. If the problem is that too many jobs being returned causes heap issues, I would think this would resolve that problem. Is there some other problem

Re: [DISCUSS] Deprecate query part of Sling Event API

So I'm missing something here, from what I gather so far, the methods that are being deprecated are to prevent a performance issue but the node structure that represents the jobs is in one place isn't it? How in the world are we getting a performance issue from that? Is there a use case to

[jira] [Created] (SLING-8206) Add Support for sling:basename when using JSON based dictionaries

Daniel created SLING-8206: - Summary: Add Support for sling:basename when using JSON based dictionaries Key: SLING-8206 URL: https://issues.apache.org/jira/browse/SLING-8206 Project: Sling Issue

Re: [DISCUSS] Deprecate query part of Sling Event API

Hi, I agree, variant B sounds like the better option due to the reasons you mention. It also provides a step by step way of moving a single type of jobs to not use search anymore. The only downside is that this doesn't force anyone to think about her job usage as everything just runs as

Re: Sling Type System: started a wiki page for concepts, ideas, motivation

I really appreciate the thought that you put into this. If you are utilizing the JCR Resource Provider to store a resource you have to declare a jcr:primaryType, and you are then bound by the definition of the node as to what you can add as an attribute or a child type. So there is such thing

[sightly] reducing exceptions spitting

Hi, Doing some profiling on a "simple" page rendering, got the alert from oracle java mission control that too many exceptions were spit. I could indeed see that there is 1K NoSuchFieldException spit per page view, and that a simple fix [0] was making things look better. Is it really better

Re: Sling Type System: started a wiki page for concepts, ideas, motivation

Hi, > 5. you describe it should be possible to derive data models from JCR CND definitions. do you think this should be the major use case? JCR CND definitions are quite out-of-fashion nowadays, and used more for historical reasons (or for performance optimizations because oak indexes are based

[jira] [Created] (SLING-8205) stop using Class.getField() to stop spitting out NoSuchFieldException

Nicolas Peltier created SLING-8205: -- Summary: stop using Class.getField() to stop spitting out NoSuchFieldException Key: SLING-8205 URL: https://issues.apache.org/jira/browse/SLING-8205 Project:

Re: Sling Type System: started a wiki page for concepts, ideas, motivation

Hi, On Tue, Jan 8, 2019 at 2:15 PM Bertrand Delacretaz wrote: > ...That common ground might be a Java API used to access the underlying > models, exposing their semantics in a way that clearly defines how > they are used in Sling and possibly other applications I have had a closer look at

Re: Sling Type System: started a wiki page for concepts, ideas, motivation

Hi, > 3. one of the reasons why sling is why it is (without an explicit modeling capability) is the rule #1 of david's model "Data First, Structure Later. Maybe." [1]. this was stated a very long time ago. would be nice if you can add a reference to your explainer page to it as well and explain

Re: Sling Type System: started a wiki page for concepts, ideas, motivation

Hello, > 2. do you plan to support only a single resource/node and it's properties. what's with sub tree structures, that are supported by JCR CND definitions? more complex data models like forms are unlikely to be represented by a single resource. or maybe that is already covered with the

Re: Sling Type System: started a wiki page for concepts, ideas, motivation

Hello, > 1. why defining a new "DSL" to describe the model metadata? what's with existing things like json schema. defining a completely new DSL often has the risk of not getting it "right" in the first place. You still need the runtime API. In this case DataMode.class, Property.class and other

Re: Sling Type System: started a wiki page for concepts, ideas, motivation

Hi, Thank you Christanto for your suggestions - I'll take Stefan's questions as a basis to clarify my ideas around this. I think we can and should find a common ground between Christanto's (pretty concrete) proposal and the (more vague) ideas that I drafted at [0]. That common ground might be a

Re: Sling Type System: started a wiki page for concepts, ideas, motivation

Hello, > 6. you describe some "other models" like FormModel, ActionsModel which sound like hypermedia support. i do not fully understand how hypermedia support fits into the other parts you describe which primarily describe the data model and not the actions for them. where does this hypermedia

Re: Sling Type System: started a wiki page for concepts, ideas, motivation

Hello Stefan, Let's tackle one by one. > 4. the name "Models" can be mixed up with "Sling Models" [2] which points somewhat into the same direction but is currently based on different concepts and is already used much. but i suppose this can be sorted out later to decide if this new approach can

RE: Sling Type System: started a wiki page for concepts, ideas, motivation

hello christanto. thanks for bringing this up! some first questions after a first read: 1. why defining a new "DSL" to describe the model metadata? what's with existing things like json schema. defining a completely new DSL often has the risk of not getting it "right" in the first place. 2.

[jira] [Commented] (SLING-7445) Install bundle: "Failed getting intermediate path at http://localhost:4502/apps/project. Reason: Forbidden" when directory listings are turned off

[ https://issues.apache.org/jira/browse/SLING-7445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736976#comment-16736976 ] Konrad Windszus commented on SLING-7445: Fixed in

[jira] [Resolved] (SLING-7445) Install bundle: "Failed getting intermediate path at http://localhost:4502/apps/project. Reason: Forbidden" when directory listings are turned off

[ https://issues.apache.org/jira/browse/SLING-7445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-7445. Resolution: Fixed > Install bundle: "Failed getting intermediate path at >

[GitHub] kwin closed pull request #1: SLING-7445 also accept 403 status code for existing intermediate nodes

kwin closed pull request #1: SLING-7445 also accept 403 status code for existing intermediate nodes URL: https://github.com/apache/sling-maven-sling-plugin/pull/1 This is an automated message from the Apache Git Service. To

[jira] [Resolved] (SLING-8202) Support "additionalMavenParams" in sling-module.xml

[ https://issues.apache.org/jira/browse/SLING-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-8202. Resolution: Fixed Fixed in

Re: [jdk bug] for those of you on Mac running JDK 1.8

Fixed now via https://issues.apache.org/jira/browse/SLING-8202 . > On 7. Jan 2019, at 14:45, Konrad Windszus wrote: > > Tried to do this with >

Failed Pipeline: sling-ide-tooling » master #69

See https://builds.apache.org/job/sling-ide-tooling/job/master/69/

[jira] [Assigned] (SLING-8202) Support "additionalMavenParams" in sling-module.xml

[ https://issues.apache.org/jira/browse/SLING-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-8202: -- Assignee: Konrad Windszus (was: Robert Munteanu) > Support "additionalMavenParams"