RE: optimizing memory consumption with XMLBeans

[Cezar Andrei <ce...@bea.com>]

Mario,

 

XMLBeans works with an in-memory xml store, it loads and saves the data
to and from streaming API's like SAX, STAX but the entire document will
be stored in memory. To avoid this, one can handle the stream and load
only small parts that fit in memory, one at a time. 

 

This isn't a usual scenario for XMLBeans right now, but we think this
would be a useful feature to add. 

 

If anybody is interested to look into it, he should consider using
XMLStreamReaderExt (which provides java typed data) and
ValidatingInfoXMLStreamReader (which provides schema related info).

 

Cezar

 

 

________________________________

From: Mario Rodriguez [mailto:rvillane@gmail.com] 
Sent: Tuesday, March 21, 2006 5:21 PM
To: user@xmlbeans.apache.org
Subject: Re: optimizing memory consumption with XMLBeans

 

I see, and XMLBeans implementation supports sTax ? for very fast
processing and light memory usage 

On 3/21/06, Radu Preotiuc-Pietro < radup@bea.com <ma...@bea.com>
> wrote:

Not sure what you are asking. On one hand, XmlBeans is indeed by default
using SAX to interface with the XML parser, but on the other, XmlBeans
is an in-memory XML processing tool, so if you need to process a huge
XML file, you would need a huge amount of (virtual) memory to do it.

 

Radu

 

________________________________

From: Mario Rodriguez [mailto:rvillane@gmail.com] 
Sent: Monday, March 20, 2006 12:12 PM
To: user@xmlbeans.apache.org
Subject: optimizing memory consumption with XMLBeans

Hi people, there is any way to configure XMLBeans to use SAX in order to
feed business objects generated by the scomp tool ?  What a I need is to
optimize  memory consumption because I'm feeding XML beans with huge XML
files 

thanks


-- 
Mario Rodriguez 

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.