https://bz.apache.org/bugzilla/show_bug.cgi?id=66079
--- Comment #4 from Vladislav Arakelov <[email protected]> --- (In reply to PJ Fanning from comment #3) > Vladislav - since you understand the issue better than the rest of use after > researching it, can you suggest changes to test63788 to better test this > issue? That test passes with and without your suggested change. It's complicated, because ctNumbering has private access in XWPFNumbering. Also, there is wider problem about this component: there is a method XWPFNumbering.getAbstractNum(BigInteger abstractNumID), but the returned object has no connection with actual ctNumbering, and therefore abstract numberings cannot be edited with this API. Actually, I encountered this problem about removeAbstractNum while trying to workaround this impossibility to edit numberings by deleting them and adding again :) . So, I will try to spend some time this weekend trying to make an appropriate test, but I think this component needs more refactoring. -- 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]
