Error calling a BizTalk WCF Service with WCFTestClient

Question

I have published schema as a wcf service (WCF-CustomIsolated). I can browse to the wsdl from the local server and from my PC. I can call the service from a console application running on my pc, but when I attempt to add the service from the wcf test client,
I get the message:
Warning: No code was generated.If you were trying to generate a client, this could be because the metadata documents did not contain any valid contracts or servicesor because all contracts/services were discovered to exist in /reference assemblies. Verify
that you passed all the metadata documents to the tool.Warning: If you would like to generate data contracts from schemas make sure to use the /dataContractOnly option.
Was there a configuration step I missed?

Answer 1

Hi Jeremy, probably not a configuration issue. I remember reading somewhere the inability of the client to consume the service in such scenarios. I am assuming metadata publishing is enabled. Will try and search the article I read.q
Praveen Behara
MCST : BizTalk Server 2006 R2, 2010
Yup, metadata publishing is enabled. I can browse to the wsdl.   This is a pure message solution, so I'm using a custom disassembler pipeline component to receive the request and generate a response.  When the wcf test client tries to add
the service, the execute method of my pipeline fires, which seems odd to me, because we're not actually making a request at this point,  only trying to get the meta data I would think.
When adding the service, wcf test client's request has an action of
http://schemas.xmlsoap.org/ws/2004/09/transfer/Get with an empty body like this:
POST http://myserver/MyService/test.svc HTTP/1.1
Content-Type: application/soap+xml; charset=utf-8
Host: myserver
Content-Length: 512
Expect: 100-continue
Accept-Encoding: gzip, deflate
Connection: Keep-Alive
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
<a:Action s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2004/09/transfer/Get</a:Action>
<a:MessageID>urn:uuid:8bd3f321-0a94-44f1-9eb4-5575068cc408</a:MessageID>
<a:ReplyTo>
<a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
</a:ReplyTo>
<a:To s:mustUnderstand="1">http://myserver/MyService/test.svc</a:To>
</s:Header>
<s:Body/>
</s:Envelope>
I'm assuming somehow the BizTalk receive location would have to be configured to behave differently under this circumstance instead of passing the message to the pipeline component...