https://doc.sibvisions.com/ 2026-04-26T03:51:31+00:00 https://doc.sibvisions.com/ https://doc.sibvisions.com/lib/tpl/material/images/favicon.ico text/html 2020-06-26T12:47:35+00:00 https://doc.sibvisions.com/jvx/server/lco/accessible_notaccessible?rev=1593175655&do=diff The @Accessible and @NotAccessible annotations are described in this article. But in some cases it's not enough to allow or deny the general access to a method or storage. Sometimes, you want to configure the access for a specific environment, e.g., it shouldn't be possible to use an action in REST environment, but it should be possible to use the same method in all other environments. text/html 2020-07-08T17:51:32+00:00 https://doc.sibvisions.com/jvx/server/lco/actions?rev=1594230692&do=diff A server-side action is a simple Java method defined in a life cycle object (LCO). A standard JVx application has an application global LCO, a session LCO, and a LCO for every screen. An action can be defined in every LCO, but it makes sense to define the actions in the right “context text/html 2020-07-08T17:52:18+00:00 https://doc.sibvisions.com/jvx/server/lco/actions_in_objects?rev=1594230738&do=diff Every server-side action should be defined in a life cycle object (LCO). Sometimes, it's better to group functionality in helper objects. It's very easy to encapsulate functionality in objects. Just create an object and add public methods: public class Car { private String type; private int speed; public Car(String type, int speed) { this.type = type; this.speed = speed; } public String getType() { return sType; } public int getSp… text/html 2020-07-08T17:50:46+00:00 https://doc.sibvisions.com/jvx/server/lco/appconfig?rev=1594230646&do=diff Sometimes you'll need additional settings for your application. Such a setting might be an additional database login or path to xsd files or mail server configuration (if not available in your database). There's no need to implement your own settings mechanism because JVx offers that out of the box. Simply add your settings to the text/html 2024-11-18T10:33:39+00:00 https://doc.sibvisions.com/jvx/server/lco/call_events?rev=1731926019&do=diff If you call a server-side function or an action, usually you don't need more than the result on the client (UI). If you have complex business logic on server side, or if you call multiple server-side functions or actions in one single call, it would be useful to have server-side events with call information. Sometimes it's really helpful to do something after a single or all calls, e.g., cleanup of states, commit, or rollback connection(s) (if you don't use autocommit). text/html 2020-06-15T10:34:54+00:00 https://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. text/html 2020-06-26T12:53:01+00:00 https://doc.sibvisions.com/jvx/server/lco/inject_objects?rev=1593175981&do=diff Occasionally, it's important to add external objects in your running application without additional coding. We have an injection mechanism which is pretty simple. It's possible to inject custom Java objects or objects which implements the interface text/html 2020-06-15T10:31:31+00:00 https://doc.sibvisions.com/jvx/server/lco/lifecycle?rev=1592217091&do=diff A life cycle object is basically a container for any objects and methods/actions that are administered on the server side. Life cycle objects are used to provide business logic to the client. Each life cycle object has a predefined life cycle. When the cycle ends, the object is discarded along with all other objects it administers. This process optimizes the application server´s memory usage. text/html 2020-06-26T12:16:42+00:00 https://doc.sibvisions.com/jvx/server/lco/objects?rev=1593173802&do=diff JVx's Life Cycle Objects are not only containers for objects and methods, they also allow the reuse of functionality through inheritance. Any POJO can potentially be used as a lifecycle object, although this would mean that we forego the advantage of reuse. We recommend a special use and a predefined class hierarchy to exploit all the advantages without restrictions! text/html 2020-07-08T17:52:01+00:00 https://doc.sibvisions.com/jvx/server/lco/objects_rename?rev=1594230721&do=diff If you call an action or request a server-side object, you should know the name of the action or the object. Usually this isn't a big problem because it's your application and you know everything about it. But it's different if you use pre-defined application frames like ProjX. text/html 2020-06-26T12:49:15+00:00 https://doc.sibvisions.com/jvx/server/lco/session_isolation?rev=1593175755&do=diff It is usually good enough if your client creates one single connection to the server. This connection could be created via application login. A login dialog is the right place for creating a connection. But sometimes you need a connection to the server independent of the authenticated user, maybe to retrieve properties or text/html 2020-06-15T10:35:53+00:00 https://doc.sibvisions.com/jvx/server/lco/sessioncontext?rev=1592217353&do=diff SessionContext is an object available only at the server that enables access to session information as well as certain objects related to a session during the handling of a client request. Example We have developed an application that reviews all existing messages in an email account and displays the number of messages. The request is initiated at the client by clicking a button.