c# - How to remove *Response convention in service stack? -
i trying stand service using service stack. service needs meet soap 1.1 standards.
now operation object trying use called sendgetaccountresponse , created no response class async service. when run project operation / message not exist.
now if go , rename dto sendgetaccountr_esponse or sendgetaccountnotification operation appears , can call operation.
something tells me there kind of convention stops operations response @ end of displayed , used request object.
does know / how can turn conventions off?
dto naming conventions
naming convention: {request dto name} + response
example: request dto: deletecustomer --> response dto: deletecustomerresponse. if leave services are, rest endpoint wouldn't exist. need hook them on same url.
https://github.com/servicestack/servicestack/wiki/soap-support
the {requestdtoname}response
convention not removable.
it's used guess response of matching request dto should default. response type can overridden specifying in on service action signature, e.g:
public class myservice { public mycustomresult get(myrequest request} {} }
or specifying using ireturn<t>
marker on request dto, e.g:
public class myrequest : ireturn<mycustomresult> {}
Comments
Post a Comment