build.xml

Checkout Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
MIRTH-2242

The binding is now configurable on the WebServiceListener. Users have the ability to select from three available options. If default is selected, then any annotations defined on a custom webservice will be used, otherwise it will default to SOAP v 1.1, also the migrated setting.

A Binding enum was added under the server connectors and made available in the shared jar. This Binding property is now present on all WebServiceReceiverProperties. The actual WebServiceReceiver will set this value when creating/publishing the endpoint.

Issue: MIRTH-2242

  1. … 5 more files in changeset.
MIRTH-1891

A new AdvancedSettings dialog has been introduced for the file writer connector and currently only shows up for SFTP. This dialog allows the user to add key authorization, hostchecking as well as a table for other configurable options. An AdvancedSettingsDialog interface and SchemeProperties abstract class were added to facilitate creating dialogs for other schemes and their properties.

A new class, FileSystemConnectionOptions, was added to reduce the number of arguments in the FileConnector. The poolkey for sftp connections has been updated to now include the new properties which may be dynamically replaced. All other methods across other file schemes have been updated to reflect these changes.

  1. … 22 more files in changeset.
MIRTH-2276 and MIRTH-2759

-Added JSON support as a serializer and data type. For now, the JSON serializer is used only for JSON messages.

-Made pretty print setting in Message Browser and Administrator Settings more generic to support both XML and JSON.

-Updated message tree panel to support JSON.

-JSON trees are a bit different from XML trees. JSON trees can contain annotations indicating if the element type is an object or an array.

-Modified builders for nodes’ variables, descriptions, and paths to support JSON format

-.toString() now only gets appended to XML nodes.

-Modified MirthTreeNode to add annotations for JSON arrays and objects.

-Added JSON data type client and server plugins.

-Added token marker for JSON messages. Keyword highlighting still needs to be done.

-Renamed Serializer classes to be more generic instead of XML specific.

-Updated Jackson jars.

-Added JSON data type properties.

-Added JSON serializer.

-Modified JavaScript builder’s transformer function to parse JSON messages and templates to JSON.

-Updated filter/transformer mapper’s validate function to only do string replacements on strings.

-Modified Rhino’s JSON.stringify() to be able to convert Java objects into strings.

-Modified Rhino to override JavaScript’s arrays’ and objects’ .toString() methods to use JSON.stringify() instead.

  1. … 83 more files in changeset.
MIRTH-1717: Completely overhauled the JavaScript text editor to be more freaking awesome. Things included:

* Better whitespace / control character displays

* Line wrapping

* Code folding (any curly brace section)

* Tab / Shift+Tab multi-selected lines

* Auto-indentation within functions / loops / etc.

* Better Find/Replace functionality, more options, Find Next shortcut key

* Auto-completion for code / functions / classes / variables / etc. This scans our userutil package and automatically generates completion references for all the classes and methods within.

  1. … 98 more files in changeset.
The getViewerType method on the AttachmentViewer was deprecated and removed from all child classes in lieu of a new method that checks whether or not the content type for any given attachment is viewable by the viewer.

The RTFViewer and all references have been renamed to a more generic TextViewer. The JEditorPane now takes in the mime type corresponding to the attachment type when instantiating the pane.

Issue: MIRTH-2630

  1. … 14 more files in changeset.
MIRTH-3554: Renamed the Library resource to Directory. Refactored build files, etc.

The resource settings panel will now always prompt users before reloading libraries.

Log levels have been changed from ERROR to WARN when libraries can't be loaded. Also the Directory resource will now only log a warning rather than throwing an Exception.

A weight attribute has been added to the Directory resource so that it will always appear first in the drop-down menu.

  1. … 21 more files in changeset.
MIRTH-3554: A new set of plugin points have been added to allow shared resources for channels/connectors to be configured. There is a new "Resources" tab in the Settings view where resources can be added/modified. Each resource has a type, for example "Library", "Mirth Results", or "Database". The first resource cannot be removed, and by default it uses the Library type, and points to the custom-lib directory. Any new channel/connector created (as well as migrated channels/connectors) will use the custom-lib resource by default.

MIRTH-3553: The way Rhino context factories are created and used has been completely overhauled to allow isolated contexts with specific classloaders. This allows custom libraries to be included within Mirth Connect channels *without* a server restart. This applies not only to JavaScript contexts, but also to other places in Mirth Connect where custom libraries might be used, like the Web Service Listener, Database connectors, JMS connectors, and custom attachment handler. When a context factory change is detected, the associated script is automatically re-compiled with the new context (and new sealed/shared scope). A new ContextFactoryController has been added to take control of context factory creation/reloading; everything that needs a context factory will request it from the controller. The library resources added with MIRTH-3554 tie into the controller as well.

  1. … 110 more files in changeset.
Bouncy Castle jars are now being signed with SHA1 digestalg to fix web start issues when building with Java 7.

Adding bcprov-ext and bcpkix to Client and CLI to replace functionality that was removed in the latest bcprov release (1.51)

Issue: MIRTH-3540

  1. … 6 more files in changeset.
The manifest update and jar signing tasks can now run in parallel. The number of threads can be specified by passing in the ant properties "manifest_thread_count" and "signjar_thread_count"

Moved ant related jars to a separate ant folder and excluded them from the build.

Issue: MIRTH-3544

  1. … 4 more files in changeset.
MIRTH-3442: Updated Derby JDBC driver JAR references in the Ant build.
MIRTH-3328: Modified the File Reader/Writer to use the new invokeConnectorService method on the parent abstract class. Also pulled the method names into a separate class that both the client and server uses.
  1. … 6 more files in changeset.
MIRTH-2504: The Web Service Sender now allows users to override endpoint addresses. It works essentially the same way the service and port combo boxes do, except that only one location URI would (should) actually be defined in the WSDL.
  1. … 7 more files in changeset.
MIRTH-3326: Added the ability to host static resources on the HTTP Listener. Users can specify a context path, resource type, value, and content type, and any requests coming in that match the context path will automatically return the configured value. There are three resource types: File, Directory, and Custom. File just returns a specific file, while Directory allows clients to request any file in a directory (subdirectories are not included). Custom allows any arbitrary string to be returned. All fields are replaceable with Velocity.
  1. … 6 more files in changeset.
MIRTH-3327: Added framework for custom connector properties plugins. The ConnectorProperties class now contains a set of ConnectorPluginProperties objects, which represent additional properties that extensions can add to certain connectors. On the client side a new plugin point ConnectorPropertiesPlugin was added, which is used to show an additional properties section in the connector panel. Each plugin can choose which connectors it supports with the isSupported method. ConnectorPanel now includes all currently installed connector properties plugin panels, and selectively sets the visibility based on the current transport name (same as it does with the other properties panels). Invalid connector plugin properties are handled in a similar way to how invalid channels are handled. The main difference is that channels with invalid connector plugin properties can still be edited and deployed, and the plugin properties are removed on next save. The user is warned when attempting to edit/import a channel/connector if it contains such properties.

MIRTH-3328: Added new plugin point for connector service extensions. These have the ability to intercept connector service invocations and inject their own logic if need be. On the client side, connector properties plugins also have the ability to intercept the response returned from connector services and perform whatever UI actions they need to. The HTTP and Web Service connectors have been modified to use the new client framework for this, and implement the handleConnectorServiceResponse method.

MIRTH-3329: Connectors and connector properties plugins now have the ability to provide custom coloring, icons, tool-tips, etc. for displaying the connector type in the destination table. In addition, custom decorations from connector properties plugins can be used by the regular connector settings panel to perform the same decoration locally. The destination table now contains ConnectorTypeData objects instead of just the transport name, and the data contains the ConnectorTypeDecoration object which holds all the information needed. The HTTP and Web Service sender connectors have been modified to display a yellow "not configured" color when an HTTPS URL is detected.

  1. … 49 more files in changeset.
Added a Global Maps panel on the dashboard to show the global map and global channel maps for selected channels. This is implemented as another core plugin, "Global Map Viewer".

If User Roles plugin is installed, access to viewing the maps can be restricted.

Issue: MIRTH-3309

  1. … 7 more files in changeset.
Updated bcprov to the latest 1.5 beta that already has the manifest changes necessary and is signed by BC.

Issue: MIRTH-2963

  1. … 9 more files in changeset.
Committed an already signed bcprov with a modified manfiest. Exclude bcprov from being signed and having its manifest modified during the build process. bcprov 1.5 will not need to be modified, and could be used instead when it is released.

Issue: MIRTH-2963

  1. … 3 more files in changeset.
Updated the build to automatically add the following to all client-lib and extension jars:

Permissions: all-permissions

Codebase: *

Application-Name: Mirth Connect

Also unsigned bcprov-jdk16-144.jar and not-yet-commons-ssl-0.3.11.jar since we modify the manifest and the signatures are no longer valid. We re-sign the jar after modifying the manifest during the build process.

Issue: MIRTH-2963

  1. … 8 more files in changeset.
MIRTH-2849 and MIRTH-2915 - Auto generate javadocs for userutil packages during the build process. Include the user-api javadocs on the file system in docs/javadocs/user-api and host the javadocs under the root http context path /javadocs. Allow directory listing for this directory. Also disable serving the default Jetty favicon in the DefaultHandler.
  1. … 3 more files in changeset.
Fixed build reference to beta version of derby. The target this reference was in was only called manually.

Issue: MIRTH-2706

MIRTH-2636: Moved user-specific APIs into designated wrapper classes in the server/userutil and connect/userutil packages. The only classes which should reference anything in these userutil packages are JavaScriptScopeUtil and ValueReplacer. Nearly all non-deprecated method signatures from 2.x have been preserved in the 3.0 userutil wrappers, and deprecated as necessary. To that end, the MessageObject class has been added back as a wrapper class, and JSSU adds "messageObject" back into JavaScript scopes, to keep legacy compatibility. Every deprecated method also logs an error entry to the server log as well.
  1. … 38 more files in changeset.
Moved license file to /docs folder

Renamed /lib to /server-lib

Moved mirth-server.jar to /server-lib

Moved mirth-cli.jar to /cli-lib

Removed mirthdb automatic creation on build.

Changed default mirthdb path to /appdata/mirthdb

Renamed mirth-manager.jar to mirth-manager-launcher.jar

Issue: MIRTH-1713

  1. … 16 more files in changeset.
MIRTH-1700, MIRTH-2552: Updated the migration controller to call custom classes/code to handle server/schema migration, instead of just executing each delta script. The concept of a separate "schema version" is now gone; now SCHEMA_INFO.VERSION stores the product version (e.g. 3.0.0). Instead of simply iterating through the schema versions and calling each delta script, the migration controller now delegates that to custom Java classes (for now, just Migrate2_0_0 and Migrate3_0_0) that can call their respective delta scripts -and- do whatever other custom code may be necessary.

The channel table has been changed so that the entire serialized channel is stored in a single column. The ID, name, and revision columns remain, however. This is an example of where "custom code" is needed on server migration. Migrate3_0_0 executes all the delta scripts up to the 3.0.0 script (which renames the old channel table and creates the new one). Then it manually selects data out from the old table, builds up the 2.x model XML as a document, and stores the serialized data in the new table.

The migrateContents and migrateServerProperties functions that were in the migration controller have been moved to Migrate2_0_0, since the upgrade from 1.8.2 to 2.0.0 is the only place they were necessary anyway.

  1. … 47 more files in changeset.
MIRTH-2241

Added event pruning capability to the message pruner.

Renamed the message pruner plugin to "Data Pruner".

  1. … 20 more files in changeset.
Moved xstream converters that were overriding xstream classes into our own package and register the converters in ObjectXMLSerializer. Removed unused DateConverter and the com.thoughtworks packages.

Issue: MIRTH-1793

  1. … 19 more files in changeset.
MIRTH-2445, MIRTH-2346, MIRTH-2444: Completely changed how moving/renaming/deleting works in the File Reader.

Instead of "Delete After Read", there is now an "After Processing Action". You can select "None", "Move", or "Delete", depending on what you want to do after a message has been successfully processed through the channel. The Move-to Directory / File Name are still there, and apply to this action.

There are now two different error actions. The first, "Error Reading Action", determines what should happen when the file failed to be read in and processed by the channel.

The other one is "Error in Response Action", which determines what to do when the message was successfully processed, but the status of the selected response is ERROR. In this case, you can choose "After Processing Action", "Move", or "Delete". If "After Processing Action" is chosen (the default), ERROR responses will just cause the After Processing Action to be performed, and not do anything different.

In addition to the error move-to directory, there is also an error move-to file name. Both of these fields apply only to the Error Reading and Error in Response actions.

  1. … 6 more files in changeset.
Added Raw data type

Added two SerializationTypes that each data type must define (RAW or XML). Currently, the raw datatype uses RAW, and all other data types use XML. The SerializationType determines what datatype the transformed content is stored as, as well as what type of object msg and tmp will be in the transformer scripts.

DataType now stores the SerializationType so the transformer executors can utilize them.

Issue: MIRTH-2275

  1. … 42 more files in changeset.
BatchAdaptor has now been isolated from the Serializers.

DataType now contains a BatchAdaptor.

Plugin classes have been updated to accommodate this change.

DataType (and related) have been moved from model to server since they are not used by the client.

AutoResponder (and related) have been moved from model to server since they are not used by the client.

Issue: MIRTH-2357

  1. … 46 more files in changeset.
Rewrote the JMS connectors for Mirth Connect 3.0

Highlights:

- The JMS connectors now have the ability to automatically reconnect to the JMS broker if the connection goes down.

- JMS message acknowledgments are sent only after the message has been persisted by Mirth Connect, for guaranteed delivery.

Issue: MIRTH-1945

  1. … 56 more files in changeset.
Data Types now have separate inbound and outbound properties.

Inbound properties consist of SerializationProperties, BatchProperties, and ResponseGenerationProperties.

Outbound properties consist of DeserializationProperties, ResponseValidationProperties, and Template SerializationProperties.

The data types dialog has been completely revamped.

The "Properties" button is gone.

Both inbound and outbound properties are now visible once a connector is selected.

The property editor panel (tree and description) has been written from scratch.

The old editor (bean version) and beaninfo classes have been removed. The property descriptor information now comes from the respective Property Group object.

X12 data type has been combined with EDI. They are now referenced as "EDI / X12".

Updated DataType client and server plugins.

Moved getDefaultProperties from DataTypeDelegate to DataTypeClientPlugin since the server doesn't use it.

Serializers now take in SerializerProperties (which contains Serialization, Deserialization, and Batch properties).

MIRTH-2274

Issue: MIRTH-2273

  1. … 221 more files in changeset.