Currently, the only J support for SAX is in older 32 bit versions of J. That mechanism has been replaced by expat in current versions of J.
(I haven't used expat to comment on how well that api works. I should fix this. But, for now, I don't have enough experience to comment further.) Thanks, -- Raul On Tue, Aug 10, 2021 at 12:06 PM Mariusz Grasko <[email protected]> wrote: > > Hi, > > We are ecommerce company and have a lot of integrations with suppliers, > products info is nearly always in XML files. I am thinking about using J as > an analysis tool, do you think that working with large files that need to > be parsed SAX- style without reading everything at once is good idea in J ? > Also is this even advantageous (as in, would code be terse). Right now XML > parsing is done in Golang, so if parsing in J is not very good we could try > to rely more on CSV exports. CSV is definiately very good in J. > I am hoping that maybe XML parsing is very good in J and the code would > become much smaller, if this is the case, then I would think about using J > for XMLs with new suppliers. > > Best Regards > M.G. > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
