Re: playing with sling pipes

sorry, realised you are actually hitting one component, with 2 subproperties, you could achieve this with a write pipe like in [0], assuming the null feature of the write pipe works which was not the case until i fixed [1], [2] and [3] :-) will send you below sample & built snapshot in private

Re: playing with sling pipes

Thanks Nicolas, the sample config worked great. The patches from the bug fixes aren’t in the latest version on github so I had to apply them myself. However, I had to remove the patch from [3] because it introduced a bug where only the null properties from the first node found are removed.

Re: playing with sling pipes

Thx Diran! Updated [3]'s patch with your feedback On 15 janv. 2016, at 23:54, DIRAN SAMARJIAN > wrote: Thanks Nicolas, the sample config worked great. The patches from the bug fixes aren’t in the latest version on github so I had to apply them

Re: playing with sling pipes

Hey Ruben! including sling users DL here. if i understand it correctly, you wish to move several properties from a same node in different things, > Eg if the property does not exist, skip the move? Is the problem you have here not to cut the execution stream if one of the property does not

Re: playing with sling pipes

Hi Nicolas, Yes, the issue we are having is not to cut the execution stream if a single pipe fails. We basically have a grouping of pipes in a container pipe but I can see by design the container pipe stops execution if any intermediate pipe fails. Is there an alternative way to group pipes

Re: playing with sling pipes

Right, you need to do 2 different pipes for prop1 and prop2 here, as there are clearly 2 different streams here, and shouldn’t be queued. the sequence is in your script calling 2 curl :-), or if you really want to do it in one curl, you can still create a servlet chaining those 2 pipes: Pipe