There is no guarantee that the change I added will help. We may do a release of XMLBeans 5.2.0 in a month or 2 but it is delayed because of a need to do a POI 5.2.5 release.
On Friday 20 October 2023 at 14:06:52 IST, Yitzchak Weiser <[email protected]> wrote: Thanks for the commit! Do you know when the next release is expected? On Tue, Oct 17, 2023 at 9:26 AM PJ Fanning <[email protected]> wrote: > Your issue appears to be exactly XMLBEANS-474. > > This is a volunteer set of projects and generally, the best approach is if > you have a problem with the existing behaviour is to try to write a patch. > > There is not much activity on the XMLBeans project. > > It may be worth your while considering finding an alternative lib, one > that is more actively maintained. > > The issue here is best discussed in the JIRA issue. > > > > > > > On Tuesday 17 October 2023 at 14:13:19 IST, Yitzchak Weiser < > [email protected]> wrote: > > > > > > Hi, > When trying to save an XMlObject sized over 1GB I am getting a > -2147483648 > java.lang.NegativeArraySizeException: -2147483648 > at org.apache.xmlbeans.impl.store.Saver$TextSaver.resize(Saver.java:1582) > at org.apache.xmlbeans.impl.store.Saver$TextSaver.preEmit(Saver.java:1215) > at org.apache.xmlbeans.impl.store.Saver$TextSaver.emit(Saver.java:1180) > at org.apache.xmlbeans.impl.store.Saver$TextSaver.emitText(Saver.java:979) > at org.apache.xmlbeans.impl.store.Saver.process(Saver.java:299) > at org.apache.xmlbeans.impl.store.Saver$TextSaver.write(Saver.java:1696) > at > > org.apache.xmlbeans.impl.store.Saver$InputStreamSaver.ensure(Saver.java:2348) > at > > org.apache.xmlbeans.impl.store.Saver$InputStreamSaver.access$200(Saver.java:2234) > at > > org.apache.xmlbeans.impl.store.Saver$InputStreamSaver$OutputStreamImpl.read(Saver.java:2393) > at > > org.apache.xmlbeans.impl.store.Saver$InputStreamSaver.lambda$read$0(Saver.java:2332) > at org.apache.xmlbeans.impl.store.Saver.syncWrap(Saver.java:2184) > at org.apache.xmlbeans.impl.store.Saver.access$000(Saver.java:33) > at > org.apache.xmlbeans.impl.store.Saver$InputStreamSaver.read(Saver.java:2332) > at java.base/java.io.InputStream.read(InputStream.java:205) > at org.apache.xmlbeans.impl.store.Cursor._save(Cursor.java:570) > at org.apache.xmlbeans.impl.store.Cursor.lambda$save$17(Cursor.java:2006) > at org.apache.xmlbeans.impl.store.Cursor.syncWrapHelper(Cursor.java:2551) > at org.apache.xmlbeans.impl.store.Cursor.syncWrapIOEx(Cursor.java:2504) > at org.apache.xmlbeans.impl.store.Cursor.save(Cursor.java:2006) > at > org.apache.xmlbeans.impl.values.XmlObjectBase.save(XmlObjectBase.java:190) > at > org.apache.xmlbeans.impl.values.XmlObjectBase.save(XmlObjectBase.java:209) > > Is this a hard limitation for xmlbeans? > I found this bug https://issues.apache.org/jira/browse/XMLBEANS-474 but > its > not clear to me what the expected behavior is? > Using the latest xmlbeans 5.1.0 > > Thanks! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
