anchor.diff:   * +500+ Lookup caused an exception
   
   ==== JNDI Result
  -Message Type:: +application/x-wf-jndi-jbmar-result+
   Response Body::
   Empty
   Response Codes::
  
positive.code: ==== Distributed Transaction Prepare
  
  Method:: +POST+
  URI:: +/txn/xa/prep/\{transactionId}+
  Additional Required Headers::
  +Accept: application/x-wf-txn-jbmar-result;version=1,application/x-wf-tx-exception;version=1+
  Additional Optional Headers::
  +Cookie: JSESSIONID=\{sessionAffinityKey}+
  Request Body::
  
negative.code: In most cases it is expected that session affinity will be used to make sure that invocations on the EJB target the correct server.
  
  ==== EJB Cancelled
  Response Body:: None
  Response Codes:: 
   * +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+.
  