Hi Robert,
I too am having SOAP/XML issues. This is no easy task, but with that said, I
think Scott Cadillac can probably shed some light onto the situation. He's
pretty much a guru along with Robert Garcia...
Good luck! :)
On 8/31/06 10:37 AM, "Roland Dumas" <[EMAIL PROTECTED]> wrote:
> My X
Hi Roland,
> they say
> it's not so
> simple. More moving parts because it's SOAP.
There is a bit to SOAP, but it still boils down to just HTTP and posting and
read text formatted as XML.
> I think I slept through
> the discussion of SOAP in San Diego.
T'sk, T'sk. I'll have to put a litt
Procedurally, is SOAP a 1 hit process or a 2?
Does the client send a properly packaged payload and wait for a
response? or does it ask for something and use that to create the query?
I don't really want to know all about it, just enough to push the
query and interpret the response in this on
Thank you for the compliments Kaustav,
> I think Scott Cadillac can probably shed some light onto the
> situation. He's pretty much a guru along with Robert Garcia...
Actually, I consider myself more of a gugu than a guru, or at least that's what
my ex-wife used to tell me all the time.
:-/
_
Hi Roland,
> Procedurally, is SOAP a 1 hit process or a 2?
> Does the client send a properly packaged payload and wait for a
> response? or does it ask for something and use that to create
> the query?
>
It can be 1 or 2, you decide. The 2 hit process involves retrieving the WSDL
prior to yo
It all depends, the best way, is to use a 2 call method, where you
query the WSDL, and then, build the soap request from its contents,
and many times this is required. This is VERY easy, when you work in
a dev environment, that has a class, that will parse the WSDL, and do
most of the work
hmm, the notion that the WSDL might be changing and even giving
changing URLs for submission does nix the idea of a static 1-step
approach.
and you say that witango doesn't have a good way to parse up the WSDL
to use to formulate a request? Does not bode well.
On Aug 31, 2006, at 12:44
Hi Roland,
Technically speaking, what Robert said is true, but speaking from experience, I
find this rarely to be the case.
If the SOAP service you're calling is for a commercial vendor, then I would
find it highly unlikely that the WSDL will change very often - and when it
does, it's more lik
I agree, most of the time its static, I do have one method, where the
url, regularly changes. My main point was, this is not one of
witango's strengths. And my RB example, shows a complete, 3 lines of
code approach.
So I am sure you will find what works best for you, but I have been
bitte
cautionary advice taken to heart.
they won't/can't show me an example of a query file, but will share
the WSDL. I don't know how to build a static query file from this,
though
There was reference to a java client, so I'm inquiring about that.
On Aug 31, 2006, at 1:29 PM, Robert Garcia wro
riginal Message-
> From: Roland Dumas [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 31, 2006 2:34 PM
> To: witango-talk@witango.com
> Subject: Re: Witango-Talk: choicepoint SOAP
>
> cautionary advice taken to heart.
>
> they won't/can't show me an examp
PROTECTED]
http://scott.cadillac.bz
-Original Message-
From: Roland Dumas [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 31, 2006 2:34 PM
To: witango-talk@witango.com
Subject: Re: Witango-Talk: choicepoint SOAP
cautionary advice taken to heart.
they won't/can't show me an example
thank you.
Now to get the URL out of them.
On Aug 31, 2006, at 5:16 PM, Phil Wade wrote:
Roland,
A really simple way to build up a soap call is to use one of the
many WSDL validator to build it for you. A simple free tool can be
found here:
http://soapclient.com/soaptest.html
Simply typ
so I get the WSDL URL https://prosuite-staging.choicepoint.com/
IdentityManagerV1
I put it into a web browser and into the soaptest I get errors back
from both. Is there some other layer of soapsuds involved?
On Aug 31, 2006, at 5:16 PM, Phil Wade wrote:
Roland,
A really simple way to
This is returning like its the actual soap url, not the wsdl url.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ -
choicepoint doesn't expose the .wsdl file to the internet. It's
behind a firewall.
They say that they also intentionally change it to break clients that
aren't qualified. Therefore, just creating a query xml file from
something like soapclient.com will have a very short life span.
Going t
but you can always access the wsdl, right? you just couldn't show us?
correct?
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://big
it is behind a firewall.
go figure
On Sep 5, 2006, at 3:50 PM, Robert Garcia wrote:
but you can always access the wsdl, right? you just couldn't show
us? correct?
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
p
So even your app can't see the WSDL? or will your app be able to see
the WSDL?
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://big
well, the way it SEEMS to work is that the notion of web services
enables machine-to-machine information interchange. Platform
independent, etc.
However, this one is buried behind a firewall, so it requires a
client that can negotiate the firewall. They whipped up such a client
in .NET. T
Sounds like you may need to write some of this in .NET, and interface
with witango. Its not too difficult to have witango and .net work
together on same site/server. If you are deploying on windows of course.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventp
On Sep 5, 2006, at 4:51 PM, Robert Garcia wrote:
Sounds like you may need to write some of this in .NET, and
interface with witango. Its not too difficult to have witango
and .net work together on same site/server. If you are deploying on
windows of course.
Mac
and you see why this defe
Hi Roland,
> They say that they also intentionally change it to break
> clients that aren't qualified.
> this one is buried behind a firewall, so it requires a
> client that can negotiate the firewall. They whipped up such
> a client
> in .NET. There may be a java client, though I've n
true, I was thinking, it wasn't just a port, but some kind of vpn or
proxy, thinking the same thing, why woiuld you need a .net client to
get through a port?
Sounds like you could use some source code to see what all this stuff
is doing.
--
Robert Garcia
President - BigHead Technology
VP
On Sep 5, 2006, at 8:01 PM, Robert Garcia wrote:
true, I was thinking, it wasn't just a port, but some kind of vpn
or proxy, thinking the same thing, why woiuld you need a .net
client to get through a port?
Sounds like you could use some source code to see what all this
stuff is doing.
25 matches
Mail list logo
