[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlbeans-dev
Subject:    [jira] Resolved: (XMLBEANS-323) SchemaTypeLoaderException "Too Many
From:       "Radu Preotiuc-Pietro (JIRA)" <xmlbeans-dev () xml ! apache ! org>
Date:       2007-04-26 23:51:17
Message-ID: 21309585.1177631477156.JavaMail.jira () brutus
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/XMLBEANS-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Radu Preotiuc-Pietro resolved XMLBEANS-323.
-------------------------------------------

       Resolution: Fixed
    Fix Version/s:  Version 2.3

Fixed with svn change 532870.

I have changed it to an unsigned short so now the limit is 64535. Representing the \
size of arrays as two bytes is common throughout the xsb format, I suspect it was \
inspired from the Java .class specification.


> SchemaTypeLoaderException "Too Many Strings" while writing inde.xsb file
> ------------------------------------------------------------------------
> 
> Key: XMLBEANS-323
> URL: https://issues.apache.org/jira/browse/XMLBEANS-323
> Project: XMLBeans
> Issue Type: Improvement
> Affects Versions: Version 2.1
> Environment: Windows XP SP2
> Reporter: Kyle Yin
> Fix For:  Version 2.3
> 
> 
> While trying to build a project containing a large number of schemas, XMLBeans \
> throws SchemaTypeLoaderException with the error message "Too many Strings (46252) \
> ... index .... code 10".   After a quick glance at SchemaTypeSystemImpl.StringPool, \
> the error message seems to be caused by the project having more schema element \
> types than the hardcoded upper limit Short.MAX_VALUE, which is rough 32k.  Could \
> someone please kindly clarify for me:  1.  What is the significant of \
> Short.MAX_VALUE ?  Why Short.MAX_VALUE instead of something like Integer.MAX_VALUE? \
>  2.  Is it reasonable to ask for an increase in this upper limit?  
> 3.  Apart from splitting up my project into smaller modules with fewer element \
> types, is there any other work-around solution for now?  Thanks!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]