https://doc.sibvisions.com/ 2026-04-17T17:58:14+00:00 https://doc.sibvisions.com/ https://doc.sibvisions.com/lib/tpl/material/images/favicon.ico text/html 2020-06-19T11:48:13+00:00 https://doc.sibvisions.com/jvx/common/setup/compile?rev=1592567293&do=diff The source code is available at sourceforge. Simply use svn and check out the repository, e.g.: svn checkout https://svn.code.sf.net/p/jvx/code/trunk/java/library jvx-library The path: trunk/java/library is enough. It's not necessary to checkout the whole trunk. text/html 2025-06-20T10:51:38+00:00 https://doc.sibvisions.com/jvx/common/setup/connectin_pooling?rev=1750416698&do=diff Our DBAccess supports a simple configurable connection pool with ConnectionPoolProvider. The ConnectionPoolProvider creates a default DataSource and an IConnectionPool. We currently use Hikari and Tomcat for our connection pool implementation. With Hikari we have an independent solution and Tomcat will only work on Tomcat application servers. text/html 2025-06-20T10:06:15+00:00 https://doc.sibvisions.com/jvx/common/setup/connectin_pooling_legacy?rev=1750413975&do=diff DBAccess supports connection pooling by the interface com.sibvisions.rad.persist.jdbc.IConnectionPool. DBAccess gets and releases connections from the pool with public Connection getConnection() throws SQLException; public void releaseConnection(Connection pConnection); text/html 2020-06-19T11:44:02+00:00 https://doc.sibvisions.com/jvx/common/setup/dbindependent_config?rev=1592567042&do=diff JVx allows the development of database-independent applications. However, access to the database requires specific information, such as host name, database port, database name, username, password, etc. This information is usually saved in a configuration file. We use the applications configuration config.xml that is available for our application on the server side: text/html 2018-02-02T12:53:19+00:00 https://doc.sibvisions.com/jvx/common/setup/deployment_descriptor?rev=1517575999&do=diff The configuration of a deployment descriptor is required for the integration of JVx in an application server. The deployment descriptor is usually an XML file called web.xml. For Apache Tomcat, for example, the file should be constructed as follows: text/html 2020-06-08T16:06:03+00:00 https://doc.sibvisions.com/jvx/common/setup/external_app_folders?rev=1591632363&do=diff JVx searches applications in a specific folder structure (rad/apps). The folder structure has to be available. Otherwise, it's not possible to use an application. However, sometimes this requirement is too strict because you can't store applications outside of this folder structure. text/html 2020-06-15T14:53:22+00:00 https://doc.sibvisions.com/jvx/common/setup/external_config?rev=1592232802&do=diff Every application has its own application zone with one configuration file. The name of the file is config.xml. This file should contain the whole configuration for your application. Sometimes your configuration has external dependencies or you have a different configuration for your test and production system. In that case, it's better to use an external configuration which contains all system dependent properties. Such an external configuration will reduce your deploment/build effort because … text/html 2024-09-04T15:30:26+00:00 https://doc.sibvisions.com/jvx/common/setup/java16plus?rev=1725463826&do=diff Starting with Java 16, JVx running on an application server like Tomcat, requires some additional settings. Optional This is relevant for resource unlocking, but not necessary if you restart the application server after every deployment. --add-opens=java.desktop/javax.imageio=ALL-UNNAMED text/html 2025-06-16T15:07:24+00:00 https://doc.sibvisions.com/jvx/common/setup/maven?rev=1750086444&do=diff JVx is available in all public Maven repositories, e.g., http://search.maven.org/ Use following dependency in your pom.xml: <dependencies> <dependency> <groupId>com.sibvisions.jvx</groupId> <artifactId>jvxall</artifactId> <version>3.1</version> </dependency> <dependencies> text/html 2020-06-19T11:33:09+00:00 https://doc.sibvisions.com/jvx/common/setup/plugins?rev=1592566389&do=diff It's possible to use custom plugins to extend or configure the JVx' server implementation. Since JVx 2.1, it's possible to implement custom plugins. The interface is com.sibvisions.rad.server.plugin.IServerPlugin and has a small number of methods: text/html 2020-07-28T10:06:01+00:00 https://doc.sibvisions.com/jvx/common/setup/zones?rev=1595930761&do=diff We recommend a specific file structure for JVx applications because every JVx projects should use the same structure. This makes it easier to maintain applications as everything is standardized. Our recommended structure is: <basedir> |- rad (Configuration.getConfigurationDir()) |- apps (Configuration.getApplicationsDir()) |- <appname> |- config.xml (Configuration.getApplicationZone(<appname>)) |- server (Configuration.getServerDir()) |- …