I can find very little Sybase documentation for doing XML to
stream, or stream to XML conversions. My feelings are that
converting a simple basic XML file is easier to work with
than
one with geeked out, multiple nested tags, and nested
groups.
I've done enough trial and error (T&E) coding to figure that
much out. It appears to me the Impact tool can only work
with a
simple XML file. Has anyone else come to this conclusion?
While
trying to do an XML to stream conversion on a complex file,
I
get an odd collection of bugs. Has anyone else experienced
these?:

1) While processing a nested group the transaction
production
will only process the group one time and then on any
subsequent attempt to process the same group fails. It
just
doesn't process the loop again.
2) Trying to use a data link in a rule component total
screws
up the output.
3) If the inbound field is empty, and it is mapped in an
out-
bound rule component, transaction production fails
stating
the inbound field is empty. I get around this by putting
a
blank in the default value field. (I've seen this error
mentioned in other newsgroup entries.)
4) When in a rule component you have the option to check
whether you want to use either the 'Data' or 'Attr.'
values.
I've noticed that I can set these to 'Data' and save the
prod obj. Then when I close and re-open the prod obj, the
selection magically gets changed to 'Attr.'.

Has anyone else seen anything like this? If so, I'd love
your
input. Thank you.