wcf client - Exposing meta data for a WCF 4.0 Rest Template Service -
probably missing basic. created wcf 4.0 rest service. works no problems when i'm hitting url browser , i'm getting want.
but want use service client mvc application (it used other non .net platforms why it's rest service in first place).
problem how service reference can start use in c# code? new minimal wcf .net 4 config approach , no interface service contract, don't know how specify mex endpoint. don't want mex endpoint in production, during development. love able specify services (around 10 in 1 application) have endpoints 1 tiny piece of config vs2010 .config transformations rips out when publish.
stop. rest service doesn't use metadata. metadata (mex endpoint) soap services because wsdl 1.1 (the version supported wcf) able describe soap service. wadl or wsdl 2.0 able describe rest service non of them supported wcf.
rest service consumed using webrequest
directly or building channelfactory
on top of shared contracts. both methods described here. other method use httpclient
rest starter kit (former api). problem starter kit has never reached rtm (it replaced wcf 4). instead of metadata endpoint wcf 4 rest service offers help page operation described. when using wcf 4 rest template page should turned on - add /help sufix address of service. here article building rest clients.
Comments
Post a Comment