https://bz.apache.org/bugzilla/show_bug.cgi?id=48995
Rodolfo Botto <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW --- Comment #7 from Rodolfo Botto <[email protected]> --- I have the same problem reported in this incident, working with poi 3.13 also. I take the sample code here, generate a main program and a sample worksheet that fails to validate on Excel 2010 and Excel 2013. Also fails on OpenXML SDK 2.0 Productivity Tool (ScreenShot provided). If you see the reported error, Validation reports that elemnt sz is unexpected in current context. Letting Excel 2013 to adjust the worksheet and saving it again, new worksheet validates with no problem. Comparing screenshots, you can see the only difference between two font definitions is element order. Invalid has (FontName, FontSize, Bold, Color). Valid one has (Bold, FontSize, Color, FontName) The order that poi save the elements, is the order the setMethods are invoked on XSSFFont, (constructor invokes 2 methods, in bad order). I've made a workaround in my case, changing the order of set (and adding somes) on constructor of XSSFFont, but is an incomplete solution, if not all properties are setted. I have no clue on how to affect serialization order on xmlbeans library, may be you can apply a more generic solution to this problem. Thanks in advance, Rodolfo Botto -- 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]
