anchor.diff:  Method::: +POST+
   URI:: +/ejb/\{applicationName}/\{moduleName}/\{distinctName}/\{beanName}/\{sfsbSessionId}/\{viewClass}/\{methodName}/\{paramType1}/\{paramType1}/...+
   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++
  ++Accept: application/x-wf-ejb-response;version=1,application/x-wf-ejb-exception;version=1+
   Additional Optional Headers::
   +Cookie: JSESSIONID=\{sessionAffinityKey}+
   X-wf-invocation-id: {invocationId}
  
positive.code:  * +202+ Returned for a successful invocation
   * +404+ Returned if the invocation was not found (i.e. it has already completed)
  
  == JNDI Protocol
  
  The JNDI protocol provides similar functionality to the existing remote JNDI implementation, but over HTTP. All JNDI URL’s are prefixed with +/jndi+.
  
negative.code: Message Type:: +application/x-wf-ejb-affinity+
  Method::: ++GET++
  URI:: +/ejb/\{applicationName}/\{moduleName}/\{distinctName}+
  Additional Required Headers::
  +Accept: application/x-wf-ejb-affinity-result;version=1+
  Request Body::
  The request body is empty.
  
  