>I suspect you'll find many SOAP environments have a hard time with
>this. If you're sending giant data, attachments are likely to be more
>efficient. But attachments have interop troubles, and they're not
>objects. I'd like to be able to send arrays of 100,000 complex objects
>and have them available to my server demarshalled. Barring that, I'd
>like to know what the practical limits are.
Yes, you are right. But in this specific scenario, I don't have any interoperability
requirements. The communication is axis-axis.
By the way, I think (but not sure 100%) that the Basic Profile 1.0 should support
SAAJ.
Luciano
-----Original Message-----
From: Nelson Minar [mailto:[EMAIL PROTECTED]]
Sent: Monday 23 February 2004 19:44
To: [EMAIL PROTECTED]
Subject: RE: Axis 1.1 Memory leaks
>the problem that I'm experiencing is related to some (known?) Axis problem to
>handle large xml documents.
Understood. Does anyone have a simple benchmark that shows how much
memory Axis consumes as a function of the size of the SOAP messages?
>In fact, I'm sending back and forth binary files or large xml files
>(2.5Mb) without using the SAAJ specification or the code used in the
>/sample/attachemnt folder of Axis1.1 distrib.
I suspect you'll find many SOAP environments have a hard time with
this. If you're sending giant data, attachments are likely to be more
efficient. But attachments have interop troubles, and they're not
objects. I'd like to be able to send arrays of 100,000 complex objects
and have them available to my server demarshalled. Barring that, I'd
like to know what the practical limits are.
Any e-mail message from the European Central Bank (ECB) is sent in good faith but shall neither be binding nor construed as constituting a commitment by the ECB except where provided for in a written agreement.
This e-mail is intended only for the use of the recipient(s) named above. Any unauthorised disclosure, use or dissemination, either in whole or in part, is prohibited.
If you have received this e-mail in error, please notify the sender immediately via e-mail and delete this e-mail from your system.
