I ran into the same sort of problem when hooking up InfoPath 2007 to
WCF web services. Had to use a Soap 1.1 basicHttpBinding to get it
connected.
I'm no expert in InfoPath, but as far as I can tell it doesn't support
WSE v.anything. You'd have to strip all your wse bits out and use plain
old vanilla Soap.
Of course, you could write you own code to do the comms to the web
service, but thats just plain nasty to have to drop down to that level
imho.
Mark
PS. Infopath isn't going to care about the extension of the file that
it is calling, it's the underlying communication protocol that matters.
souhaibb.javed[ at ]gmail.com wrote:
[Quoted Text] > Hi,
>
> I'm using BizTalk 2006 having WSE 3.0 (twoConnect) Adapter for exposing
>
> Orchestration as a WebService.
>
>
> I'm trying to create an InfoPath form to send some values to the
> Orchestration Web Service. However as WSE3.0 is generating .ASHX file
> instead
> of .ASMX file. InfoPath (it seems like it) is only supporting .ASMX
> files
> only if we are designing the form based on Web Services. "Invalid URL"
> kind
> of related messages pops up.
>
>
> Can anyone advice on this matter, if there is a patch available
> somewhere
> for InfoPath to support WSE3.0 generated web services having .ASHX
> files.
>
>
> Thanks.
>
>
> With Regards
|