[cfaussie] Re: cfinvoke webservice, xml response and 'cf' datatypes

2007-01-20 Thread Toby Tremayne
Hi Adam, what you need is an http proxy - basic principal is that you goto http://localhost:somerandomport and setup the http forwarder to listen on that port, but forward to your proper web address. Then you make your web requests as normal and you can watch the raw data being

[cfaussie] Re: cfinvoke webservice, xml response and 'cf' datatypes

2007-01-20 Thread Toby Tremayne
Having re-read the second part of your email I'd also recommend that you're probably best off creating an xml packet to return rather than passing a native array - that way your service becomes tech agnostic and you can consume it any way you like. Toby On 19/01/2007, at 16:00 , Adam

[cfaussie] Re: cfinvoke webservice, xml response and 'cf' datatypes

2007-01-20 Thread Toby Tremayne
And yes that should be principle not principal - more caffeine required. On 21/01/2007, at 12:52 , Toby Tremayne wrote: Hi Adam, what you need is an http proxy - basic principal is that you goto http://localhost:somerandomport and setup the http forwarder to listen on that port,

[cfaussie] Re: cfinvoke webservice, xml response and 'cf' datatypes

2007-01-20 Thread Shane Farmer
Hi Adam, A very handy tool you could try is SoupUI (www.soapui.org). We use it at work to run test suites against our Java web services. You point it at the WSDL, it can generate a default request where you fill in the blanks and hit send. What you get back is the actual SOAP envelope with all