Values within the code template/library exported xml file are inconsistent

[rbeckman-nextgen]

In Mirth Connect 3.3.0, exporting the same code template libraries yields different results; the fields within the tag seem to get scrambled around after testing multiple exports. No modifications were made to the libraries or templates. The channel IDs under the tag seem to switch around as well. The change in xml file happens most consistently after a restart of the Connect service.

See below for examples:

First export {code}

DESTINATION_FILTER_TRANSFORMER GLOBAL_DEPLOY CHANNEL_UNDEPLOY DESTINATION_DISPATCHER GLOBAL_UNDEPLOY CHANNEL_BATCH GLOBAL_PREPROCESSOR GLOBAL_POSTPROCESSOR SOURCE_RECEIVER CHANNEL_ATTACHMENT CHANNEL_DEPLOY CHANNEL_POSTPROCESSOR DESTINATION_RESPONSE_TRANSFORMER CHANNEL_PREPROCESSOR SOURCE_FILTER_TRANSFORMER

{code}

Second export after a restart of the Connect service gives a different output {code}

GLOBAL_UNDEPLOY DESTINATION_RESPONSE_TRANSFORMER CHANNEL_DEPLOY GLOBAL_PREPROCESSOR DESTINATION_DISPATCHER DESTINATION_FILTER_TRANSFORMER CHANNEL_UNDEPLOY CHANNEL_ATTACHMENT GLOBAL_DEPLOY GLOBAL_POSTPROCESSOR CHANNEL_PREPROCESSOR SOURCE_FILTER_TRANSFORMER SOURCE_RECEIVER CHANNEL_BATCH CHANNEL_POSTPROCESSOR

{code}

Imported Issue. Original Details: Reporter: calvinouk Created: 2015-10-19T15:47:38.000-0700

[rbeckman-nextgen]

This is expected because those are regular Sets, not linked or anything. Those two exports are completely valid, it doesn't matter at all what order that context types are in.

However we could switch to a linked set in those cases, so that a diff tool won't complain about it.

Imported Comment. Original Details: Author: narupley Created: 2015-10-19T15:52:03.000-0700

[rbeckman-nextgen]

"Settings->Backup Config" and 'exportcfg' in CLI are impacted as well.

vote +1 because i think that exports and backups should give reproducible results

Imported Comment. Original Details: Author: aloyse Created: 2015-10-19T23:51:43.000-0700