ili2pg error xml document structures must start and end within the same entity

[dmunozcastro]

when I executes an update to postgres using ili2pg-4.9.1 and ili2pg-4.9.0 from a xtf that pass all the validations, the jar generates the error: xml document structures must start and end within the same entity.

I attach the logs generated, the xtf was the same and it is 1.023.282 KB

ili4.9.0.log

ili4.9.1.log

If you have any idea I thanks too much.

[edigonzales]

Did you check if the error - that the xml parser reports - is real? If so it would be a bug in ilivalidator.

[dmunozcastro]

Tx for your quik anwer.

Yes, I reviewed all the xtf, all the tags are well, in aditión the row and the column that indicates don´t have any difference with its predecessors and successors so it seems don´t have any sense.

I attach some lines of the xtf.

some extract from full xtf from line 1220300 to line 1220308:

<LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente><fuente_administrativa REF="1cdf5fc3-f41f-4450-853f-55a269056fe6"></fuente_administrativa></LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente>
<LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente><fuente_administrativa REF="9fd6b712-5fa4-4d1c-beb5-78b8235a20ee"></fuente_administrativa></LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente>
<LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente><fuente_administrativa REF="26cc660c-0be7-4ff3-94c7-2ab7f0244cca"></fuente_administrativa></LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente>
<LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente><fuente_administrativa REF="726dc092-7d5c-40fc-be59-4232fb104172"></fuente_administrativa></LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente>
<LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente><fuente_administrativa REF="7f06fd62-bd4a-4f82-ac4c-ed1df777c5d9"></fuente_administrativa></LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente>
<LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente><fuente_administrativa REF="48d9ff07-cb5c-4d81-b564-d21bf16b3373"></fuente_administrativa></LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente>
<LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente><fuente_administrativa REF="e38129d9-7a06-4217-ba83-b60bdc655f04"></fuente_administrativa></LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente>
<LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente><fuente_administrativa REF="7feb53aa-b5c9-4a7d-aa97-c6688ef49616"></fuente_administrativa></LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente>
<LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente><fuente_administrativa REF="823a6106-b882-4e86-9277-5f44a9bb9441"></fuente_administrativa></LADM_COL_V3_1.LADM_Nucleo.col_unidadFuente>

TIA

[sjib]

Use an xml checker to see if it is well formatted
https://stackoverflow.com/questions/37116985/error-xml-document-structures-must-start-and-end-within-the-same-entity

e.g. https://codebeautify.org/xmlvalidator

[dmunozcastro]

I used a desktop solution because the size of the xtf is too big, this was the result:

The result was 0 errors 0 warnings as we spect.

I don´t know any schema (W3C or RelaxNG) that I can give to program I used so it can do a deeper validation, if you know some I will appreciate it too much.

[edigonzales]

Can you try to delete the line / object in the file where it throws the error?

[dmunozcastro]

Yes I can, I'm going to try it and share with you the result.

[dmunozcastro]

In this try the xtf load correctly, I attach the log.

At this point I don't understand anything, for me this don't have any sensse, if the xtf pass the validation, how can I identify what is going on whit the line I sended previusly?, if that line is deleted it mades the update runs with out any problem, the line don't seems to have any sintax or relational error.

If you have any idea I appreciate that you share it with me. This librarys pretends to work in a unatended environment.

ili4.9.0_II.log

[sjib]

Do you get the error when you just leave the line in the data file that creates the error?Then you would have identified the error, else the error is somewhere else.

[dmunozcastro]

Yes, when the line is in the xtf file the error arise. I all ready compared this line with the other of the same object, no structure differences on it. I really don´t know how can I find the error somewhere else.