Re: [jackson-user] Json deep merge array processing strategy

2021-04-07 Thread Tatu Saloranta
On Tue, Apr 6, 2021 at 8:48 PM Saurin Joshi wrote: > > Thanks Tatu for prompt response and suggestion. > > I could solve the 1st issue by overriding withResolved() method and got > CustomCollectionDeserializer working as described below. However, I see the > complications it will bring in for

Re: [jackson-user] Json deep merge array processing strategy

2021-04-06 Thread Saurin Joshi
Thanks Tatu for prompt response and suggestion. I could solve the 1st issue by overriding withResolved() method and got CustomCollectionDeserializer working as described below. However, I see the complications it will bring in for maintaining this class. I will instead go with your suggested

Re: [jackson-user] Json deep merge array processing strategy

2021-04-06 Thread Saurin Joshi
Apologies for opening a zombie thread. I am also interested in deep merge of 2 arrays based on index. If I have 2 JSON strings *JSON string1 *and *JSON string2* as below, then I would like the output merged property like *Merged JSON* *JSON string1:* { "property1": [ {

Re: [jackson-user] Json deep merge array processing strategy

2018-10-28 Thread Tatu Saloranta
Merging for arrays does mean concatenation (append for Collections), and nothing else. This because while there are many possible ways users might want to handle merging of two sequence values, it is surprisingly difficult to figure out declarative way that covers enough without being very