Trace:
Differences
This shows you the differences between two versions of the page.
|
jvx:common:util:servercontext [2018/02/02 09:42] admin created |
jvx:common:util:servercontext [2020/06/15 14:38] (current) cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ~~Title: Using ServerContext~~ | ~~Title: Using ServerContext~~ | ||
| - | The ServerContext is a special Context for server-side objects. If you create your own plugins or extend the server, session manager, object provider or a server class, it can useful to have access to the affected session. The ServerContext will be created before the [[jvx:server:lco:sessioncontext|SessionContext]] and it exists during the whole server-side execution of a call. | + | The ServerContext is a special context for server-side objects. If you create your own plugins or extend the server, session manager, object provider or a server class, it can useful to have access to the affected session. The ServerContext will be created before the [[jvx:server:lco:sessioncontext|SessionContext]] and it exists during the whole server-side execution of a call. |
| The ServerContext has few methods: | The ServerContext has few methods: | ||
| Line 16: | Line 16: | ||
| You shouldn't call destroy because it makes the context unusable. | You shouldn't call destroy because it makes the context unusable. | ||
| - | The system identifier is a unique identifier for the server environment. It depends on the deployment mode, e.g. a desktop application will return the working directory as system identifier. If you deploy the server on an application server, the context URL will be used as system identifier. | + | The system identifier is a unique identifier for the server environment. It depends on the deployment mode, e.g., a desktop application will return the working directory as system identifier. If you deploy the server on an application server, the context URL will be used as system identifier. |