What is a ServerHandler?
A ServerHandler has the task to delegate client requests to external application logic for subsequent
processing. It is the interface between EJOE and applications, which publish remote services over EJOE.
The choosen ServerHandler must be indicated when creating an instance of EJServer.
There are three kinds of ServerHandler known by EJOE:
-
RemotingHandler:
They offer the possibility to process client requests by reflection.
-
de.netseeker.ejoe.handler.DefaultRemotingHandler
:
Default RemotingHandler, corresponds to the use of ordinary reflection with some gains
in speed by caching of classes and methods.
-
de.netseeker.ejoe.handler.AssistedRemotingHandler
:
Extended RemotingHandler, which works on the basis of generated and cached
proxy-classes.
By the generation of the proxy-classes the first call of a method lasts longer than
using the DefaultRemotingHandler, all following calls will be however faster.
The generation of the proxy-classes relies on
javassist
The AssistedRemotingHandler does not work with JDK/JRE < 1.5.0!
-
Custom ServerHandler:
Customized ServerHandler implementing
de.netseeker.ejoe.handler.ServerHandler
.
-
de.netseeker.ejoe.handler.ClassHandler
:
A special, internally used ServerHandler, which is used by EJOEs RemoteClassloader.
During the integration of EJOE into the own enviroment there is one critical question:
To use a ServerHandler of the family of
RemotingHandlers
or to implement a
custom ServerHandler
?
