Waarp Depends on

This project depends on the following libraries:

  • NETTY (excellent NIO framework) from version 3.5 (NIO support) and from V3 of Waarp on Netty from version 4.1. 
  • Apache Commons IO from 2.3 (special file functions like wildcard support). 
  • Apache Commons Codec from 1.6 (Base64 support).
  • Apache Commons Compress from 1.4 (TAR and ZIP support).
  • Apache Commons Exec from 1.1 (external Exec support).
  • DOM4J from 1.6.1 and JAXEN from 1.1.1 (XML support), only used by the current implementation of the standard Ftp Server. It could be replaced very easily. 
  • optional: LOGBACK from 1.0.5, can be replaced by any logger facilities (default is Java native logger). Only used by the current implementation of the standard Ftp Server. It could be replaced very easily.
  • optional: JavaSysMon from 0.3.3  (from GoldenGate Common) to enable the CPU throtling. If the JRE supports native way, this is optional. If the CPU throtling is not required, it is optional.
  • A Database support: right now tested were H2 database engine ; partially tested are Oracle, PostGreSQL and MySQL/MariaDB support. Any new database could easily be implemented (only 3 functions are to be implemented). 
  • From Waarp project, two modules are necessary: Waarp Common (files support) and Waarp Digest (MD5 and other digests support) ; on most of the projects, Waarp Gateway Kernel is also needed (HTTP support) 
  • From Waarp project: optionally Waarp LocalExec (Local Execution Daemon support) and Waarp SNMP (SNMP support) which implies to have also SNMP4J jars
  • For FTP Client, Waarp uses FTP4J project.
  • Jackson JSON library from version 2.2