http://doc.sibvisions.com/ 2026-06-13T08:44:28+00:00 http://doc.sibvisions.com/ http://doc.sibvisions.com/lib/tpl/material/images/favicon.ico text/html 2024-11-18T10:34:26+00:00 http://doc.sibvisions.com/de/jvx/common/util/loggerfactory?rev=1731926066&do=diff Ohne Log Mechanismen ist die Software Entwicklung bei weitem anstrengender als es sein müsste. Aus diesem Grunde ist bereits im Kern von JVx ein Log Mechanismus verankert. Durch UIComponent werden folgende Methoden bereitgestellt: public void info(Object... pInfo) public void debug(Object... pInfo) public void error(Object... pInfo) text/html 2024-11-18T10:35:28+00:00 http://doc.sibvisions.com/jvx/common/util/loggerfactory?rev=1731926128&do=diff Without log mechanisms, software development is a lot more arduous than it needs to be. For this reason, a log mechanism is included in JVx. The following methods are provided via UIComponent: public void info(Object... pInfo) public void debug(Object... pInfo) public void error(Object... pInfo) text/html 2024-11-18T10:41:03+00:00 http://doc.sibvisions.com/reactui/logging?rev=1731926463&do=diff The application itself logs messages in Javascript console of your browser (developer tools). The network tab in developer tools shows all requests, the payload and responses. This is very helpful for debugging. If you want to know what's happening on server-side. This is not enough. The server-side runs on a Java application server like Tomcat or Wildfly. To enable logging on server-side, simply do following: text/html 2020-07-03T12:51:30+00:00 http://doc.sibvisions.com/applications/configure_logging?rev=1593780690&do=diff JVx uses standard JDK logging API or log4j. If you don't use a custom logging.properties file, the log mechanism won't work as expected because of standard log settings of JRE/JDK: The default logging.properties file sets the global level to: .level= INFO and also the console log handler level, to: text/html 2021-06-30T08:21:23+00:00 http://doc.sibvisions.com/visionx/visionx_logging?rev=1625041283&do=diff VisionX starts an embedded application server (Tomcat) and an embedded database (PostgreSQL). Especially log output from the application server is interesting. If you use logging in your application in the live preview, you won't see the message without enabling VisionX logging. text/html 2025-06-23T13:31:40+00:00 http://doc.sibvisions.com/visionx/use_log4j?rev=1750685500&do=diff This is a very technical article and it's only relevant for developers or experienced users. Usually the integrated log mechanism is good enough, but from a developer point of view it might be helpful to use a different log mechanism. Every application will be created with a text/html 2026-03-04T09:53:12+00:00 http://doc.sibvisions.com/visionx/faq_tech?rev=1772617992&do=diff Firewall setup VisionX requires http (port 80) and https (port 443) to cloud.sibvisions.com for e.g. solution store, cloud management and other features. Which database & which platform are you using? VisionX supports all major database vendors: Oracle, Postgres, MySql/MariaDB, MS Sql, DB2, EDB and Hana. We're using Java and support all Java application servers like: Tomcat, Wildfly, Glassfish, etc. You can deploy the created application with VisionX or manually, to the cloud, on premise, or … text/html 2020-06-15T14:40:43+00:00 http://doc.sibvisions.com/jvx/common/util/log4j?rev=1592232043&do=diff If you want to use log4j or log4j2 instead of standard Java logging API for your application, simply add the logger factory configuration to your classpath. First, create a file with the name loggerfactory.properties in one of your source/resource directories. Don't use a package name! text/html 2025-06-23T13:35:31+00:00 http://doc.sibvisions.com/jvx/developer_documentation?rev=1750685731&do=diff Client Server Common text/html 2025-06-23T09:44:19+00:00 http://doc.sibvisions.com/visionx/howtos?rev=1750671859&do=diff This is the place for VisionX HowTos. text/html 2024-02-19T13:19:28+00:00 http://doc.sibvisions.com/reactui/home?rev=1708348768&do=diff This is the place for the documentation of our react UI. text/html 2022-11-29T12:15:02+00:00 http://doc.sibvisions.com/applications/projx?rev=1669724102&do=diff text/html 2020-06-15T10:24:16+00:00 http://doc.sibvisions.com/workflow/quartz?rev=1592216656&do=diff Version: 1.0 / 2020-03-04 Introduction This document describes the integration of Quartz Job Scheduler with VisionX workflow module. Basically, it explains how a workflow can be started by Quartz Job Scheduler. Requirements We need following tools and libraries: text/html 2024-11-18T10:15:38+00:00 http://doc.sibvisions.com/jvx/firstapp_step-by-step?rev=1731924938&do=diff The aim of this tutorial is to create an application with the Enterprise Application Framework. Moreover, a quick overview of the framework's possibilities will be given. The application's task is to display the data from a database table and make them editable. The application requests authentication with username and password. text/html 2020-07-08T17:36:26+00:00 http://doc.sibvisions.com/jvx/client/gui/exceptionhandling?rev=1594229786&do=diff Exception handling is very important for applications. It's necessary to visualize unexpected exceptions and to handle expected exceptions. Exception handling should be easy, centralized, and shouldn't blow up the application code. Isn't it boring to catch exceptions after unimportant code blocks? text/html 2022-03-31T05:43:10+00:00 http://doc.sibvisions.com/visionx/addon_auditlog?rev=1648705390&do=diff Version: 1.0 / 2022-03-31 Introduction This document describes the integration of Audit Logging for applications built with VisionX. The Audit Log Add-on offers historization for database tables. Therefore, all data changes are completely logged according to auditability including time, user and the data that has been changed. text/html 2025-06-20T10:06:15+00:00 http://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 2024-11-18T10:16:40+00:00 http://doc.sibvisions.com/jvx/code_snippets?rev=1731925000&do=diff We have a list of useful code snippets for you. Simply use them for your application. All snippets are free to use and licensed under Apache 2.0. Test DBStorages Without Lifecycle Objects Access a DBStorage without JVx Server, Lifecycle Object, Security, e.g., for unit tests. text/html 2020-06-15T10:34:54+00:00 http://doc.sibvisions.com/jvx/server/lco/custom_objects?rev=1592217294&do=diff Developers can integrate their own objects at the client as well as at the server. Here we will illustrate the use of objects that are integrated at the server and accessed by the client. Any Java object/library/API can be used at the server. Compatibility to server´s JVM is a basic requirement. In addition, stateless calls should be supported. Although it would generally not be a problem to use stateful objects, the scalability of the application would be affected.