Tony,
I'm interested, why not just use xslt to convert the
XML directly into a U2 string and then pass in the
data using uodotnet subroutines. Is there some
advantage in using an extra step of converting to ADO?
Unfortunately the U2 XSLT routines won't let you do this as they insist
that the output from your stylesheet XML and do not accept the text
output method.
If you know xslt, xpath, xquery, etc, knock your socks off. I'd guess
there are about 5 people in this entire group who have a working
proficiency with them.
Careful Tony you might be surprised.
A better reason is that (again very subjectively) I don't see a reason to
write a transformation into a string which then needs to be reparsed via
string manipulation in yet another program. If you're going to do that,
just parse the data manually in UniBasic anyway.
But the simplest way might be XML to dynamic array -- if the U2 routines
allow it.
This struck me as another case where IBM thought about adding a
technology to U2 but didn't fully understand the technology they were
adding -- XSL can output text, why not consider that users might want to
generate non-XML output; MQ Series supports transactions for message
operations but does U2?; Unix allows processes to "share" an open socket
(or queue together to recieve requests) why not let the sockets
implementation support this?
rant rant,
Craig
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
