[Bug 57450] [PATCH] A way to autosize columns on SXSSF

https://bz.apache.org/bugzilla/show_bug.cgi?id=57450 Stefan Thurnherr changed: What|Removed |Added Attachment #33251|0 |1

[Bug 57450] [PATCH] A way to autosize columns on SXSSF

https://bz.apache.org/bugzilla/show_bug.cgi?id=57450 --- Comment #9 from Stefan Thurnherr --- Attaching an updated patch file with a refactored solution (after discussion on DEV mailing list). Main aspects: * AutoSizeColumnTracker is now completely internal and

[Bug 58597] XWPFDocument causes SecurityException under securitymanager

https://bz.apache.org/bugzilla/show_bug.cgi?id=58597 --- Comment #8 from Uwe Schindler (ASF) --- I will commit the patch tomorrow and proceed with more fixes like this. This should also fix the issue of Robert. -- You are receiving this mail because: You are the assignee for

[Bug 58597] XWPFDocument causes SecurityException under securitymanager

https://bz.apache.org/bugzilla/show_bug.cgi?id=58597 Uwe Schindler (ASF) changed: What|Removed |Added Attachment #33267|0 |1 is

[Bug 58597] XWPFDocument causes SecurityException under securitymanager

https://bz.apache.org/bugzilla/show_bug.cgi?id=58597 --- Comment #10 from Uwe Schindler (ASF) --- I committed this now. There are more setAccessible calls outside of test that are not yet wrapped. I will work on remving them in a similar way. The root cause of this issue is

Re: Potential POI 3.13 performance regression

On Tue, 10 Nov 2015, Jon Iles wrote: I've been advised that one change which was made between 3.12 and 3.13 was the move from OPOIFS to NPOIFS. I'm not familiar with the internals of POI, and I'm wondering if it is possible to switch between these two implementations in 3.13 to see if this