Recently we've found out that Cache is getting stricter with regards to it's TCP licensing.

To be recognized as a SOAP message, it needs to have a SOAPACTION header and proper SOAP Envelopes.

After we had fixed that, license consumption went back to normal.

HTH

What version of Cache are you running ?

We had a similar issue with %Open, it was a bug:

there was a leak in $ZE variable, which was fixed by change DLP3616 - Object Storage - 
complete object initialization when %LoadData fails. The change now reset $ZE="" on start 
of %LoadData method.

2016.2.1 (Build 803_0_16949U)

Maybe it is related

Do ##class(%Dictionary.ClassDefinition).%DeleteId("Test.Class")
Set ClassDef=##class(%Dictionary.ClassDefinition).%New()
Set ClassDef.Name="Test.Class"
Set ClassDef.Super="%Persistent"
Set ClassDef.ProcedureBlock=1
Set MethDef=##class(%Dictionary.MethodDefinition).%New()
Set MethDef.Name="Name"
Set MethDef.ReturnType="%String"
; Uncomment for ClassMethod
; Set MethDef.ClassMethod=1
Set MethDef.FormalSpec="First:%Boolean,Second:%String=""Default"""
Do MethDef.Implementation.WriteLine($Char(9)_"If First Return 1")
Do MethDef.Implementation.WriteLine($Char(9)_"Return Second")
Set MethDef.parent=ClassDef
Do ClassDef.Methods.Insert(MethDef)
Do ClassDef.%Save()

Will you be able to use the Atelier REST services ?

%Api.Atelier.v1.GetDoc 

You can use XSLT to do this:

ClassMethod Run()
{
  Set XML=##class(%Dictionary.CompiledXData).%OpenId(..%ClassName(1)_"||XML").Data
  Set XSLT=##class(%Dictionary.CompiledXData).%OpenId(..%ClassName(1)_"||XSLT").Data
  Set sc = ##class(%XML.XSLT.Transformer).TransformStream(XML, XSLT, .Result,, .Params,)
  Do Result.OutputToDevice()
}

XData XML{
<?xml version="1.0" encoding="UTF-8" ?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/'>
  <SOAP-ENV:Header>
<SomeCustomHeader/> </SOAP-ENV:Header>
  <SOAP-ENV:Body><SomeCustomBody/></SOAP-ENV:Body>
</SOAP-ENV:Envelope>
}

XData XSLT {
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" omit-xml-declaration="yes"/>
  <xsl:strip-space elements="*"/>
  <xsl:template match="@*|node()">
   <xsl:copy>
    <xsl:apply-templates select="@*|node()"/>
   </xsl:copy>
  </xsl:template>
</xsl:stylesheet>
}
 

Couple of things I'm not sure of:

• what is pCompletionKey  used for? Can that be used as a unique reference for that invocation of SendRequestAsync?
• Is there such a thing as a sleep "Status" to use as Quit for OnRequest? Or do I need to loop until done? Will HANG in this case release the resources used by the process?
• if the target operation responds with an error is that handled by OnResponse or only OnError?

The CompletionKey is a 'tag' which you can attach to each async call. So you can distinguish them in the OnResponse by that tag.

Just 'Quit' the OnRequest, Ensemble will call the OnResponse when needed.

At the end (all Requests have responded or an optional time-out has occurred) the OnComplete will be called.

If the target operation has responded with a error-message in the Response message it will be in the OnResponse.

(I think) the OnError will be called if the target operation exits with a status code of not $$$OK

using a Command Pipe would be the way to achieve this:

Set Command="git status"
Set Pipe="|CPIPE|"
Open Pipe:(Command:"R"):0
If '$Test Return "Cannot open CommandPipe to "_Command
For  {
    Use Pipe Read Line If $ZEOF Quit
    Set Lines($Increment(Lines))=$ZStrip(Line,"<>W")
}
Close Pipe

It's probably more about semantics then syntax, but the correct way of using HTTP methods would be:

Create a resource: POST

Replace a resource completely: PUT

Update one or more properties: PATCH