Heath
doo...@brainfood.com wrote:
From: Adam Heath doo...@brainfood.com
Subject: Re: Discussion: XML file parsing improvement
To: dev@ofbiz.apache.org
Date: Saturday, April 25, 2009, 9:52 PM
Adrian Crum wrote:
OFBiz uses a lot of XML files. When each XML file
is
read, it is first parsed
--- On Sat, 4/25/09, Adrian Crum adrian.c...@yahoo.com wrote:
From: Adrian Crum adrian.c...@yahoo.com
Subject: Re: Discussion: XML file parsing improvement
To: dev@ofbiz.apache.org
Date: Saturday, April 25, 2009, 10:28 PM
Adam and David,
Thank you for your comments! I'll look into the entity
OFBiz uses a lot of XML files. When each XML file is read, it is first parsed
into a DOM Document, then the DOM Document is parsed into OFBiz Java objects.
This two-step process consumes a lot of memory, and it takes more time than it
should.
There is an alternative - what is called
The outcome of optimizing the memory usage and helping to get past some of
these out of memory issues is definitely a big win - but I don't know enough
about the event-driven parsing paradigm to speak to the outcome. I guess my
vote would be that it's worth a shot for sure.
Cheers,
Tim
--
Tim
I'm guessing you're speaking of SAX parsers when you talk about event-
driven parsing.
If you take a look at the entity XML import code it actually is a SAX
event-driven parser.
As for other XML readers (like entity defs, widget XML files, etc,
etc) I'd be surprised if a SAX reader
Adrian Crum wrote:
OFBiz uses a lot of XML files. When each XML file is
read, it is first parsed into a DOM Document, then the
DOM Document is parsed into OFBiz Java objects. This
two-step process consumes a lot of memory, and it
takes more time than it should.
There is an alternative -
: Re: Discussion: XML file parsing improvement
To: dev@ofbiz.apache.org
Date: Saturday, April 25, 2009, 9:52 PM
Adrian Crum wrote:
OFBiz uses a lot of XML files. When each XML file is
read, it is first parsed into a DOM Document, then the
DOM Document is parsed into OFBiz Java objects
