How is Session State maintained over Web Services?
Session Management in a stateful Web Service (using HTTP for the SOAP transport binding) is typically achieved using either SOAP headers or HTTP cookies. The Oracle Content DB Web Services use the HTTP cookies method, and thus, a client using the Oracle Content DB Web Services must support HTTP cookies. Session authentication/establishment for the Oracle Content DB Web Services is performed by either the RemoteLoginManager, or through S2S (ServiceToServiceLoginManager or S2S servlet). When a client successfully authenticates using the appropriate login operation, a ‘set-cookie’ directive is returned with the response (the cookie name is JSESSIONID – the standard OC4J Session Cookie). Any subsequent Web Service requests by the client must include this cookie. Failure to include this cookie will result in a SOAP Fault being returned, containing an FdkException with the error code “ORACLE.FDK.AccessDenied.” The Oracle Content DB Web Services do not currently use SOAP Headers because not a
