I appreciate that, and I'm not afraid to use third party middleware when it makes sense. It doesn't really make sense in this instance. It took all of about six lines of code to create the SOAP request, set the XML and submit the request. It's certainly not stretching the language when the functionality is built in. Constructing the SOAP request is trivial. Parsing the return is a little more work, but not difficult.
Rather than even waste time trying to figure out why the xalan and xerces libs wouldn't load (this thing is running on an old SCO OSR 5.0.7 box after all), I just scrapped the built in XDOM routines and resurrected an XML parser I wrote in Basic years ago. A couple of simple subroutine calls, and I have the fields I want from the XML doc. At any rate, I was creating a "proof of concept", and now it's done. I'll be cleaning it up and implementing it next week. --Larry Larry Hiscock Western Computer Services -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony G Sent: Friday, August 22, 2008 3:52 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] SOAP in Unidata 6.1 Larry - I didn't recognize up front that you were talking about UD as webservice client. However the solution is the same. Creating a web service client and/or only takes a couple seconds (as seen in the video). This is how our products work - we write an item to a file that's polled every second or so, the data is pulled into a middle-tier, then it's passed to a web service and the result is passed back through the same channel. The MV DBMS never needs to speak to a web service. There's no SOAP, no XML, no protocols, no xerxes libs or xalan - and to move data to a relational DBMS we never use VSG, ODBC, or flatten data. The value-add that we provide is to make the entire process available through well-defined BASIC subroutines so that the MV developer doesn't need to know anything at all about "how" an external interface works. I don't know why people are so absolutely fixated on spending all of this time to make the MV environment do all of these things when there are non-MV tools (free and otherwise) that specialize in doing them. Tony Gravagno Nebula Research and Development TG@ remove.pleaseNebula-RnD.com > -----Original Message----- > From: Larry Hiscock > Thanks for the example. This is pretty close to what > I had. The problem turns out to be that apparently > Unidata doesn't build the SOAP envelope quite right if > you use the SOAPSetParameters function as the example > in the manual does. When I built the entire content > manually, and used SOAPSetRequestContent, everything > worked just fine. > > Now to see if I can find out why Unidata won't load > the xalan and xerces libs to parse the XML :-S ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
