2.5.4.2.2 Activate a Client-Activated Object and Invoke a Method

Goal: A client application activates a Client-Activated Object (CAO) and invokes a method on the activated object.

Context of Use: The client application activates a Client-Activated Object on a remoting server and invokes a method on that object.

Primary Actor: The primary actor is the client application.

Supporting Actor: The supporting actor is the remoting server (the server application on which the remote object resides). The remoting server also hosts the RemoteActivationService service, which activates the Client-Activated Objects.

Preconditions:

  • The client system and remote system have negotiated the encoding to be used.

  • The client application recognizes the Server Object URI of the RemoteActivationService and is configured with enough information about the Server Type to construct the activation message.

Main Success Scenario:

  1. The client application calls the Activate method of the RemoteActivationService to activate a Client-Activated Object of a particular Server Type. The Activate method returns the Server Object Reference of the activated object.

  2. The client application invokes a method on the returned Server Object.

  3. The remoting server executes the method.

Extensions

  • If the client application is required to access a method or methods of the activated Server Object, it can prevent the object from being unmarshaled by using lifetime management after step 3, as described in the use cases in sections 2.5.4.2.3 and 2.5.4.2.4.

Minimal Guarantees: The client application cannot activate the Client-Activated Object.

Success Guarantee: The client application activates a Client-Activated Object and invokes a method on the activated object.