The public jadice® server java API for developers is powerful and open for a flexible integration of jadice® server functionalities. As a reference for developers the javadoc documentation of the public jadice® server distribution API will help you to develop custom applications that use functionalities of jadice® server.
For recent API documentations of the provided jadice® modules please take a look at the folder javadoc/client-lib of the current jadice® server distribution.
In this folder you will find a series of jar files containing the javadoc information of provided jadice® server modules which are supposed to be integrated into own client applications.
In order to extend the jadice server® with own server side functions please take a look at the folder javadoc/server-lib.
All packages and classes contained in the jadice® server client API javadoc documentation and the jadice® server API javadoc documentation are public jadice® server API and may be freely used for embedding jadice® server functionality within own applications, respectively extending jadice server with own functions. This API is fully supported. If any questions or problems with public API classes or their functionalities occur, feel free to contact us. We are pleased to help you in any way.
Developers may possibly recognize internal packages in the jadice® server distributions, too. Packages which follow a package naming convention like com.levigo.*.internal.* where the asterisk (*) substitutes any zero or more characters as a wildcard are private API and must not be used directly.
Internal packages, contained classes and their particular functionalities are intellectual property of levigo holding gmbh.
All classes and even particular parts of functionalities contained in internal packages are private and not part of the public jadice API.
It is strongly advised not to use these classes and their API in any direct way. Direct use of these classes or even of their particular functionalities is not supported and may cause undesirable behaviour. These internal classes and their functionalities may change in each release without having any vested interest or title to prior internal API or any functionality.
Anyhow, direct use of internal API is done without any warranty; even without the implied warranty of merchantability or fitness for a particular purpose. levigo holding gmbh is not liable for any direct, indirect, incidental, special, exemplary or consequential damage caused or done by direct use of the internal API.