JPOX is an Open Source implementation. It is written by a small number of people to perform complicated tasks. The JPOX experts work on this largely in their spare time and, though they do provide a level of free "forum-based" support, cannot be expected to provide answers to all questions in as timely manner as they would like. Users of this software are expected to utilise the extensive documentation, and utilise the free forums to obtain the answers they require.
JPOX is an Open Source project and so the source code is available where companies choose that option. This is clearly not convenient for the majority of companies who prefer something ready-made to allow an optimised deployment of JPOX into priority projects. For this reason we aim to provide a multi-tier support framework so that businesses can choose what suits them best.
These are detailed below.
If you or your company requires support for your use of JPOX please contact us via email to arrange your support with andy AT jpox DOT org. If you require a more advanced support arrangement than those listed then we are open to discuss your requirements.
The JPOX product lifecycle from release to retirement is as follows.
Active: patches/bug fix releases may be issued on regular basis. Mature: patches/bug fix releases may be issued on Official Support basis. Retired: patches/bug fix releases only on exceptional cases on Extended Support basis. Users are encouraged to upgrade their software.
JPOX is built to run on many configurations, including J2SE from many vendors and versions. The following table lists the availability period for corrective and evolutive maintenance of JPOX corresponding to a J2SE. Upon retirement, users are encouraged to upgrade their J2SE and JPOX versions.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||