Output contains \n characters
Issue #37
resolved
I'm not sure if this is the connector or xmlservice, but I'm getting \n characters after every <parm> and <data> tag. It's adding unnecessary output byte/iPLUG size. Does anyone know more about this? Is there a way to remove it?
['<pgm name=\'...\' lib=\'...\' error=\'fast\'>\n<parm io=\'out\'>\n<data type=\'100a\' io=\'out\' name=\'...\'>...</data>\n...']
Comments (7)
-
-
reporter
I am making a direct call using idb-connector with
call QXMLSERV.iPLUG512K(?, ?, ?, ?)and the result includes the \n in the output string. The XML is still valid, it's just unnecessary bytes.I guess I can answer my own question. I'm just having trouble understanding it all.
-
Interesting. I have not seen that before. This must be coming from XMLService, though. This could be verified by running your same query from a tool like Run SQL Scripts. Perhaps we should open an issue over at the XMLService repo once verified.
-
The newline characters are definitely coming from XMLService. I ran call QXMLSERV.iPLUG512K(?, ?, ?, ?) using Run SQL Scripts (I used https://bitbucket.org/litmis/nodejs-itoolkit/src/master/test/rpg/zzcall.rpgle to test with) and the output has the newline characters in it. Is https://bitbucket.org/inext/xmlservice-rpg/issues the right place to post the issue?
-
Yes, that's the correct spot. Thanks!
-
@bjerome I posted the issue under https://bitbucket.org/inext/xmlservice-rpg/issues/14/output-contains-n-characters so I think the issue in this repo can be closed.
-
reporter
- changed status to resolved
Agreed. Thanks for posting!
- Log in to comment
Brian, are you using the itoolkit with the iDb2Call transport? Or are you calling xmlservice directly, with this connector?
Also, just to verify, the
\nyou're seeing is the actual newline character, not an actual "\n", right? In other words, the XML is still perfectly valid, but has unnecessary bytes due to the newlines?