RE: Is Axis creating a DOM object and hence it may cause memory issue?

[Anne Thomas Manes]

When using the RPC provider (RPC, Wrapped, or Document style), Axis uses SAX to parse the message and convert the XML to Java objects. When using the MSG provider (Message style), Axis converts the message into a DOM.   From: Liu, Scott [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 14, 2004 6:10 PM To: [EMAIL PROTECTED] Subject: RE: Is Axis creating a DOM object and hence it may cause memory issue?   Thanks, Anne.   Does this imply that if I use Axis’ doc/literal web services framework it would be safe to assume the system memory is checked but in Axis messaging framework the system memory may not be optimized?   Scott   -----Original Message----- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 13, 2004 1:38 PM To: [EMAIL PROTECTED] Subject: RE: Is Axis creating a DOM object and hence it may cause memory issue?   The Axis Messaging interface returns a DOM. Use the JAX-RCP interface instead. It returns Java types.   From: Liu, Scott [mailto:[EMAIL PROTECTED] Sent: Monday, April 12, 2004 9:21 PM To: [EMAIL PROTECTED] Subject: Is Axis creating a DOM object and hence it may cause memory issue?   I have read somewhere that Axis uses SAX parser and the memory is basically well managed. But in org.apache.axis.message.SOAPBodyElement class the getDocumentElement method is implemented as such    private static Element getDocumentElement(InputStream input) {         try {             return XMLUtils.newDocument(input).getDocumentElement();         } catch (Exception e) {             throw new InternalException(e);         }     }   So the XMLUtils.newDocument(input) will return a DOM object? This worries me a little bit.   When the InputStream contains 100MB xml data this DOM object is going to consume a lot of memory (it will make the Axis not usable?). Am I missing something here?   Thanks,   Scott