Hi Astrid,
My apologies! I made a mistake when I tried my example <all> containing 36 children; I'm now able to reproduce your problem.
A fix for this bug is available by extracting the latest source from CVS. Sorry for any inconvenience this has caused you.
Thanks,
Henry
------------------------------------------------------------------------
Henry Zongaro XML Parsers development
IBM SWS Toronto Lab Tie Line 778-6044; Phone (416) 448-6044
mailto:[EMAIL PROTECTED]
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: <xsd:all> - high memory need
Hi Henry,
thanks a lot for your fast response !
There might be a point to your suggestion with my classpath, as I am using Jdom and Xalan too, which both use Xerces - maybe an old version. It will take me a while to figure out a way to make all versions work together with Xerces-J 1.4.1. If this does not solve my problem, I will send a new SOS with my example.
Thanks,
Astrid
-----Urspr�ngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 23. Juli 2001 15:24
An: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Betreff: Re: <xsd:all> - high memory need
Hi Astrid,
Actually, there was a change of implementation for <all> that was first made available in Xerces-J 1.4.0 that should have reduced the amount of memory required for <all>. I just tried an example in which a schema contains an <all> with 36 children, each of which has minOccurs="0". The profiling tool I tried showed that the maximum amount of heap storage used was under 4MB.
Could there be a problem in your CLASSPATH? If not, please try posting an example that reproduces your problem.
Thanks,
Henry
------------------------------------------------------------------------
Henry Zongaro XML Parsers development
IBM SWS Toronto Lab Tie Line 778-6044; Phone (416) 448-6044
mailto:[EMAIL PROTECTED]
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: <xsd:all> - high memory need
Hi there,
my Schema contains an <xsd:all> with about 25 elements with minOccurs="0".
Using Xerces 1.4.1 this takes more than my free 48M of memory (
java.lang.OutOfMemoryError) while using a <xsd:sequence> the same small
programm uses about 6M.
Is there hope for a change in implementation of <xsd:all> in Xerces ? Or can
anyone give me an idea of how I can avoid this OutOfMemoryError without
fixing a special sequence for my elements ?
Looking forward to your answers,
Astrid
