docs/3.0/remote-object-persistence-coding-server.html

Title: Remote Object Persistence Coding Server

	<H2><A name="RemoteObjectPersistenceCodingServer-RemoteObjectPersistenceCodingServer"></A>Remote Object Persistence Coding Server</H2>

<P>In the simplest case, there is no custom code on the server. The server would only contain Cayenne mapping files, persistent classes and web.xml descriptor <A href="remote-object-persistence-cws-deployment.html" title="Remote Object Persistence CWS Deployment">specifying deployment parameters</A> of the service. Customization is done in one of the following ways:</P>

<UL>
	<LI>Via subclassing <TT>org.apache.cayenne.remote.hessian.service.HessianServlet</TT></LI>
	<LI>Adding business logic via <A href="remote-object-persistence-lifecycle-callbacks.html" title="Remote Object Persistence Lifecycle Callbacks">lifecycle callbacks</A>.</LI>
</UL>


<H3><A name="RemoteObjectPersistenceCodingServer-Sections"></A>Sections</H3>

<OL>
	<LI><A href="remote-object-persistence-lifecycle-callbacks.html" title="Remote Object Persistence Lifecycle Callbacks">Remote Object Persistence Lifecycle Callbacks</A></LI>
</OL>