20
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] SOAP API [ad]
Thanks Tony, but ...
the web services we use are .NET, the HelloWorld example I used took
less than minutes to setup. We also have inbound and outbound web
services that use UO.NET. I'm not sure why we would want to pay for an
addi
Hi Gerry
UniVerse Ver10.2 has a soap interface and tool. You can use this to build
up soap server for UniVerse. You can set up a subroutine or use TCL to
process requests. It simplifies a lot of the process. However it still
lacks the element of identifying the user.
With SOAP you need t
gerry wrote:
> Thanks Tony, but ...
> the web services we use are .NET, the HelloWorld example I used took
> less than minutes to setup. We also have inbound and outbound web
> services that use UO.NET. I'm not sure why we would want to pay for
> an additional framework for such a simple thing.
ather
than fighting with the SOAP API - but the jury is still out for another
day or so.
Gerry
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tony Gravagno
Sent: June 1, 2007 4:55 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] SOAP API [ad]
Gerry
Gerry, the .NET framework has all of this building and parsing built-in, as
well as auto-generation of web service clients and servers. With UO.NET or
mv.NET you can create a front-end to your app with absolutely no concern
for XML or SOAP envelopes. You can get your HelloWorld function within
mi
2:45 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] SOAP API
You get that string, but there are commands you can use which parse it
into ordinary dynamic arrays. Look at the XDOM and XMAP related
commands.
IBM has sample basic code posted on their site that shows you how to ge
:[EMAIL PROTECTED] On Behalf Of gerry-u2ug
Sent: Friday, June 01, 2007 2:19 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] SOAP API
We have some older code that works with a web service via the CallHttp
API.
I am looking at some newer things and decided to look into using the
SOAP API instead of
We have some older code that works with a web service via the CallHttp
API.
I am looking at some newer things and decided to look into using the
SOAP API instead of CallHttp mainly because I assumed that the SOAP API
would make things 'cleaner' in particular when accessing the returned
data.
Howeve
