Hello,
I believe the current limitation is about 8 elements in an "all".
I'm working on a change to the implementation for the Xerces-J 1.4
release that will remove the limitation. I'll post to xerces-j-user when
the change is in CVS.
Thanks,
Henry
------------------------------------------------------------------------
Henry Zongaro XML Parsers development
IBM SWS Toronto Lab Tie Line 778-6044; Phone (416) 448-6044
mailto:[EMAIL PROTECTED]
"Scott J. Geertgens" <[EMAIL PROTECTED]> on 2001/04/06 02:20:06 PM
Please respond to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: RE: Schema : sequence vs all (OutOfMemoryError)
I believe this is a known performance issue, with a resolution targetted
for Xerces 2. The general rule in the mean time is to not use 'all' when
you
plan to have more than 3(?) elements at that level.
SJG
-----Original Message-----
From: Benson Cheng [mailto:[EMAIL PROTECTED]
Sent: Friday, April 06, 2001 12:17 PM
To: [EMAIL PROTECTED]
Subject: Schema : sequence vs all (OutOfMemoryError)
I want my schema to allow the xml elements in any order, so I changed all
of
the "sequence" to "all", on some of the schemas works fine, but some of
them
will run for a long time and finally give me an "OutOfMemoryError" as
below:
Exception in thread "main" java.lang.OutOfMemoryError
<<no stack trace available>>
Is anybody run into this problem before? Or what kind of rule need to be
followed in order to use "all"?
BTW, I am using xerces version 1.3.0
Thanks in advance,
Benson.
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
