The xml tools in u2 do allow very easily the extraction of certain elements
and attributes from xml files. I have just the one 100 line databasic
program, I supply it the path to an xml file, the path to the .ext
extraction file, it then returns a dynamic array. Sometimes if you want to
go through
Symeon is right; the various XML tools in U2 are actually pretty good and
the DOM parser is entirely written to standards.
The real problem is that the documentation for them is frankly terrible and
there is no good overview on which tools should be used in which
circumstances.
Hmm, sounds like I
Well done Brian for volunteering.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Brian Leach
Sent: 28 January 2012 12:52
To: 'U2 Users List'
Subject: Re: [U2] UniVerse Import XML data [not-secure]
Symeon is right;
I agree with Brian, the documentation is atrocious. If one follows the
examples in the documentation, shouldn't *something *work? But not so with
the XDOM stuff. Awful, awful docs.
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserve
Thanks for the input guys, appreciate it. Tom, thanks for posting that
link; I had forgotten about that one, but I suspect it's a different
situation than what I'm seeing here. In that case the printer wasn't being
assigned when it should; in this case the PRINTER OFF in Unidata appears to
be doi
Hi Jake,
Are these subroutines you could share?
Thanks,
Charlie Noah
On 01-27-2012 3:47 PM, Holt, Jake wrote:
I just created a set of subroutines I copy and paste into anything that
uses reads or writes XML. Most interfaces don't handle much beyond
reading and extracting the element, value an
> From: Symeon Breen
> The guys at u2 did NOT write their own xml parser,
> they use the libraries from the OS, so on udt on
> linux, 7.1 used libxml, 7.2 uses libxerces - just the
> same as php, or java, or the linux xml tools, like
> xmlwf. So if it fails in u2 it will fail in php.
I had no
