https://doc.sibvisions.com/ 2026-04-21T10:37:43+00:00 https://doc.sibvisions.com/ https://doc.sibvisions.com/lib/tpl/material/images/favicon.ico text/html 2023-08-08T09:37:19+00:00 https://doc.sibvisions.com/jvx/communication/alive?rev=1691487439&do=diff If you're using a desktop client for your application and a communication protocol like http, you have to know about the integrated alive mechanism of JVx. What's the alive mechanism? The alive mechanism allows detection of invalid connections. This is important for automatic session handling and memory management. If you start your application, every application has one or more connections to the server-side. If you close your application, all used resources will be released. If you're not us… text/html 2020-06-08T15:48:33+00:00 https://doc.sibvisions.com/jvx/communication/async_callback?rev=1591631313&do=diff Any function at the client´s business logic can be addressed using Server Actions. These are usually actions that do not take up a lot of time, such as, input validation. For this reason, communication between client and server is synchronized, i.e., the client makes a request to the server and waits for a response. During the wait time, the mouse cursor in the application is displayed as an hourglass, and the user can perform no further actions. text/html 2020-07-08T17:46:47+00:00 https://doc.sibvisions.com/jvx/communication/calling_server_action?rev=1594230407&do=diff A server action is a method/function that is defined in a life cycle object at the server. Execution is initiated either by the client or directly at the server. In short, it is any method at the business level of the application. Server actions are used for functions that are not/should not be executed at the client, including business logic such as mail transmission, interface requests, calculations, etc. text/html 2024-11-18T10:35:01+00:00 https://doc.sibvisions.com/jvx/communication/client_server_properties?rev=1731926101&do=diff Client/Server properties are used to transmit information about the client to the server and vice versa. The transmission of properties is integrated in the communication protocol and does not require special handling. During the transmission, only new, changed, or deleted properties are considered. In addition, only strings, numbers, and boolean values are transmitted but no serializable POJOs. This guarantees that the same properties are available at the server and at the client and that they… text/html 2020-06-08T15:54:08+00:00 https://doc.sibvisions.com/jvx/communication/connection_client_properties?rev=1591631648&do=diff The use of Client/Server Properties has already been explained. However, in some cases it may be beneficial if default values can be defined during the creation of a master connection. This makes sense when, for example, client tasks are configured by the server. A concrete example would be the distinction between productive and development mode or, in addition, the default log level. text/html 2020-06-08T15:57:52+00:00 https://doc.sibvisions.com/jvx/communication/connections?rev=1591631872&do=diff JVx is generally used to develop multi-tier applications with an emphasis on databases. To facilitate data exchange between client and enterprise tier, a transport layer is required. This transport layer not only has a very abstract definition in JVx, but an implementation based on http(s) already exists. text/html 2020-07-08T17:48:02+00:00 https://doc.sibvisions.com/jvx/communication/push_publish?rev=1594230482&do=diff A standard JVx application requests data from the server side via Connection. This concept doesn't support sending messages from the server to the client side. In JVx, we have a keep alive mechanism and this usually checks every 30 seconds if the connection to the server-side is still valid. This alive check can be used to send properties to the client using text/html 2022-11-29T12:17:04+00:00 https://doc.sibvisions.com/jvx/communication/push_support?rev=1669724224&do=diff Sometimes it's important to notify all client about an event or about changed records. This is known as “push”. You push a message to all clients. In web environments a websocket is used for push notification. In JVx we have a push mechanism which is technology independent and it works different in different UI technologies. text/html 2022-11-22T10:06:26+00:00 https://doc.sibvisions.com/jvx/communication/rest_customservice?rev=1669111586&do=diff JVx already has REST services for action calls, data access an administration. Sometimes it's necessary to offer custom REST services for an application. Sure, you could create a simple action in your application and an action can be called with standard REST services, but this requires application authentication. If you have a different use-case for your REST service it's also possible to create your own REST service without using different libraries. text/html 2020-06-08T16:02:01+00:00 https://doc.sibvisions.com/jvx/communication/rest_exceptionhandling?rev=1591632121&do=diff Our standard REST services come with standard exception handling. This means that all server-side exceptions will send the http status code 400 (Bad Request) to the client. The implementation already checks some exception types and returns custom http status codes: text/html 2020-06-08T15:58:58+00:00 https://doc.sibvisions.com/jvx/communication/serialization?rev=1591631938&do=diff As already mentioned under Connections, objects are serialized during the transmission between client and enterprise tier. However, instead of the standard Java serialization, special technology-independent serialization mechanisms are used. The so-called serializers have to fulfill the ISerializer interface. text/html 2020-07-08T17:47:19+00:00 https://doc.sibvisions.com/jvx/communication/timeouts?rev=1594230439&do=diff For security reasons, the validity of client/server connections or sessions is limited. After inactivity (no user interaction) of a predefined time, the connection or session is invalidated, and the client has to reconnect if necessary. If no timeouts are defined for JVx, the connections/sessions are not invalidated.