Documentation

Trace:

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
jvx:server:lco:call_events [2020/06/26 12:26]
cduncan
jvx:server:lco:call_events [2020/07/08 17:51] (current)
cduncan articles
Line 4: Line 4:
 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). 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).
  
-Our JVx server implementation has some events which could be useful for your application. We've defined the interface javax.rad.server.ICallHandler with following methods:+Our JVx server implementation has some events which could be useful for your application. We've defined the interface javax.rad.server.ICallHandler with the following methods:
  
 <file java> <file java>
Line 38: Line 38:
 We have an additional method that invokes "​something"​ after all other operations. It's invokeFinally. We have an additional method that invokes "​something"​ after all other operations. It's invokeFinally.
  
-The call stack could look like following, for a single action call:+The call stack could look like the following, for a single action call:
  
 <file java> <file java>
This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information