[XML-DEV Mailing List Archive Home]
[By Thread]
[By Date]
RE: [xml-dev] Editing huge files; recommended Java parsers?
- To: "Gregory Murphy" <Gregory.Murphy@...>, "David Byrden" <David@...>
- Subject: RE: [xml-dev] Editing huge files; recommended Java parsers?
- From: "Kevin Krouse" <kkrouse@...>
- Date: Fri, 24 Sep 2004 15:04:33 -0700
- Cc: <xml-dev@...>
- Thread-index: AcSiXC5VMnuh0F8uRf63I+Fsb26liwAJTdew
- Thread-topic: [xml-dev] Editing huge files; recommended Java parsers?
You can get XMLBeans from http://xmlbeans.apache.org/
The XmlCursor currently loads the entire document you're working on in
memory and you can walk/inspect it like DOM but with less overhead.
We're currently looking into a streaming version of XmlCursor. Stay
tuned.
--
Kevin Krouse
BEA Systems
-----Original Message-----
From: Gregory Murphy [mailto:Gregory.Murphy@...]
Sent: Friday, September 24, 2004 10:29 AM
To: David Byrden
Cc: xml-dev@...
Subject: Re: [xml-dev] Editing huge files; recommended Java parsers?
On Fri, 24 Sep 2004, David Byrden wrote:
> For editing files of around 200MB without unusual
> power or memory consumption, what is recommended
> for the Java platform?
> The edits are probably local, so the obvious approach
> is to build a memory tree for specific subtrees of the
> document. What parser would help? We'd like to do as
> little custom programming as possible.
You might want to look at the XML Cursor API provided by BEA XMLBeans.
It
allows you to walk through a document, token by token, and as needed
create
DOM-like objects of fragments. You can learn more from the on-line
documenatation:
http://e-docs.bea.com/workshop/docs81/doc/en/core/index.html
// Gregory Murphy. Isopaleocopria.
-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription
manager: <http://www.oasis-open.org/mlmanage/index.php>
|
