Skip to Content

Does ESP still reject XML records with missing tags?

Dec 15, 2016 at 04:04 PM


avatar image

Several months ago I reported a problem in the ESP XML adapter where it rejected events that didn't have every defined tag present in the data, rather than simply placing nulls in the corresponding ESP columns. I was told it would be added to the bug fix queue.

Has this been fixed yet? If so, in what version of ESP? If not, is there a projected date when it will be fixed?

I'm working a project where a third party parser is probably going to deliver events in XML format and this defect is likely going to generate problems on their end. I need to know whether this has to be pursued and what impact it will have on the development phase.



10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Dan Tarnower Dec 20, 2016 at 07:18 PM

Is anybody even reading these posts? Please bring back SCN!

10 |10000 characters needed characters left characters exceeded
Gerald Wang
Dec 21, 2016 at 09:33 AM

Hi Dan,

This has not been addressed. We are currently evaluating the changes required for this.



10 |10000 characters needed characters left characters exceeded
Jeff Wootton
Dec 21, 2016 at 03:05 PM

Dan: please contact me directly so that I can understand the context and prioritize this appropriately.

Note that a workaround would be to develop a custom XML parser module (java module for adapter toolkit).

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hi Jeff,

Thanks for the offer. I may have to take a few days to respond.

In the meantime, here's my original question:

My current requirement is a bit different. I'm starting a new project and the actual I/O connectivity hasn't been fully defined yet, but I suspect it will be receiving/sending XML through the socket adapter. So I won't be using the toolkit_file_xmldoc_input adapter. However, I need to know ASAP if the toolkit_socket_xmllist_<input/output> adapters behave the same way (ESP columns that aren't present in the XML cause the event to be ignored).

I will be working on this interface with another 3rd party, separate from the customer, and I don't know how much leeway they will be willing or able to give.