RE: Resource provided by custom ResourceProvider crashes upon calling hasChildren()

2017-06-08 Thread Olaf
Hi Bart, I put them right in the code, where they are probably hard to spot :-) The essential one should be the one next to the place where you add the resource to the list of resource in ResourceProvider#listChildren. Updated version: You can never re-provide a resource resolved by a different

Re: Resource provided by custom ResourceProvider crashes upon calling hasChildren()

2017-06-08 Thread Bart Wulteputte
Hi Olaf, Is it possible that you didn't send your remarks? I don't see them in your first mail. Best regards _ From: Olaf > Sent: donderdag, juni 8, 2017 11:25 PM Subject: RE: Resource provided by custom ResourceProvider crashes

RE: Resource provided by custom ResourceProvider crashes upon calling hasChildren()

2017-06-08 Thread Olaf
Hi Bart, I just saw you already used ResourceProvider#(ResolveContext ctx, Resource parent), excellent. Forget my first remark then, providing a SyntheticResource should do. Cheers, Olaf -Original Message- From: Olaf [mailto:o...@x100.de] Sent: Donnerstag, 8. Juni 2017 23:23 To:

RE: Resource provided by custom ResourceProvider crashes upon calling hasChildren()

2017-06-08 Thread Olaf
Hi Bart! Resource providers are mighty, but tricky things indeed. Please find my >remarks below. Cheers, Olaf -Original Message- From: Bart Wulteputte [mailto:bart.wultepu...@gmail.com] Sent: Donnerstag, 8. Juni 2017 22:50 To: users@sling.apache.org Subject: Resource provided by

Resource provided by custom ResourceProvider crashes upon calling hasChildren()

2017-06-08 Thread Bart Wulteputte
Hi, While trying to implement a POC and I ran into a strange error, and I hope you guys can help identify whether this is a bug, or if I'm just doing something wrong. I'm playing around with custom resource providers to pull external data into sling. I don't do anything crazy in there (yet), but

Re: Removing commons.json guidance

2017-06-08 Thread Nicolas Peltier
Hi Karl, Thanks for this! (Thought I needed to do the work :-) ) Nicolas > On 29 May 2017, at 15:34, Karl Pauls wrote: > > Hi Nicolas, > > I'm not sure I 100% understand what you are asking but in a nutshell, > the org.json license has been moved to CAT-X (i.e., not