-
From: Guillaume Lucazeau [mailto:glucaz...@gmail.com]
Sent: Montag, 16. November 2015 16:09
To: users@sling.apache.org
Subject: Re: Resource class vs CND
Thank you Olaf for your answer.
I have currently little information about the app. What I know is that it will
mostly manage documents
After spending 6 months working with AEM and MongoDB. I would be hesitant to
recommend it as a solution.
-Original Message-
From: Olaf [mailto:o...@x100.de]
Sent: Monday, November 16, 2015 10:49 AM
To: users@sling.apache.org
Subject: RE: Resource class vs CND
Hi Guillaume,
That does
class vs CND
After spending 6 months working with AEM and MongoDB. I would be hesitant to
recommend it as a solution.
-Original Message-
From: Olaf [mailto:o...@x100.de]
Sent: Monday, November 16, 2015 10:49 AM
To: users@sling.apache.org
Subject: RE: Resource class vs CND
Hi Guillaume
;
> -Original Message-
> From: Guillaume Lucazeau [mailto:glucaz...@gmail.com]
> Sent: Freitag, 13. November 2015 16:10
> To: users@sling.apache.org
> Subject: Re: Resource class vs CND
>
> Thank you for your advice
>
> I got rid of my CND file and created conten
Thank you for your advice
I got rid of my CND file and created content using sling:resourceType. I
had the idea that defining my node structure somewhere would allow me to
create form dynamically to add subnodes.
So I've created two classes:
// Document.java
@Model(adaptables=Resource.class)
is JCR OCM, but it's dated / requires some additional work:
http://www.connectcon.ch/2015/en/speakers/katarzyna-kozlowska.html
-Original Message-
From: Guillaume Lucazeau [mailto:glucaz...@gmail.com]
Sent: Freitag, 13. November 2015 16:10
To: users@sling.apache.org
Subject: Re: Resourc
My opinions:
Sling is really about being able to take a data set and present that data in
multiple ways. For the vast majority of use cases you should use the existing
node types and property values and you don't need to use a CND.
A custom nodetype is useful if there is a need to perform
