Trace: • Implementing the Security Manager
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
jvx:server:lco:objects [2020/06/15 10:34] cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
jvx:server:lco:objects [2020/06/26 12:16] (current) cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
||
|---|---|---|---|
| Line 125: | Line 125: | ||
| We derive from Application to receive full access to the methods and objects of the super class. The derivation of GenericBean ensures the availability of objects. | We derive from Application to receive full access to the methods and objects of the super class. The derivation of GenericBean ensures the availability of objects. | ||
| - | Each SubConnection (Client), and therefore each workscreen, receives its own life cycle object: | + | Each SubConnection (Client), and, therefore, each workscreen, receives its own life cycle object: |
| <file java Educations.java> | <file java Educations.java> | ||
| Line 177: | Line 177: | ||
| == GenericBean == | == GenericBean == | ||
| - | The previous example shows that due to the derivations all methods are inherited, but that each instance would usually manage its own objects. We would therefore expect that each instance of Educations creates a new database connection through the call of getDBAccess! | + | The previous example shows that, due to the derivations, all methods are inherited but each instance would usually manage its own objects. We would, therefore, expect that each instance of Educations creates a new database connection through the call of getDBAccess! |
| This is the difference between POJO and GenericBean. | This is the difference between POJO and GenericBean. | ||
| - | Because of the derivation of GenericBean, the server makes sure that all instances are reused. In our example the session Instance is set as the parent at the instantiation of Educations and the Application instance is set as parent of the Session instance. Because of this definition, the method getDBAccess always returns the same database connection. | + | Because of the derivation of GenericBean, the server makes sure that all instances are reused. In our example, the session Instance is set as the parent at the instantiation of Educations and the Application instance is set as parent of the Session instance. Because of this definition, the method getDBAccess always returns the same database connection. |
| Another feature of GenericBean is the access to managed objects by their names: | Another feature of GenericBean is the access to managed objects by their names: | ||
| Line 189: | Line 189: | ||
| </file> | </file> | ||
| - | We can therefore call either getEducations() or get("educations") and in both cases the same instance is delivered. For this process to work the desired object has to be instantiated and put to the cache: | + | We can, therefore, call either getEducations() or get("educations") and, in both cases, the same instance is delivered. For this process to work, the desired object has to be instantiated and put to the cache: |
| <file java> | <file java> | ||