trunk

Issue: MIRTH-1040

MIRTH-1700

Fixed problem in ImportConverter3_0_0.migrateJmsReceiverProperties if an error occurred while reading the old connection properties - needed to log an error and fail gracefully.

Moved the Version enum from DMC into it's own file.

Renamed Migrator to ServerMigrator.

Rewrote migration code in Migrate2_0_0 so that it does migrates global scripts and server properties manually, without referencing controller classes - fixes errors when migrating from version 1.8.x.

Modified Migrate2_0_0, Migrate3_0_0 and ServerMigrator so that they do not reference any controller classes.

Added additional utility methods to DonkeyElement.

Changed the dialog so that it is created/disposed on open/close instead of using setVisible().

Issue: MIRTH-2569

Issue: MIRTH-2594

Don't set forceQueue to false when starting the connector until after onStart(). This ensures the connector does not try to send anything until after it has finished starting.

Issue: MIRTH-1040

AlertSender now dispatches events instead of calling the alert controller directly.

AlertSender is now constructed with either channelId or a connector message. The connector message allows it to dispatch error events for a specific connector.

Events dispatched from the AlertSender that do not have a metaDataId associated will trigger if any of the connectors for that channel are enabled.

Events dispatched from the AlertSender will only trigger if the User Defined Transformer event type is checked.

User javascript code for sending alerts should remain identical to how it was in 2.x

Cleaned up the error message builder to only append new lines when needed.

Issue: MIRTH-2621

They now work similarly to how channels are import/exported.

The command token is now importalert/exportalert (instead of importalerts/exportalerts).

Issue: MIRTH-2633

Issue: MIRTH-2548

The nextMetaDataId element has been removed from Migrate3_0_0. This isn't needed here because it's added in ImportConverter3_0_0.

MIRTH-2499

Fixed MigratableConverter.unmarshal() so that it reads the object's version number from the top-level document element, rather than each migratable element since it is now only on the document element.

Also fixed MigratableConverter.unmarshal() so that it reads the current object's class type from the unmarshalling context, rather than trying to determine it from the element's name (this would not work on child elements since the child element names are field names and not class names).

Moved elementToXml() and elementFromXml() out of XmlUtil and into a new MigrationUtil class, since XmlUtil is exposed to the User through the TemplateValueReplacer, these methods didn't really need to be there.

Removed hardcoded "3.0.0" version number and made the Server and Client each initialize ObjectXMLSerializer with the current server version on startup.

Moved compareVersions() and normalizeVersion() from MigratableConverter into MigrationUtil.

Restored previous behavior when importing channels in the message browser so that it prompts the user when importing a channel from a previous version of Mirth Connect.

CodeSnippetTypeHandler has been removed. It was only being used to facilitate selecting/inserting the CODE_TYPE column for code templates, and that column is no longer being stored directly.

Migrate3_0_0 has been updated to select old code template data, manually build the 2.x model document and insert it into the new code template table.

The migrateChannelTable portion of Migrate3_0_0 has been updated to include the nextMetaDataId element in the channel document, which was neglected beforehand.