https://bz.apache.org/bugzilla/show_bug.cgi?id=59252
lawern changed:
What|Removed |Added
CC||lars.wer...@agentes.de
--
You are receiving
https://bz.apache.org/bugzilla/show_bug.cgi?id=59252
lawern changed:
What|Removed |Added
Version|3.14-FINAL |5.0.x-dev
--
You are receiving this mail
https://bz.apache.org/bugzilla/show_bug.cgi?id=59252
Sz.Noemi changed:
What|Removed |Added
CC||noemi.szemen...@foconis.de
--
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=59252
--- Comment #7 from Francisco Castaneda
---
I had the same problem, unless you call write on an outputstream, changes won't
be saved.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=59252
--- Comment #6 from Marcel M. ---
I just hit this bug in 5.0.0.
A (wasteful) workaround is to write to a NullOutputStream to trigger the in
place update of the File:
try (Workbook wb = WorkbookFactory.create(new File("foo"));
https://bz.apache.org/bugzilla/show_bug.cgi?id=59252
Javen O'Neal changed:
What|Removed |Added
Depends on||57919
--
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=59252
Dominik Stadler changed:
What|Removed |Added
Depends on||59287
--
https://bz.apache.org/bugzilla/show_bug.cgi?id=59252
--- Comment #5 from Javen O'Neal ---
Testing the change to POIXMLDocument.close from comment 4, I got an error on
TestXSSFBugs.bug45431 (which relates to a macro-enabled workbook):
"Rule M2.4 exception : this error should
I never understood why the default is to write changes to disc.
I'd prefer the default to leave the document unchanged and only write the
changes when commit() is called.
close() should be callable in any case, possibly throwing away any temporary
objects -
and it should be ok, to call it again.
This is a candidate for GSOC or Help Wanted.
Need WorkbookFactory.create and XSSFWorkbook constructor to open read only
Should not write to file on close if a workbook is merely opened and not
modified.
Sounds like changing close's behavior is contentious, so we'd need to
decide what direction
https://bz.apache.org/bugzilla/show_bug.cgi?id=59252
--- Comment #3 from Alex ---
Ok,I think I understand your point, close() shouldn't save to file (and I
actually agree with that) but what I'm saing its that it actually doesn't save
on close() with 3.14 release unless you
https://bz.apache.org/bugzilla/show_bug.cgi?id=59252
--- Comment #2 from Nick Burch ---
OPCPackage has always supported in-place write for Files. OPOIFS never did,
while NPOIFS now does. Because OPOIFS never did, and that's all we had for
agest, the usermodel APIs never did
https://bz.apache.org/bugzilla/show_bug.cgi?id=59252
Javen O'Neal changed:
What|Removed |Added
OS||All
--- Comment #1
13 matches
Mail list logo