Trace: • Using Calculated Values • Setting Default Values • Supported Application.xml Properties • Application and Server Zones • Push support • Replace JVx' standard Application With ProjX • Application Events • Custom Themes
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
jvx:server:lco:actions_in_objects [2020/06/15 10:53] cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
jvx:server:lco:actions_in_objects [2020/07/08 17:52] (current) cduncan articles |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ~~Title: Actions in Server Objects~~ | ~~Title: Actions in Server Objects~~ | ||
| - | Every [[jvx:server:lco:actions|server-side action]] should be defined in a [[jvx:server:lco:lifecycle|life-cycle object]] (= LCO). Sometimes it's better to group functionality in helper objects. | + | Every [[jvx:server:lco:actions|server-side action]] should be defined in a [[jvx:server:lco:lifecycle|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: | It's very easy to encapsulate functionality in objects. Just create an object and add public methods: | ||
| Line 32: | Line 32: | ||
| Our Car class has two methods: **getType** and **getSpeed**! | Our Car class has two methods: **getType** and **getSpeed**! | ||
| - | If you're using the Car class in your life cycle object, like following: | + | If you're using the Car class in your life cycle object, like the following: |
| <file java> | <file java> | ||