https://bz.apache.org/bugzilla/show_bug.cgi?id=62834
--- Comment #2 from Greg Woolsey <[email protected]> --- Hmm. Along the way I noticed this call flow: XSSFSheet.onDeleteFormula(XSSFCell) calls XSSFCell.getCellFormula() calls XSSFCell.getCellFormula(XSSFEvaluationWorkbook) with a null parameter, so it creates a new one, but only when it needs to call convertSharedFormula(). Looks like the next step is to see just how bad it will be to get the actual evaluation object from the formula evaluator down into that context. I suspect that's where things really go wrong, using a different evaluation instance than the one in use higher in the call stack. I'm not a fan of passing nulls, but since part of the code already expects that possible input, getCellFormula(), I suppose it isn't too awful. Better ideas welcome. That's not the bug here, though, that's just something that will bite someone down the road if it isn't handled. I'm implementing passing the needed value from the FormulaEvaluator, and adding JavaDoc about invalidating evaluator instances for other callers, without changing the public API for now. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
