Documentation

Trace:

Differences

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

Link to this comparison view

Next revision
Previous revision
Last revision Both sides next revision
jvx:server:lco:objects_rename [2018/02/01 22:57]
admin created
jvx:server:lco:objects_rename [2020/06/15 10:51]
cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation)
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 following call:
  
 <file java> <file java>
Line 56: Line 56:
 </​file>​ </​file>​
  
 +The Replacement will work for LCO names as well:
 +
 +<code java>
 +@Replacement(name = "​Public"​)
 +public class ExternalSession extends GenericBean ​
 +{
 +}
 +</​code>​
 +The LCO can be used with the original name or the Replacement. Both names will work.
This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information