08-24-04 11:58 PM
I belive I have seen a post indicating that you could add those properties
to the message context and it would work, but this might not be a supported
solution. I think the only supported solution is to use an orchestration
with a web reference.
Matt
"abdulsait" <abdulsait@discussions.microsoft.com> wrote in message
news:2826F6FF-8E20-4318-8917-BB61B627F0A9@microsoft.com...
> I am having some trouble calling webservices from an orchestration.
>
> Now I know how to consume webservice in an orchestration by using web
> references and web messages. But, I have a send port with Specify Later in
my
> orchestration that goes to a Role Link. Some partners in the role will
have
> FILE and a few may have SOAP adapters. I can send to FILE with no problem,
> but SOAP fails with "AssemblyName not valid".
>
> I read some place that it is mandatory to use WebPorts to call web
services
> from an orchestration. Is this true?
>
> I found that this is necessary because XLANG adds a couple extra
properties,
> AssemblyName and WebMethod, at runtime.
>
> Is there a way to create a custom pipeline to add these properties and
their
> values? Any have any thoughts on accomplishing this? It seems odd that I
> cannot call web services without using webports.
>
> Thanks a bunch
[ Post a follow-up to this message ]
|