•  
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fixed adding the same content type multiple times to the message browser advanced filter overwriting all but the most recent search string.…
Fixed adding the same content type multiple times to the message browser advanced filter overwriting all but the most recent search string.

Fixed searches on destination raw content incorrectly using the source raw instead of source encoded

MIRTH-2570

Issue: MIRTH-2448

    • -61
    • +28
    ./sqlserver/sqlserver-message.xml
  1. … 5 more files in changeset.
The following fields are now included in the Message Browser quick search:…
The following fields are now included in the Message Browser quick search:

Message ID

Connector Name

Custom meta-data columns (string-type only)

Issue: MIRTH-2528

  1. … 3 more files in changeset.
Replaced use of the "string_agg" aggregate function in the message browser in Postgres with the "array_agg" function, which is supported by Postgres >= 8.4. The former is only available in >= 9.0.…
Replaced use of the "string_agg" aggregate function in the message browser in Postgres with the "array_agg" function, which is supported by Postgres >= 8.4. The former is only available in >= 9.0.

Tested and verified that there are no other obvious problems that occur when using Postgres 8.4.

Mirth Connect 3.0 now supports Postgres >= 8.4

Issue: MIRTH-2341

Allow the "!=" operator for custom String metadata searches…
Allow the "!=" operator for custom String metadata searches

String metadata searches now use "=" operator instead of the text version "EQUALS". This produced unnecessary complexity.

Removed TEXT_EQUALS conditions from the message queries.

Fixed a potential NullPointerException when using Timestamp custom metadata if the timestamp value for a message was null.

Issue: MIRTH-2522

  1. … 3 more files in changeset.
Changed length of VARCHAR columns PERSON_PASSWORD.PASSWORD and ALERT.NAME from 256 to 255. We received a report that VARCHAR(256) caused an error when creating the database schema in MySQL.…
Changed length of VARCHAR columns PERSON_PASSWORD.PASSWORD and ALERT.NAME from 256 to 255. We received a report that VARCHAR(256) caused an error when creating the database schema in MySQL.

Issue: MIRTH-2541

Moved channel tags from the Channel object to the ChannelProperties object. Also removed the associated table and queries, since this change removes the need for those. The DefaultChannelController …
Moved channel tags from the Channel object to the ChannelProperties object. Also removed the associated table and queries, since this change removes the need for those. The DefaultChannelController now gets the tags directly from the channels, which are pulled from the channel cache.

Issue: MIRTH-2548

  1. … 9 more files in changeset.
MIRTH-2537

- Prevent potential deadlocks by ensuring that only one pruner process can execute at one time (additional requests to start the pruner will be ignored if the pruner is already running)

MIRTH-2496

- Refactored/optimized/cleaned up much of the pruner code (it is now contained in a single MessagePruner class, rather than separate With/WithoutArchiver classes)

MIRTH-2539

- Added the ability to manually start and stop the pruner from the pruner settings pane (archiver settings can now be specified when the pruner schedule is disabled)

- Added panel above the pruner schedule that displays various status information about the pruner (current state, start/elapsed time, info on last process, next scheduled time)

MIRTH-2544

- Updated the Quartz Scheduler library to version 2.1.7 and updated the code in MessagePrunerService to use the new API.

  1. … 17 more files in changeset.
Updated Derby's message archiver query so that it is consistent with the pruning query, which checks the received_date on the d_m table rather than the d_mm table. In the future, we may update Derby t…
Updated Derby's message archiver query so that it is consistent with the pruning query, which checks the received_date on the d_m table rather than the d_mm table. In the future, we may update Derby to check on d_mm.received_date as the other databases do (MIRTH-2471).

Issue: MIRTH-1699

Removing SQL Server 2000 files since we are now only supporting version 2005 and above.…
Removing SQL Server 2000 files since we are now only supporting version 2005 and above.

Issue: MIRTH-2496

    • -77
    • +0
    ./sqlserver2000/sqlserver2000-channel.xml
    • -192
    • +0
    ./sqlserver2000/sqlserver2000-database.sql
    • -48
    • +0
    ./sqlserver2000/sqlserver2000-statistic.xml
    • -54
    • +0
    ./sqlserver2000/sqlserver2000-configuration.xml
    • -47
    • +0
    ./sqlserver2000/sqlserver2000-codeTemplate.xml
    • -127
    • +0
    ./sqlserver2000/sqlserver2000-event.xml
    • -75
    • +0
    ./sqlserver2000/sqlserver2000-alert.xml
    • -39
    • +0
    ./sqlserver2000/sqlserver2000-script.xml
    • -127
    • +0
    ./sqlserver2000/sqlserver2000-user.xml
Fixed error in the alert SQL code for Derby.…
Fixed error in the alert SQL code for Derby.

Removed old alert tables in derby-database.sql.

Issue: MIRTH-2530

Removed old alert tables in sqlserver-database.sql…
Removed old alert tables in sqlserver-database.sql

Issue: MIRTH-2496

MIRTH-2497

MIRTH-2530

Fixed errors with the message pruner/archiver when using MySQL.

Removed old alert tables in mysql-database.sql.

Issue: MIRTH-2497

Fixed errors with the message pruner/archiver and the alert system when using Oracle.…
Fixed errors with the message pruner/archiver and the alert system when using Oracle.

Issue: MIRTH-2498

  1. … 2 more files in changeset.
Updated SQL code for Derby, MySQL and Oracle to support the latest changes to the alerts system.…
Updated SQL code for Derby, MySQL and Oracle to support the latest changes to the alerts system.

Issue: MIRTH-2530

MIRTH-2496

MIRTH-2382

Added Microsoft SQL Server support for Mirth Connect 3.0

SQL Server >= 2005 is supported.

Tested with SQL Server 2005 Express and SQL Server 2012 Express on Windows 7 32-bit.

    • -124
    • +56
    ./sqlserver/sqlserver-database.sql
    • -54
    • +81
    ./sqlserver/sqlserver-channel.xml
    • -0
    • +415
    ./sqlserver/sqlserver-message.xml
    • -48
    • +0
    ./sqlserver/sqlserver-statistic.xml
    • -32
    • +18
    ./sqlserver/sqlserver-codeTemplate.xml
    • -26
    • +20
    ./sqlserver/sqlserver-script.xml
    • -35
    • +28
    ./sqlserver/sqlserver-configuration.xml
  1. … 16 more files in changeset.
Implemented alerting for main (3.x) (excluding import/export and channel selection)…
Implemented alerting for main (3.x) (excluding import/export and channel selection)

Added event streaming architecture.

Connectors now dispatch events on error instead of sending alerts directly.

Added an alert worker which listens for the events to determine whether an alert should be sent.

Alerts now have separate summary and edit panes.

Alerts can now route the alert template to another channel, in addition to sending an email.

Channel state changes now dispatch a channel event.

Mirth now passes an event dispatcher to Donkey.

Removed some outdated event code in donkey that wasn't being used.

Removed the donkey event table.

Renamed old EventController to SystemEventController (This is now considered deprecated and will likely be removed soon).

MIRTH-2530

MIRTH-2531

MIRTH-2532

  1. … 104 more files in changeset.
MIRTH-2498

Added Oracle support for Mirth Connect 3.0

Oracle >= 11gR2 is supported (11gR2 released in 2009).

Tested with Oracle 11gR2 Express Edition on Fedora Linux.

Modified custom meta data column types in order to achieve compatibility with Oracle. Custom types are now: String, Number, Boolean, Timestamp.

Modified postgres, mysql, derby queries as needed to work with the code changes made to support Oracle (for example, updated any MyBatis select queries that returned a map to return a more specific result type instead, since returning a map caused problems w/ Oracle).

  1. … 40 more files in changeset.
Cleaned up the Postgres query file in Donkey so that it is easier to port it to support other databases.…
Cleaned up the Postgres query file in Donkey so that it is easier to port it to support other databases.

Removed the "removeChannel" query since it is not needed.

Removed the channel statistic query files for Postgres and Derby since they are not used and are no longer loaded.

Issue: MIRTH-2512

  1. … 1 more file in changeset.
MIRTH-2511: Fixed when Ignore Case option is selected, the selected search operator is still used.…
MIRTH-2511: Fixed when Ignore Case option is selected, the selected search operator is still used.

MIRTH-2510: Return partial matches when searching by server id.

MIRTH-2497

Added MySQL support for Mirth Connect 3.0

MySQL >= 5.0 is supported.

Tested with MySQL versions: 5.0.96, 5.5.30, 5.6.10

  1. … 21 more files in changeset.
Fixed error that prevented messages from being archived/pruned when the pruning metadata/content age is set to zero.
Fixed error that prevented messages from being archived/pruned when the pruning metadata/content age is set to zero.
Updated Derby support for the new message pruner/archiver.…
Updated Derby support for the new message pruner/archiver.

Removed unnecessary sql in the Message.prunerDeleteMessageContent query for Postgres.

Issue: MIRTH-1699

  1. … 2 more files in changeset.
MIRTH-2426

Maps and Errors are now stored in the Content table (d_mc) rather than the Metadata table (d_mm)

ConnectorMessage now holds a MapContent and ErrorContent instead of the data directly, this way the channel can know if it has already persisted either of them.

ContentType now has 3 sub-types (Message, Map, Error).

ContentType codes are now integers instead of characters.

MIRTH-2443

The encryptor has been moved out of the channel (and sub-objects) and into the JDBCDao directly. There is no need to hold both the unencrypted and encrypted content in memory during the duration of the message being processed. At the Dao level, the message is encrypted if necessary because storing into the DB. Encrypted messages are decrypted automatically at the Dao level as well.

PassthruEncryptor has been removed.

MessageContent now only stores a boolean of whether the content in it is encrypted. This more closely matches the content table.

Removed various encrypt/decrypt methods that are no longer necessary.

MIRTH-2442

Fixed encrypted queued messages not being able to be decrypted if channel encryption was disabled.

MIRTH-2464

DonkeyDao is now used instead of MyBatis when retrieving connector messages for the message browser/exporter. This provides a performance bonus of roughly 40% for this stage of the retrieval.

MIRTH-2467

Added Errors column to the message browser to replace the Response Sent/Status column

This column indicates whether a Processing, Postprocessor, or Response error occurred in the message (or Multiple). This is necessary because we no longer retrieve the error (or maps) during the initial search.

The ConnectorMessage stores an errorCode during processing which indicates which errors occurred, using bitwise storage.

MIRTH-2436

If the response transformer sets the message status to QUEUED but queueing is disabled, a Response Error will now be stored. This allows both the original Processing Error and the Response Error to be saved and viewed. This particular Response Error is not stored when the status is fixed before the response transformer, because the connectors themselves often set the status to QUEUED unbeknowst to the user.

MIRTH-2462

Added tooltips to the Message Browser columns.

Refactored the columns to make adding/modifying them easier in the future.

Added minimum width on Connector column

MIRTH-2466

Added Orig. Received Date to the message browser, using the date from the message table.

Misc.

Re-added toString method in Response object as it is needed to display a value in the message browser maps tab.

Flipping the boolean returned in FilterTransformerResult now that the logic has been reversed. (Except for the ones that were already previously flipped)

Ran the formatter.

Issue: MIRTH-2426

  1. … 69 more files in changeset.
Added message archiving capability to the message pruner. (MIRTH-1699)…
Added message archiving capability to the message pruner. (MIRTH-1699)

Rewrote the message export code into a unified engine that is used both by the archiver and the message browser export dialog. Created a MessageWriter interface along with an implementation that writes messages using Apache VFS. Also created a wrapper implementation to support compressing exported message files into an archive.

Created a new unified message export UI panel used in both the pruner settings panel and the message browser export dialog, to accompany the new export engine.

Rewrote the message import code and created a new message import dialog to support importing messages in the various formats now supported by the archiver/exporter.

Added the ability to import messages from the server filesystem. (MIRTH-2311)

Restored the pruner block size option that was removed earlier. (MIRTH-2414)

Added the ability to disable the message pruner completely. (MIRTH-2413)

    • -11
    • +107
    ./postgres/postgres-message.xml
  1. … 82 more files in changeset.
Added message send date to the connector message and message browser. (Date right before message was sent for destination connectors)…
Added message send date to the connector message and message browser. (Date right before message was sent for destination connectors)

Added message response date to the connector message and message browser. (Date right before response is sent for source connector, date right after response is received for destination connectors)

Renamed dateCreated on message and connectorMessage to receivedDate

Renamed Date & Time on message browser to Received Date

Removed attemptedResponse and responseError from the message.

Added responseErrors to the connector message.

Send Attempts now increments to one on the source connector if it attempted to send a response.

The Reply Sent column in the message browser has been renamed to Response Status. (SENT, ERROR, --)

Response Status now uses Send Attempts and Response Error from connector message to generate its value.

Removed VMRegistry class as it is no longer being used.

Removed getMessageContentFromResultSet method in JDBCDao as it is no longer being used.

Issue: MIRTH-2137

  1. … 41 more files in changeset.
MIRTH-1546: Only global scripts are now stored in the database, and all template storage / controller references have been removed (the database schema version has been updated as well).
MIRTH-1546: Only global scripts are now stored in the database, and all template storage / controller references have been removed (the database schema version has been updated as well).
    • -0
    • +1
    ./deltas/derby-9-10.sql
    • -7
    • +1
    ./sqlserver2000/sqlserver2000-database.sql
    • -0
    • +1
    ./deltas/mysql-9-10.sql
    • -32
    • +0
    ./sqlserver2000/sqlserver2000-template.xml
    • -0
    • +1
    ./deltas/sqlserver-9-10.sql
    • -0
    • +1
    ./deltas/oracle-9-10.sql
  1. … 16 more files in changeset.
Added a "Deleted Connectors" row to the message browser advanced filter. It does what you would expect it to.…
Added a "Deleted Connectors" row to the message browser advanced filter. It does what you would expect it to.

Cleaned up advanced filter text, alignment, and size.

ItemSelectionTable and TableModel now have the option to show the key column. Advanced Filter now shows the key column.

The search queries now use exclusion logic if the Deleted Connectors is selected, and inclusion logic if it is not selected.

Issue: MIRTH-2390

  1. … 11 more files in changeset.
Added Response Transformer to the destination connector.…
Added Response Transformer to the destination connector.

Added Response Transformer edit pane to destination connector.

Implemented back-end Response Transformer logic.

Added Response Transformed Content Type.

transformWithoutSerializing() can now return null.

Fixed issue with map variables added in filter steps not showing up for subsequent filter steps or in the transformer.

Fixed issue with response maps always being stored regardless of storage settings.

MIRTH-1663

MIRTH-2370

MIRTH-2368

Issue: MIRTH-2118

  1. … 54 more files in changeset.
Converted varchar and text fields to the nvarchar type for the MS SQL Server database schema. This improves performance in SQL Server and allows storage of unicode strings.…
Converted varchar and text fields to the nvarchar type for the MS SQL Server database schema. This improves performance in SQL Server and allows storage of unicode strings.

MIRTH-1759

MIRTH-2092

    • -73
    • +73
    ./sqlserver/sqlserver-database.sql
Data type was pointing to the wrong property in the mybatis configuration …
Data type was pointing to the wrong property in the mybatis configuration

Issue: MIRTH-2250