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
Next revision
Previous revision
jvx:server:lco:objects_rename [2019/03/08 10:27]
admin
jvx:server:lco:objects_rename [2020/07/08 17:52] (current)
cduncan articles
Line 1: Line 1:
 ~~NOTRANS~~ ~~NOTRANS~~
-~~Title: Rename ​server-side objects ​and action names~~+~~Title: Rename ​Server-Side Objects ​and Action Names~~
  
 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. 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.
  
-The application frame has some pre-requirements, e.g. the menu will be created after authentication. The application frame does following call:+The application frame has some prerequisites, e.g.the menu will be created after authentication. The application frame does the following call:
  
 <file java> <file java>
Line 17: Line 17:
 </​file>​ </​file>​
  
-This means that you have following in your Session LCO:+This means that you have the following in your Session LCO:
  
 <file java> <file java>
Line 36: Line 36:
 </​file>​ </​file>​
  
-The application frame won't work if the method name isn't getWorkScreenAccess. If you have a specific naming schema and won't use the same method name, you could do following:+The application frame won't work if the method name isn't getWorkScreenAccess. If you have a specific naming schema and won't use the same method name, you could do the following:
  
 <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