OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cam message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [cam] [Fwd: [Fwd: Re: [xml-dev] Editing huge files; recommended Java parsers?]]


David,
 
We used XML Beans to generate Java objects for CIQ Specifications.
It works well.
 

Regards,

Ram

Ram Kumar
General Manager
Software R&D and Architecture
MSI BUSINESS SYSTEMS
Suite 204A, 244 Beecroft Road
Epping, NSW 2121, Australia
Direct: +61-2-9815 0226
Mobile: +61-412 758 025
Fax: +61-2-98150200
URL: www.msi.com.au

 


From: David RR Webber [mailto:david@drrw.info]
Sent: Wednesday, September 29, 2004 1:09 AM
To: TC, CAM OASIS,
Subject: [cam] [Fwd: [Fwd: Re: [xml-dev] Editing huge files; recommended Java parsers?]]

Of interest from the XML-dev list.

DW


Subject:
RE: [xml-dev] Editing huge files; recommended Java parsers?
From:
"Kevin Krouse" <kkrouse@bea.com>
Date:
Fri, 24 Sep 2004 15:04:33 -0700
To:
"Gregory Murphy" <Gregory.Murphy@eng.sun.com>, "David Byrden" <David@Byrden.com>
CC:
<xml-dev@lists.xml.org>

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@eng.sun.com] 
Sent: Friday, September 24, 2004 10:29 AM
To: David Byrden
Cc: xml-dev@lists.xml.org
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.





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]