OHMPI 3.0: NetBeans IDE Resets Dateformat Element In Object.xml Back To "MM/dd/yyyy" Default On Save
Last updated on MARCH 08, 2017
Applies to:Oracle Healthcare Master Person Index - Version 3.0 and later
Information in this document applies to any platform.
OHMPI 3.0 using NetBeans 8.0.2
NetBeans IDE resets dateformat element in object.xml back to "MM/dd/yyyy" default on save.
The NetBeans IDE installed with the OHMPI development environment will always set the dateformat element in the object.xml configuration file back to the default value of "MM/dd/yyyy" any time the project is saved within the UI. This is irrespective of any direct editing of the xml files. For example, if the initial project is created with the dateformat of "yyyyMMddHHmmss", which is the HL7v2 DTM and HL7v3 TS common format, and then the project is later updated to either add a field or change a configuration through the UI, upon saving the project, the previously configured dateformat value is reset back.
STEPS TO REPRODUCE:
2. Generate application files, Clean and build the project
3. Check the object.xml file > 'dateformat' field - it corresponds to selected option
4. Edit the project's configuration (e.g. changed the Match Type for PersonCatCode) and save
5. Check again the project's object.xml file. The 'dateformat' is changed to default.
Unfortunately, instead of causing errors during loading of data, the Java SimpleDateFormat parser made decisions based on a relationship between the format and the string of data passed in the date fields.
It also causes to question the use of the UI for updates to the object and configuration favoring direct editing of the xml files so as not to cause unexpected changes to the configuration through the UI.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms