The bug is also present into the NCA fork, it is not introduced during the
merge.
In order to give the soapSigner to the binding operation I am setting the
signer as a request parameter.
The problem is that the request parameters object does not have to be called
parameters, so if you provide
the parameters by the name params the resulting files will fail to build, due
to the hardcoded variable name:
operationXMLString = parameters.soapSigner ? [parameters.soapSigner
signRequest:operationXMLString] : operationXMLString;
Instead of 'parameters' the '%«part.name»' should be used.
ANYWAY we should see if there is a more claver way to set the soapSigner as
some request might even not have parameters at all.
Original issue reported on code.google.com by pmilosev on 29 Apr 2011 at 2:49
Original issue reported on code.google.com by
pmilosev
on 29 Apr 2011 at 2:49