We've had good success with Saxon for this kind of thing. mxAjax / CFAjax docs and other useful articles: http://www.bifrost.com.au/blog/
2009/9/15 Barney Boisvert <bboisv...@gmail.com>: > > I'd recommend grabbing a SAX parser and using that instead of the > DOM-based stuff that CF ships with. Then you can stream the file in > and deal with it's nodes sequentially, rather than having to inflate > the whole thing into a DOM tree to manipulate. Definitely can make > the code trickier to write since you only have one shot at each node, > but it'll save your ass with the memory constraints. > > cheers, > barneyb > > On Mon, Sep 14, 2009 at 2:42 PM, Alan Rother <alan.rot...@gmail.com> wrote: >> >> Hey All, >> I'm trying to parse out a 65mb XML file from a customer... Don't ask... >> Every time I try to hit it with XMLParse(), memory spikesfrom 500mb to 1,200 >> and then crashes CF.... >> >> Has anyone else dealt with big XML files like this? >> >> >> =] >> >> -- >> Alan Rother >> Adobe Certified Advanced ColdFusion MX 7 Developer >> Manager, Phoenix Cold Fusion User Group, AZCFUG.org >> >> >> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:326306 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
