Jeremy,
We had a few problems a while back to do with consuming a .net web service.
The problem with ColdFusion MX 6.1 was it could not pass the
credentials through the soap headers. I didn't want to have to build
the headers by hand so we were able to get the web service changed to
accept them as arguments. I think there was an update that let you add
to the soad header but I couldn't get it to work properly.
The way the Seek web service does things is so you only have to
authenticate once and just pass your token back each time. It isn't
really to do with the language it was done in, just that every method
call needs to be authenticated. Without seeing the other methods
available after authenticating (probably only on non-test web service)
I couldn't say if using the returned token is a .net or CF issue.
One thing I found anouying was the web service we were using was
returning a .net dataset. We ended up writing a transform function that
could go through a dataset and convert it to a CF query. The function
still needs work unfortunately. The CF server doesn't seem to handle
the process if there are 1000+ records returned. The XML was getting
too big.
Shane
---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
- [cfaussie] Re: Consuming a .NET webservice Andrew Muller
- [cfaussie] Re: Consuming a .NET webservice Aaron DC
- [cfaussie] Re: Consuming a .NET webservice Jeremy
- [cfaussie] Re: Consuming a .NET webservice Shane Farmer
