FRL to XML Translate Warning

[Henry Tabingo]

I have an interface with a translate from FRL to XML. It has been running for about a year now. The issue is that the translate logs a warning that says:

Missing elements in possible ALL group at tns:DATA.tns:HR_FILE_UPD_MESSAGE(0).tns:HR_FILE_ENTRIES.tns:HR_ENTRY.tns:PERSON_INFO.0(0).  Please review the schema definition and populate the required nodes if necessary

Missing elements in possible ALL group at tns:DATA.tns:HR_FILE_UPD_MESSAGE(0).tns:HR_FILE_ENTRIES.tns:HR_ENTRY.tns:EMP_ORG_POSITION_LST.tns:ORG_POSITION.0(0).  Please review the schema definition and populate the required nodes if necessary.

The log file generated is so large because of the two warnings per message multiplied by the number of messages that it’s difficult to find other useful stuff in the log.

The schema has five required fields stated below and these are always populated. The rest of the fields not stated below are optional. I have tried disabling the validation when compiling the schema (xsd file) but to no avail. Why is Cloverleaf is doing this? We’re on AIX CL 5.7 Rev2.

If anyone has experienced this same issue and resolved it, please share with me your resolution.

FRL

---

>XML

---

>Required

Interface: >OPTILINK<               Emp_ID: >000006852<                 Emp_ID.#text                           Yes Person_LastName: >Lastname <    Person_LastName.#text             Yes Person_FirstName: >Firstname <    Person_FirstName.#text            Yes Dept_Number: >0007420<             Emp_Org_Dept.#text                Yes Job_Code: >22222<                      Position_Control_Number.#text  Yes Thanks, Henry

Topic

[Robert Kersemakers]

Hi Henry,

I haven’t seen these error messages before; with XML translations we always get very cryptic error messages.

These errors indicate that some of your (outbound?) ‘nodes’ are mandatory, but not populated. So some of the nodes (PERSON_INFO and EMP_ORG_POSITION_LST) seem to have a minimum value of 1, but the fields of this node are not populated and so the node stays empty.

If you change the minimum of these nodes to 0, the error should be gone. Or populate the nodes…

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Henry Tabingo]

Robert,

In CL 5.7 I tried changing the minimum values to 0 and recompiled, but was still getting the warning.

We just upgraded to CL 5.8 and the same translate no longer generated warning messages in the log file. Interesting!

Thanks for you help!

[Author]

Replies