ER7BatchAdaptor now appends the segment delimiter from the inbound data type properties to the pattern, if it is not a normal line break.

The individual messages built from the batch message now use the segment delimiter from the inbound data type properties instead of being hard coded to carriage return.

Switched some replaceAll statements to use StringUtils.remove instead for better performance.
Issue: MIRTH-2680
If Convert Line Breaks is off, only the segment delimiter is used in the batch adaptor now. If it is on, then it is used along with CRLF, CR, and LF.
Issue: MIRTH-2680
If both inbound and outbound data types is true, Convert Line Breaks on the inbound properties is now set to true if Convert LF to CR is true on either the inbound or outbound properties.
Issue: MIRTH-2672
NCPDPSerializer now uses StringUtils in transformWithoutSerializing to perform delimiter replacements.
Issue: MIRTH-2674
Remove BatchMessageProcessor because it is no longer used.
Issue: MIRTH-2684
Updated WebAdmin copyright year to 2013.
Issue: MIRTH-2683
MIRTH-2636: Overrode ScriptRuntime in Rhino so that we can check when a user is trying to compare a Donkey Status with a string. If they are trying to compare the status to SUCCESS or FAILURE, the correct strings are used instead (SENT/ERROR), and a server error is logged. If they are trying to compare with ACCEPTED or UNKNOWN, a server error is logged but the equality will always return false (because those statuses no longer exist).
DICOM data type migration is now working.

When importing a channel, connector, or transformer with DICOM as the source inbound data type, the attachment handler is now automatically set to DICOM if it was previously set to NONE.

When importing a channel, connector, or transformer with anything other than DICOM as the source inbound data type, the attachment handler is now automatically set to NONE if it was previously set to DICOM.
Issue: MIRTH-2610
MIRTH-2610: Added null check first in migrateConnector to prevent a NPE from being thrown when the metadata ID isn't known.
Column Names can now be set to the empty string.

The logger is now a singleton that is initialized on the fly, so deserializing an exiting delimited properties will no longer give a null pointer exception.

Invalid values are no longer allowed to be set and deployed for column names and column width columns.
Issue: MIRTH-2687
Moved configuration migration into ServerMigrator and relevant version migrator classes.

Added code to add/remove configuration entries for version 3.0.0.
Issue: MIRTH-2681
Fix column names or column width properties being deleted in some cases when other properties are modified.
Issue: MIRTH-2687
MIRTH-2691, MIRTH-2666: Updated ResponseSelector so that it grabs the correct response from the source connector's response map rather than the merged connector message's. This is because the merged connector message is created before the postprocessor executes and is never recreated. Any custom keys placed in the response map in the postprocessor (and the postprocessor entry itself) are placed in the source connector's map after the postprocessor finishes.
MIRTH-2682

Fixed problem with viewing messages in the message browser that contain invalid XML character(s).

Modified ObjectXMLSerializer so that it only puts the serialized data into a DOM document if it detects that the serialized data contains a Migratable object.

More work is needed to ensure that invalid XML characters are dealt with appropriately in all cases (see MIRTH-2692).
Fixed commandImportConfig in CLI to pass the expectedClass to ObjectXMLSerializer to that it can run pre-3.0.0 migration on the imported server configuration.
Issue: MIRTH-2499
Added 3.0.0 migration code to update the pruner's configuration category from 'Message Pruner' to 'Data Pruner'
Issue: MIRTH-2690
When destination connectors are imported, the response transformer data types are now set to the destination connector transformer's outbound data type. All response data type properties are set to the default values.
Issue: MIRTH-2685
Remove jmx.port when migrating mirth.properties to 3.0.0
Issue: MIRTH-2681
If a channel fails to deploy, it will now be removed from the deployed channel cache. Also the channel scripts will be removed from the script cache.
Issue: MIRTH-2505
When a source connector is imported, the number of filter/transformer steps now updates automatically.
Issue: MIRTH-2694