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. Currently 90% of this system still runs 'green-screen' and as such, things are often driven from within uv - mv.NET may have its place in a system that runs 90% via external client apps, however this isn't one of those cases.
Universe in general provides almost everything we need to do what we currently want to do, the implementation is often bizarre and incomplete and severely lacking in usable documentation & working samples, but with a little divination ( sometimes more ) it can be figured out. Hence my posting here. As for my question, I am leaning toward just sticking to callHttp rather 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: [email protected] Subject: RE: [U2] SOAP API [ad] 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 minutes. mv.NET uses UO.NET as a raw data pipe. Think of mv.NET as a suite of libraries that make development much easier for many purposes. For your purposes you don't need mv.NET, but I encourage you to consider mv.NET as a superset over UO that will save time with a lot of projects. For example, mv.NET faciliates both inbound and outbound web services. Email me for an mv.NET FAQ, which includes pricing info and a link to download documentation and a free trial of the software. Nebula R&D is a worldwide distributor of mv.NET, providing installation assistance, product support, and development and training services for .NET and mv.NET. Code samples provided by Nebula R&D include ADO.NET, ASP.NET, and Web Services, using VB.NET and C# for side-by-side comparison. HTH Tony Gravagno Nebula Research and Development TG @ removethispartNebula-RnD.com gerry wrote: > 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. > However as far as I can tell, it has actually makes it messier. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
