Re: [castor-user] XML - Performance with castor binding framework

[Andrew Fawcett]

Title: Message

If you have any natural boundries or scoping within your XML document you can unmarshall these "XML fragments" into small chunks by selectively feeding XML to the unmarhsaller via your own SAX handler. Thus controlling the number of objects in memory at a given time.

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 15 December 2004 11:40
To: [EMAIL PROTECTED]
Subject: Re: [castor-user] XML - Performance with castor binding framework

Hi,

We have a requirement to read XML data (Unmarshall) that could extend to a size 4GB and more.

I'm not sure whether castor-xml framework will behave normally when number of objects grow in the JVM.

 

Is there any work around solution with this framework that is not memory intensive.

 

Thanks

Banujee

Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments.

Season's greetings from all at CODA The information in this message is confidential and may be legally privileged. It may not be disclosed to, or used by, anyone other than the addressee. If you receive this message in error, please advise us immediately. Internet emails are not necessarily secure. CODA does not accept responsibility for changes to any email which occur after the email has been sent. Attachments to this email may contain software viruses, which could damage your systems. CODA has checked the attachments for viruses before sending, but you should virus-check them before opening.

 

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-user