✎ Using ServerContext | Documentation

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

~~NOTRANS~~
~~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 has few methods:

<file java>
protected abstract void destroy();
public abstract ISession getSession();
public abstract String getSystemIdentifier();
public abstract String getServerIdentifier();
public abstract ICallHandler getCallHandler();
</file>

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.