I have used SoupUI (http://www.soapui.org/), which is in on the CF411
list.  You give your WSDL address and it allows you to make requests. As
Charlie mentioned, this will confirm if the problem is with the web
service itself. The other reason this was a big deal for me is that it
shows you what the soap request should look like. Whenever I have had
problems with a web service, my soap request was wrong.

Hope it helps,

Ruben

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Charlie
Arehart
Sent: Wednesday, May 27, 2009 12:46 PM
To: [email protected]
Subject: RE: [ACFUG Discuss] Web Service Problem

So are you saying that in fact things are ok, if you don't use that
tool?

And as far as tools to analyze web services, there are those built into
Dreamweaver and Eclipse (with the Adobe CF Extensions). Have you tried
either of those? Each of these can explore any web service URL you
provide, and show you its methods, arguments, etc. There are also free
web-based tools that can explore any web service. These will help you
confirm if a problem is in your client or tool, or if in fact the web
service can be consumed just fine.

See the section of my CF411 site:

Web Services Browsing/Testing Tools
http://www.cf411.com/#websvc

which includes specific pointers for where to find the web service
testing features in DW and Eclipse. Those tools can also build CFINVOKE
or createobject calls to invoke such web services, though I realize in
your case, Gerry, you're not likely interested in that feature. Still,
for just confirming that a web service can be browsed at all, they're
useful for you.

/charlie


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Gerry
Gurevich
Sent: Wednesday, May 27, 2009 12:24 PM
To: [email protected]
Subject: Re: [ACFUG Discuss] Web Service Problem

A little clarification of my initial description:

I had indicated that the SOAP envelope was formed wrong...but it turns
out that this was the tool that I was using to generate the SOAP request
that was malforming the outbound request.  Presumably it is because of
something in the WSDL.  But I'm investigating another tool.


-------------------------------------------------------------
To unsubscribe from this list, manage your profile @
http://www.acfug.org?fa=login.edituserform

For more info, see http://www.acfug.org/mailinglists Archive @
http://www.mail-archive.com/discussion%40acfug.org/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------






-------------------------------------------------------------
To unsubscribe from this list, manage your profile @
http://www.acfug.org?fa=login.edituserform

For more info, see http://www.acfug.org/mailinglists Archive @
http://www.mail-archive.com/discussion%40acfug.org/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------





-------------------------------------------------------------
To unsubscribe from this list, manage your profile @
http://www.acfug.org?fa=login.edituserform

For more info, see http://www.acfug.org/mailinglists
Archive @ http://www.mail-archive.com/discussion%40acfug.org/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------



Reply via email to