Documentation

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

jvx:server:lco:custom_objects [2018/02/01 22:27]
admin created
jvx:server:lco:custom_objects [2020/06/15 10:34] (current)
cduncan
Line 1: Line 1:
-~~Title: Use your own objects ​at the server~~+~~Title: Use Your Own Objects ​at the Server~~
  
 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. 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.
Line 5: Line 5:
 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. 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.
  
-All server objects that are used by JVx in lifecycle ​objects support stateless calls. ​+All server objects that are used by JVx in life cycle objects support stateless calls. ​
  
 == Example == == Example ==
Line 57: Line 57:
 </​file>​ </​file>​
  
-The object is used in the Lifecycle ​object of our MasterSession:​+The object is used in the life cycle object of our MasterSession:​
  
 <file java Session.java>​ <file java Session.java>​
This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information