- A Lightweight Java Middleware


OCSelot's way of being slim and accessible doesn't stop at documentation: the manual doesn't present every detail of the system, repeating what can just as easily be found in the overview, the examples, and the API. It is there to supplement the other docs by shedding light on aspects otherwise insufficiently covered.

To set the scene

let's briefly recapitulate the main players in an OCSelot application: There's the proxy, a local representative of a remote object, and the subject, the remote object serving the proxy, and there are the client and the server, which function as mediators between the other two.

The four components are linked unidirectionally, like this:

and in this order, from left to right, the manual will deal with them:

The proxy

Class proxiesCreating a class proxyConstructorsThe "rich" constructor The "pure" constructorFinal classesAbstract classes - Final methodsStatic methodsVirtual constructorsPrivate, default, and protected methodsSuperclass methodsInterface proxiesCreationGenerate interfacesClass vs. interface proxy: when to use which?Exceptions

The client

Association with the proxyCreating a clientRemote and local useThe client for remote communicationThe client for local communicationSecurityInvoking methods on the server

The server

Creating a serverRemote and local useThe server for remote communicationThe server for local communicationWhy use a server locally at all?Subject maintenanceSecurityInvoke server methods from remoteStop the server

The subject

Providing a subjectConditions for association with proxyRemovalSubject info
Last modified Jan 19, 2006