Re: Possible bug in bundlor

[Piotr Tajduś]

You can find simple maven project with one test  in attachment, it 
requires connection to mongodb:
    private String mongoUrl = "mongodb://127.0.0.1:27017";
    private String dbName = "bundlor-test";
Best regards,
Piotr


On 22.10.2019 16:23, Julian Reschke wrote:
On 22.10.2019 15:13, Piotr Tajduś wrote:
I have added bundlor definition for my document structure. It works
fine, but I have found possible bug which occurs when node name starts
with siblings name - fragment from dump:

"/crkid/dokument/TEST/2019/10/22/14/05/TXX%3A20191022009/metadane/inneMetadaneDateTime", 


"/crkid/dokument/TEST/2019/10/22/14/05/TXX%3A20191022009/metadane/inneMetadaneDateTime/imd.public.TestDATETIME 

= 2019-10-10T11:22:33.000+02:00",
"/crkid/dokument/TEST/2019/10/22/14/05/TXX%3A20191022009/metadane/inneMetadaneDateTime/jcr:primaryType 

= crkidmd:InneMetadane",

"/crkid/dokument/TEST/2019/10/22/14/05/TXX%3A20191022009/metadane/inneMetadaneDate", 


"/crkid/dokument/TEST/2019/10/22/14/05/TXX%3A20191022009/metadane/inneMetadaneDate/imd.public.TestDATETIME 

= 2019-10-10T11:22:33.000+02:00",
"/crkid/dokument/TEST/2019/10/22/14/05/TXX%3A20191022009/metadane/inneMetadaneDate/imd.public.TestDATE 

= 2019-10-10T00:00:00.000+02:00",
"/crkid/dokument/TEST/2019/10/22/14/05/TXX%3A20191022009/metadane/inneMetadaneDate/jcr:primaryType 

= crkidmd:InneMetadane",

Properties from inneMetadaneDateTime are cloned into inneMetadaneDate.
When I remove those nodes from bundlor patterns everything is fine. To
avoid this problem I have changed inneMetadaneDateTime into
inneMetadaneDT and it works too.


Best regards,

Piotr

Any chance you can reproduce this in a unit test?

Best regards, Julian


<<attachment: test.zip>>