anchor.diff:  The request body is empty.
   
   This message cancels an async request.
  -
  -==== EJB Invocation Result
  -
  -Message Type:: +application/x-wf-ejb-invocation-result+
  -Method::: +POST+
  -URI:: +/ejb/\{applicationName}/\{moduleName}/\{distinctName}/\{invocation-id}+
  -Additional Required Headers::
  -+Accept: application/x-wf-ejb-response;version=1,application/x-wf-ejb-exception;version=1+
  -+Cookie: JSESSIONID=\{sessionAffinityKey}+
  -Request Body::
  -The request body is empty.
  -
  -This method is used to retrieve the body of an async request. Note that this should be sent immediately after the async method invocation was submitted, as the server will not keep async results around forever (as this would constitute a memory leak). By default a server will keep a result for 60 seconds after the async invocation has completed.
   
   === Response Messages
   
  
positive.code: Additional Required Headers::
  +Accept: application/x-wf-ejb-response;version=1,application/x-wf-ejb-exception;version=1, application/x-wf-ejb-invocation-id;version=1++
  Additional Optional Headers::
  +X-wf-ejb-allow-cancellation: true+
  +Cookie: JSESSIONID=\{sessionAffinityKey}+
  Request Body::
  The method body consists of n parameter values, serialized using JBoss Marshalling, followed by a serialized attachments map of the form +Map<String, Object>+.
  Notes::
  This message sends a request to the server. If the request completes successfully (or is submitted successfully in the case of a void returning async EJB methods) the server will respond with an +x-wf-ejb-response response+. If an error occurred the server will respond with an +x-wf-ejb-exception+ response.
  
  If the +X-wf-ejb-allow-cancellation+ header is true and the target method is an asynchronous method that returns a Future then a +x-wf-ejb-invocation-id+ message will be returned. This method contains the invocation ID of the async method, and the server may retrieve it or cancel it using this async id. In this case a session ID must be used to ensure cancel and retrieve messages are sent to the correct server.
  
  ==== EJB Session Open
  
  
negative.code: 
  The EJB protocol is mapped to the +/ejb+ context inside the service context path. When specifying the URI for a request all fields are required, if they are null or empty they should be replaced with a ‘-’ character.
  
  This protocol has been designed to work with the existing EJB client API.
  
  Cancellation support is provided through the use of a client side invocation id and a session cookie. The session cookie makes sure a cancellation goes to the correct server and ensures there are no conflicts, while the invocation id is used to identity the invocation to cancel.
  
  === Request Messages
  
  