2.5.4.2.1 Invoke a Method on a Server-Activated Object

  • Article

Goal: A client application performs an operation on a Server-Activated Object (SAO) on a remoting server.

Context of Use: A client application invokes a method on a Server-Activated Object (SAO) on a remoting server.

Primary Actor: The primary actor is the client application.

Supporting Actor: The supporting actor for this use case is the remoting server (the server application on which the Server-Activated Object resides).

Preconditions:

  • The client application and remoting server have negotiated the encoding to be used.

  • The client application recognizes the Server Object URI.

Trigger: The client application invokes a method on the Server-Activated Object on the remoting server.

Main Success Scenario:

  1. The client application connects to the remoting server by using the Server Object URI.

  2. The client application invokes a method on the remoting server.

  3. The remoting server executes the method.

Variations:

  • If the method invocation is two-way, the client application waits for response from the remoting server.

  • The remoting server sends back a response that can contain a return value and output arguments.

Minimal Guarantees: The method invocation fails.

Success Guarantee: The client application successfully invokes the remote object method on the remoting server.